Connect Claude to your Document360 knowledge base to work with your documentation directly from your Claude conversations. Once connected, Claude can search documentation, retrieve article content, create and update articles and categories, move content through review workflows, and publish it to your knowledge base site - with every operation following your Document360 roles and permissions.
Currently, there is no confirmed timeline for the availability of a direct Claude connector in the US region. Document360 has submitted the necessary Multi-Cloud Platform (MCP) request to Anthropic and is awaiting approval. Users are encouraged to stay updated through official Document360 announcements for any changes or updates regarding this feature.
If you are on a US-region project and you attempt to connect through Claude’s connector directory, clicking the Document360 connector redirects you to the EU-region Document360 portal (portal.document360.io). Because your project is hosted in the US region, your domain cannot be entered through the EU portal, and the connection will fail. Use the custom connector instead. For the US-region MCP server URL and setup steps, refer to the Connect MCP using custom connectors article.
The Document360 MCP connector is built and maintained by Document360. It is not a community-built or third-party tool. When connecting from the connector directory in Claude, Claude's interface may display a Community label on the Document360 tile. This label reflects how Claude categorizes third-party connectors in general; it does not mean the Document360 MCP connector itself is community-built or unofficial.
You can establish this connection in two ways:
- From the Document360 portal - Start the connection from the MCP settings page in Document360.
- From Claude - Add the Document360 connector from the connectors directory in Claude.
Both methods result in the same connection. Both take you directly to a chat session once connected.
Before you begin
- Ensure MCP is enabled in your Document360 project. For the steps to enable MCP, refer to the Connect MCP to your AI assistant page.
- You must have a Claude account on a paid plan.
- If your Claude account is on a Team plan, your Claude workspace administrator must enable custom connectors for your team before individual members can add them. If you are unable to add the Document360 connector, contact your Claude Team administrator to enable this.
- MCP access follows your Document360 role-based permissions. Claude can only access content permitted for the account you authenticate with.
Connect from the Document360 portal
To connect Claude from Document360,
- Navigate to Settings () in the left navigation bar.
- Go to AI Settings > MCP.
- On the Claude tile, click Connect.
You will be redirected to the Document360 connector in Claude, prompting you to connect.

-
Click Connect.

-
In the Connect with Document360 MCP page, select the desired project from the dropdown.
-
Select the I understand and trust this URL checkbox.
-
Click Continue.
You will be redirected to a Claude chat session. The connection is now active; enter a prompt to start working with your knowledge base.
Connect from Claude
To connect directly from Claude,
- Open Claude.
- Click your profile and navigate to Settings.
- Go to Connectors.
- Click Browse.
- In the search bar, search for Document360.

- Open the Document360 connector and click Connect.
- In the Connect with Document360 MCP page, select the desired project from the dropdown.
- Select the I understand and trust this URL checkbox.
- Click Continue.
You will be redirected to a Claude chat session. Enter a prompt to start working with your knowledge base.
Manage the connection
After connecting, you can manage the Document360 connector's tools, permissions, and connection status from Claude.
Go to Settings > Connectors and select Document360.
Set tool permissions
The Document360 connector's tools appear on the connector page, grouped by type (for example, Read-only tools, Write/delete tools) with the number of tools in each group. Under Tool permissions, you can control when Claude is allowed to use each tool.
You only see the tools your organization has given you access to. The tools available also depend on your Document360 role and permissions.
Each tool can be set to one of the following:
| Permission | Behavior |
|---|---|
| Always allow | Claude uses the tool without asking for approval. |
| Ask every time | Claude asks for your approval before each use. |
| Blocked | Claude cannot use the tool. |
You can set a permission for an entire group using the group's dropdown, or set each tool individually using the icons next to it. Setting different permissions across the tools in a group shows the group as Custom. This lets you, for example, allow read tools such as get-article and get-categories to run automatically while blocking or requiring approval for other tools.
Combine org-wide and individual access levels
Your organization's connector settings and your own personal tool permissions work together, not independently. If your organization sets a tool's permission to Blocked for everyone, that restriction applies organization-wide: individual members can tighten their own settings further, but cannot loosen them past what the organization allows. For this reason, do not set the write or delete tools to Blocked at the organization level if any employee needs write access through this connector.
If you need most employees to have read-only access while one or more specific people keep write and delete access, use one of the following approaches instead.
Approach 1: Rely on Document360 roles
This works on any Claude plan. Since MCP access follows your Document360 role-based permissions, you can leave the connector's write and delete tools allowed at the organization level, and instead control access through Document360 itself:
- Assign employees who should have read-only access a Document360 role that only permits reading published articles.
- Keep your own Document360 role with edit and delete permissions so your write access continues to work through the same connector.
Approach 2: Use Claude custom roles (Claude Enterprise only)
If you are on Claude Enterprise and also want the write and delete tools hidden from most employees within Claude itself:
- Set the organization-wide policy for the Document360 connector's write and delete tools to allowed. Do not set it to Blocked.
- Create a custom role for all employees that sets the Document360 connector to Custom, allowing the read tools and blocking the write and delete tools.
- Create a separate role (for example, a Technical Writers role) that allows the write and delete tools, and add the people who need write access to that role.
Permissions add up across the roles a person belongs to, so someone in both the all-employees role and the Technical Writers role keeps write access.
View connector details
Click the more options icon ( ) and select View details to open the connector's information page. This page includes the author, the connector URL (used when connecting through a custom connector), and links to the documentation, support, and privacy policy. For a detailed explanation of each tool, refer to the Supported MCP tools article.
Get new MCP tools
When Document360 releases new MCP tools, Claude may not detect them automatically. To refresh the available tools:
- Go to Settings > Connectors and select Document360.
- Click the more options icon ( ) and select Refresh tools list.
The connector updates to include any newly added MCP tools without requiring a full reconnect.
Disconnect
- Go to Settings > Connectors and select Document360.
- Click Disconnect.
- In the confirmation dialog, click Disconnect to confirm, or Cancel to keep the connection.
Once disconnected, Claude can no longer access your knowledge base until you reconnect.
Once disconnected, Claude can no longer access your knowledge base until you reconnect.

Verify the connection
To confirm that Claude can access your knowledge base:
- Start a new chat in Claude.
- Enter a prompt that asks Claude to fetch or search your documentation. For example, ask it to find an article by title or summarize a specific topic from your knowledge base.
If the connection is successful, Claude returns results sourced from your Document360 knowledge base. For more prompts you can try, refer to the MCP use cases article.
If Claude returns no results or an error, verify that MCP is enabled in Document360 and that the connector is active in Claude, then refresh the tools list and try again.
Troubleshooting
Claude returns a "CONNECT tunnel failed, response 403" or "HTTP 000" error when calling the Document360 API
If you have configured Claude to call Document360 REST API endpoints directly (not through the MCP connector) and Claude returns an error similar to "CONNECT tunnel failed, response 403" or an HTTP 000 status, the connection is being refused before the request reaches Document360. This is a network-level block from Claude’s own environment, not an authentication failure.
An invalid API key would produce a 401 status code with a JSON error body. A 403 CONNECT tunnel failure means Claude cannot establish the connection at all.
Claude’s network environment only allows outbound connections to an approved list of domains by default. The Document360 API host must be added to Claude’s allowed domains before API calls can succeed.
To add the Document360 API host to Claude’s allowed domains:
- If your Claude account is on a Team or Enterprise plan, ask your Claude organization admin to add the host under Organization settings > Capabilities.
- If your Claude account is on a paid individual plan, add the host yourself under Settings > Capabilities.
Add the host that matches your Document360 project’s data center:
- EU region:
apihub.document360.io - US region:
apihub.us.document360.io
Adding either host covers all Document360 API endpoints on that host, including endpoints such as Get an article and Bulk update articles.
After the domain is added, retry the request. If the request now returns a 401 instead of a connection error, verify that the API key is valid by running the same request from a local machine. A 200 response from there confirms the key is correct.
If you are building a workflow where Claude listens for Document360 webhook events and also makes API calls back to Document360, see Webhook notification channel for instructions on configuring the outgoing webhook in Document360.
No changes are required on the Document360 side for webhook delivery. The apihub domain configuration above applies only to API calls that Claude initiates.