Skip to main content

Claude documentation connector

Connect Claude to your Biel.ai project through remote MCP so it can use your indexed documentation in a conversation.

Before you start​

Index your documentation, enable hosted MCP on a Biel.ai plan that includes it, and copy the project's MCP server URL from the widget's Connect menu. The endpoint must be reachable over HTTPS from Anthropic's servers.

Use the complete project URL. A public project needs no Biel.ai API key. For private content, review MCP access configuration first. Shared credentials grant connector users the credential's project access.

1. Add a custom remote connector​

For an individual account with connector access:

  1. Open Customize > Connectors in Claude.
  2. Select + Add > Add custom connector.
  3. Name the connector, for example Your Product Docs.
  4. Paste your complete Biel.ai MCP URL and continue.
  5. Review the detected authentication. Choose No sign in for a public project.
  6. Finish adding the connector.

On Team or Enterprise, an authorized owner adds the endpoint under Organization settings > Connectors > Add > Custom > Web. Members then connect to it from Customize > Connectors. See Anthropic's custom connector guide for current account and role requirements.

2. Enable and test the connector​

Start a conversation, use + > Connectors, and enable your connector. Ask:

Use Your Product Docs to explain how authentication works and cite the documentation.

Then test source retrieval:

Search Your Product Docs for SDK authentication using biel_search, then read relevant documents with biel_get_document. Use the retrieved sources to answer and cite them.

The server exposes biel_ai for Biel-generated answers, biel_search for hybrid keyword and semantic retrieval, and biel_get_document for complete indexed document text. Normally the assistant searches, reads relevant documents, and writes its own answer. Use biel_ai when you specifically want Biel to answer. See tools and limits.

Check a follow-up, a document with page or worksheet references, and a query with no result. Verify that source URLs work and that non-URL documents are identified by title and location.

3. Publish a connector in the Claude directory​

For public distribution, open the directory submission portal linked from Anthropic's plugin publishing guide. Choose the Single MCP connector route and provide your remote endpoint and listing details. Follow the portal's validation and review feedback, then publish after approval. Directory submission is available to developers on paid Claude plans.

Use a public documentation project for a public connector, or arrange supported authentication for the intended audience. Keep private API keys out of public listing details. A hosted endpoint connects to the specific Biel.ai project in its URL.

Troubleshooting​

  • Cannot connect: copy the URL again, including its path. Check that MCP is enabled and that Anthropic can reach the endpoint.
  • 403: check private-project API-key permissions, allowed domains, and usage limits. Biel.ai does not provide OAuth through an API-key URL.
  • Timeout: use source retrieval when Claude needs context to write its own answer. Generated answers can take longer; retries should follow a reported failure.
  • Updated tools are missing: reconnect the custom connector and start a new conversation. Anthropic currently documents removing and re-adding a custom connector to change its configuration.

Use the MCP troubleshooting guide for project and session errors.