Skip to main content
The Filed MCP server is not live in production yet. The connection details below are accurate for the built server, but the URLs will not resolve until it ships. Check with Filed before sharing this page with an integrator who needs it working today.
Filed runs a remote MCP server that lets AI assistants like Claude and Codex act directly on a Filed workspace: run GraphQL queries and mutations, upload documents, and read the API docs, all without you writing any integration code. Unlike the API key model used for custom integrations, connecting an MCP client to Filed is a one-time OAuth consent flow in your browser. There is no key to copy or paste.

​
Connect a client

Approving the connection creates an MCP-type entry in the workspace’s Integrations page, the same place API keys live. Revoke access at any time by deleting it there: the next request from that client gets a 401.

​
What the server exposes

The server exposes three tools. They are the same tools Filed’s own assistant uses, so anything the assistant can do for you in Filed, your MCP client can do too, with the same access. Every call runs as you. You only reach the clients your firm has given you, and admin-only actions are refused for other roles with a clear reason.

​
How agents should work

  1. Call product_docs with what you want to do, such as “send the return to tax software” or “reply to a note on a document”. It returns the booklet pages for that job and the schema of every tool they name.
  2. Find the client with product_query and clients_find.
  3. Read with product_query, change things with product_mutation.
  4. Work that takes time, such as Data Entry or adding documents, returns a task id. Follow it with product_query and tasks_get_status.
Errors come back as {error: {code, message, hint}}. An invalid input includes the tool’s schema, so the agent can correct the call without searching again.

​
Uploading documents

MCP tool calls carry a single JSON message, so file bytes don’t travel through a tool call directly. To upload a document, the assistant:
  1. Calls product_mutation with files_get_upload_url to get a short-lived (10-minute) upload token and the platform’s tus upload URL.
  2. Drives the resumable tus upload directly against that URL, exactly as described in Uploading documents.
  3. Passes the resulting upload id to documents_save, which saves the document to the client. documents_process_into_binder then adds it to the Binder.

​
Access and revocation

A connection is scoped to one workspace, chosen when you approve it. To connect a second workspace, add another connection and approve it separately. To revoke access, delete the connection from the workspace’s Integrations page. The next token exchange (within about two minutes, due to caching) starts failing, and the next MCP request from that client gets a 401.

​
Troubleshooting

The client won’t complete the connection
  • Confirm you’re signed in to the Filed web app in the same browser that completes the OAuth redirect.
  • Confirm your MCP client supports streamable HTTP (not only SSE).
Tool calls return 401
  • The connection was revoked, or the underlying session cache expired and the next exchange failed. Reconnect the client.
A tool call returns FORBIDDEN or NOT_FOUND
  • The connection acts as you. A client your firm hasn’t given you looks like one that doesn’t exist, and admin-only actions are refused for other roles. The error’s hint says what is missing.