Extend

Parse, extract, classify and split documents and fill PDF forms from Claude with Extend.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Extend connector does

The Extend MCP server connects Claude to Extend's document processing platform. Its 86 tools parse PDFs, images and Office files, extract fields and line items, classify and split documents, fill PDF forms, and build, publish and run reusable processors and workflows. Every run spends Extend credits. Sign-in is OAuth, scoped to the workspaces you choose.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Extend tools (86)

  • add_evaluation_items
  • cancel_classify_run
  • cancel_extract_run
  • cancel_split_run
  • cancel_workflow_run
  • classify_document
  • create_classifier
  • create_evaluation_set
  • create_extractor
  • create_splitter
  • create_webhook_endpoint
  • create_webhook_subscription
  • create_workflow
  • delete_classify_run
  • delete_edit_run
  • delete_evaluation_item
  • delete_extract_run
  • delete_file
  • delete_parse_run
  • delete_split_run
  • delete_webhook_endpoint
  • delete_webhook_subscription
  • delete_workflow_run
  • deploy_workflow_version
  • detect_form_fields
  • edit_pdf
  • extract_data
  • get_classifier
  • get_classify_batch
  • get_classify_run
  • get_documentation
  • get_edit_run
  • get_evaluation_run
  • get_extract_batch
  • get_extract_run
  • get_extractor
  • get_file
  • get_file_upload
  • get_form_detection_run
  • get_me
  • get_parse_batch
  • get_parse_run
  • get_split_batch
  • get_split_run
  • get_splitter
  • get_workflow
  • get_workflow_run
  • list_classifier_versions
  • list_classifiers
  • list_classify_runs
  • list_evaluation_items
  • list_evaluation_sets
  • list_extract_runs
  • list_extractor_versions
  • list_extractors
  • list_files
  • list_parse_runs
  • list_split_runs
  • list_splitter_versions
  • list_splitters
  • list_webhook_endpoints
  • list_webhook_subscriptions
  • list_workflow_runs
  • list_workflow_versions
  • list_workflows
  • parse_document
  • publish_classifier_version
  • publish_extractor_version
  • publish_splitter_version
  • run_classify_batch
  • run_evaluation
  • run_extract_batch
  • run_parse_batch
  • run_split_batch
  • run_workflow
  • run_workflow_batch
  • search_documentation
  • split_document
  • update_classifier
  • update_evaluation_item
  • update_extractor
  • update_splitter
  • update_webhook_endpoint
  • update_webhook_subscription
  • update_workflow
  • upload_file

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Metered. Every processing run consumes credits; the connector itself has no spending cap we found documented.
  • One deployment per connector. The directory connector reaches the default deployment only.
  • Human review stays in the dashboard. When a workflow pauses for review, the agent hands you a dashboard link to approve it.
  • No air-gapped option. Extend says it offers cloud, bring-your-own-cloud and hybrid deployment, but not a fully air-gapped one.
  • Compliance is Extend's statement. Extend's compliance page says it keeps controls "aligned with SOC 2 Type II", is HIPAA compliant and can sign BAAs, and is GDPR compliant with EU processing in Frankfurt. We have not reviewed its reports.
  • No tool schemas or annotations were readable, so parameters are not described here.

Frequently asked questions

Why doesn't Extend sign-in recognise my account?

Your client is probably connected to a different Extend deployment from the one that hosts your workspace. Extend runs a separate MCP server per deployment: the default at mcp.extend.ai, US2 at mcp.us2.extend.app and EU1 at mcp.eu1.extend.ai. The Claude directory connector uses the default. If your workspaces live in US2 or EU1, add a custom connector with that deployment's URL instead and sign in again.

Why can't the agent find an Extend resource I know exists?

It is usually looking in the wrong workspace or environment. Extend keeps resources separate per workspace and per Test or Production environment, so an extractor created in Test does not exist in Production. Ask the agent to call get_me, which lists the workspaces and environments the connection was granted, and then to target the place where the resource actually lives.

Should I use Extend's MCP server, CLI or an SDK?

Use the MCP server for chat and tool-calling clients such as Claude. Extend recommends its SDKs, in Python, TypeScript, Java and Go, when an agent is writing durable integration code, and its extend CLI for one-off jobs driven from a shell. Its Agent Quickstart explains how to equip a coding agent with each option, including a CLI skill and an API context file.

Sources

Use it in an agent

Put Extend to work.

Connect Extend once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.