A read-only connection between your AI assistant and the corporate record you keep in DocChief: your documents, the events they record, the people and companies named in them, and the standings between those parties.
https://mcp.docchief.ai/mcpWho can use it
This server is not open to the public. You need both of the following.
- A DocChief account at my.docchief.ai. You sign in with that account to connect.
- A space (dataroom) that is yours or was shared with you. Either you created the space, or its owner invited you to it and gave you a role in it.
Having an account is not enough on its own. A signed-in user who owns no space and has not been invited to one reads nothing here, because the server only ever returns what that person’s own DocChief account already opens.
You also need an MCP client that supports remote servers over HTTP and OAuth, such as Claude. There is nothing to install and nothing to run on your machine. The server is hosted by DocChief.
Connect the server
- In your MCP client, add a custom connector.
- Paste the server URL
https://mcp.docchief.ai/mcp. - The client sends you to DocChief to sign in. If you are already signed in, this step is skipped.
- DocChief shows you which application is asking for access and where it will send you back. Check the application name and the return address, then approve or reject.
- You are returned to your client and the connection is ready. The tools below become available to the assistant.
Anyone can register a client and name it whatever they like. The approval screen shows the return address for exactly this reason. If the name says one thing and the address points somewhere you do not recognise, reject it.
What the server can do
Fifteen tools, all read-only over your own data. The assistant chooses which ones to call based on your question.
Find your way around
| Tool | What it does |
|---|---|
list_spaces | Lists every space you can read, your role in it, and how much of it you can see. |
get_space_vocabulary | Lists the exact filter values that exist in a space: document types, party roles, event types. |
search_documents | Finds documents by type, by party or by event. |
semantic_search | Searches by meaning across a space when you are looking for a clause or a figure rather than a file. |
Read a document
| Tool | What it does |
|---|---|
get_document | Returns everything DocChief extracted from one document: its parts, dates, parties and events. |
get_document_summary | Returns the short summary of a document. |
get_extracted_text | Returns the document’s text, page by page. |
get_document_view_link | Returns a link that opens the document in the DocChief viewer. The link requires a DocChief login. |
See the record across a whole space
| Tool | What it does |
|---|---|
list_space_parties | Lists the people and companies named across the space. |
list_space_events | Lists dated events across the space, such as signings, issuances and appointments. |
list_space_relationships | Lists what is true between parties as a result of those events, such as signing authority or a shareholding. |
list_watches | Lists the health checks DocChief runs over the space. |
get_watch_section | Returns one health-check subject in full. |
DocChief itself
| Tool | What it does |
|---|---|
get_docchief_updates | Returns product news and usage tips. |
send_feedback_to_docchief | Sends a message from you to the DocChief team. This is the only tool that writes anything, and it writes to our support inbox, never to your documents. |
What the server cannot do
- It cannot upload, edit, move, rename or delete anything.
- It cannot download a file.
get_document_view_linkreturns a link to the DocChief viewer, and opening it needs a login. - It cannot create or change share links. Sharing stays in the DocChief app.
- It never returns documents you have moved to the trash.
- It cannot reach spaces you do not have access to, or documents inside a space that were not shared with you.
Who can see what
Access is worked out on every single request, from your DocChief account. It is not stored in the connection, and connecting grants nothing by itself.
- A space owner, or a co-admin, reads the whole space.
- An invited member reads only what the owner gave them. That is often a subset of the documents rather than the whole space.
- A signed-in user with no space of their own and no invitation reads nothing.
If your access in DocChief changes, the connection reflects that on the next call. You do not need to reconnect. An empty result is a normal answer, not a failure.
How authentication works
- OAuth 2.1, authorization code flow with PKCE (
S256). Your DocChief password is never shared with the client. - Clients register themselves through Dynamic Client Registration (RFC 7591). No client secret is issued, and none is needed.
- Access tokens last 1 hour. Refresh tokens last 30 days and are rotated on use.
- Tokens are bound to the MCP endpoint, so a token minted for this server is not valid anywhere else.
Discovery documents, if your client asks for them:
https://mcp.docchief.ai/.well-known/oauth-protected-resource
https://my-api.docchief.ai/.well-known/oauth-authorization-server
Clients that cannot do OAuth
Some local tools only support a plain bearer token. For those, open Connectors → Connect to MCP in DocChief, expand Advanced settings, and create a token under Access tokens. Send it as Authorization: Bearer dcmcp_…. The token carries your own access and can be revoked from the same place. Otherwise connect over OAuth, which is what Claude and ChatGPT do by default.
Disconnecting
Open Connectors → Connect to MCP in DocChief, expand Advanced settings, and revoke the application under Connected assistants. The connection stops working immediately and the client must go through approval again to come back. Revoking one application does not affect any other.
Support
Write to contact@docchief.ai, or ask your assistant to use send_feedback_to_docchief.