MCP server for docs

Hosted MCP server for your docs

Connect your indexed documentation to Claude, Cursor, Windsurf, and other supported MCP clients. Hosted MCP starts at $150/month and uses the same sources as the Biel chatbot.

14-day freeSelf-serveLive in 15 min
Claude · biel-docs MCP
D
How do I configure the rate_limit on a route in Acme's API? Need to support burst windows.
Called biel-docs.search_docs · 2 sources

PATCH the route with rate_limit. Each route has its own bucket scoped to the path; authenticated and anonymous traffic are metered separately.

curl -X PATCH https://api.acme.dev/v1/routes/checkout \
  -d '{"rate_limit":{"requests":100,"per":"minute","burst":50}}'

The burst field caps transient surges. When clients exceed the limit, the API returns 429 with a Retry-After header.

api/rate-limits.md § Per-route configurationapi/config.md § rate_limit reference

100,000+ technical questions answered, 98.7% rated helpful

ScyllaDB
Katalon
Tezos
Talon.one
GrepTime
CrazyGames
SecuroSys
ScyllaDB
Katalon
Tezos
Talon.one
GrepTime
CrazyGames
SecuroSys
Without MCP vs with MCP

The same question, two days apart.

Today, developers ask their AI assistant a question, get a generic answer, then go hunt your docs to confirm. Tomorrow, the same assistant queries your docs first and grounds the answer. The difference is one MCP endpoint.

Without MCP · generic LLM
Guess
how do I configure rate_limit on an Acme route?
No tools available · answering from training data
For most APIs you'll set a rate_limit field somewhere on the route or endpoint config. Common patterns are {"requests": N, "per": "minute"} or middleware-based limiters like express-rate-limit.
// Generic example — verify against Acme's actual API
app.use('/checkout', rateLimit({
  windowMs: 60 * 1000,
  max: 100,
}));
You'll want to check Acme's documentation for the specific configuration shape.
Sources
No documentation accessible · suggested reading: Acme API reference
Generic guess · no groundingDeveloper goes to docs →
With MCP · Claude + biel-docs
Answer
how do I configure rate_limit on an Acme route?
Called biel-docs.search_docs · grounded in 2 sources
Set rate_limit on the route. Each endpoint has its own bucket scoped to the route path; authenticated and anonymous traffic are metered separately.
# PATCH a single route
curl -X PATCH https://api.acme.dev/v1/routes/checkout \
  -H "Authorization: Bearer sk_..." \
  -d '{"rate_limit":{"requests":100,"per":"minute"}}'
For burst handling, add burst (transient surge cap). Limits are enforced at the edge before reaching your handler.
Sources
api/rate-limits.md§ Per-route configuration
api/config.md§ rate_limit reference
1 synthesized answer · 2 sourcesUser has the answer ✓
Compatible tools

One endpoint for supported MCP clients

Configure the hosted endpoint in the tools your team already uses. Availability depends on each client’s MCP support.

Claude Desktop

Chat with your docs in Claude. Configure once in claude_desktop_config.json.

Claude Code

CLI-powered doc lookups while you're heads-down in a terminal.

Cursor

Retrieve relevant documentation while working in the editor.

Windsurf

Make indexed documentation available to supported Windsurf workflows.

VS Code + Copilot

Connect through an MCP-compatible VS Code extension.

Cline

Autonomous agents with read access to your docs as a tool.

How it works

Connect your docs, then add the endpoint

Biel hosts the MCP server. Connect your sources, copy the project endpoint, and add it to a supported client.
  1. 01

    Connect your docs

    Paste your documentation URL. Biel.ai crawls, chunks, and indexes your content automatically. Twenty-plus platforms supported out of the box.Create an account
  2. 02

    Get your MCP endpoint

    Plans with MCP include a hosted server URL for your project. Biel operates the endpoint, so you do not need to deploy an MCP server.
    https://mcp.biel.ai/v2/<project>/mcp
  3. 03

    Add it to any AI tool

    Add the URL to a supported MCP client. It retrieves from the same indexed sources as your Biel chatbot.
Supported platforms

Connect multiple sources to one project

Index supported documentation sites, repositories, and knowledge sources, then expose that project through one MCP endpoint.

Things teams ask during evaluation

What is the Model Context Protocol (MCP)?

MCP is an open protocol for connecting AI assistants to tools and data sources. Biel uses it to make your indexed documentation available to compatible AI clients.

Do I need to self-host the MCP server?

No. Plans with MCP include a hosted endpoint at mcp.biel.ai. Add that URL to a supported client; Biel operates the server.

Which AI tools support MCP today?

Biel works with clients that support remote MCP servers, including Claude, Cursor, Windsurf, Cline, and compatible VS Code extensions. Client support can change, so check the client documentation during setup.

How does the MCP server stay in sync with my docs?

Biel refreshes indexed sources on a schedule or on demand. The MCP endpoint and website chatbot retrieve from the same project index.

Can multiple team members use the same MCP server?

Yes. The endpoint is shared per project. Each team member adds the same URL to their MCP client config. For internal docs, scope a token to your workspace. For public docs, no auth is required.

Can I expose internal docs alongside public docs?

Yes. Mix Confluence, Notion, GitHub repos, and your public docs in the same project. The MCP server can serve all of them under one endpoint, or you can split internal and external into separate projects with separate tokens.

Does MCP replace the chatbot widget?

No. The website widget serves readers in your docs; MCP makes the same project index available inside compatible AI tools.

Is the MCP server secure?

Yes. Access is read-only and scoped by project token; tokens can be rotated or revoked from the dashboard. See the Security Overview.

Turn your docs into an MCP server.

14-day free trial · No credit card required
Try me ↓