Skip to main content

MCP Server

Official Talonic MCP server. Lets AI agents extract structured, schema-validated data from any document via the Model Context Protocol. Twenty-two tools and two resources, verified end-to-end against production.

Hosted at mcp.talonic.com/mcp (the bare origin mcp.talonic.com also works) — zero install, works with every MCP client. Also available on npm as @talonic/mcp for local use, and listed on the official MCP Registry as io.github.talonicdev/talonic-mcp.

The server exposes twenty-two tools: talonic_extract for document extraction with schema-validated JSON output, talonic_search for full-text search across your document registry, talonic_filter for structured field-level filtering, talonic_get_document for retrieving individual documents, talonic_to_markdown for converting documents to clean markdown, talonic_list_schemas for browsing available schemas, talonic_save_schema for persisting new extraction schemas, talonic_get_balance for checking the workspace credit balance and runway, talonic_get_pricing for the per-unit credit pricing catalog, talonic_get_usage for per-function credit consumption, talonic_request_upload for browser-handoff uploads when the file is too large to send through the tool-call channel, the Field Registry family — talonic_list_fields, talonic_get_field and talonic_field_values — for the canonical concepts Talonic discovered across your documents and their values with provenance, talonic_find_data for locating the fields, documents and passages behind a concept by meaning, talonic_list_agent_tools and talonic_invoke_agent_tool for running the platform agent's own retrieval and analysis primitives directly, and the Agent-stage task family — talonic_list_agent_tasks, talonic_get_agent_task, talonic_claim_agent_task, talonic_heartbeat_agent_task and talonic_submit_agent_task — for pulling documents parked at an Agent stage, working them under a lease, and submitting the declared outputs. All tools return typed, structured responses with confidence scores and provenance metadata.

Supported MCP clients include Claude Desktop, Cursor, Cline, Continue, Cowork, and any client implementing the Model Context Protocol specification. Setup takes one line — add the server URL to your client configuration and provide your Talonic API key as an environment variable.