> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bindbee.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Docs MCP

> Connect your AI assistant to the Bindbee documentation so it answers from the live docs instead of guessing.

Bindbee hosts an MCP server over the whole documentation site. Point Claude, Cursor, Codex, or any MCP client at it and they can search the docs, read full pages and grep the OpenAPI specs while they help you build.

```
https://docs.bindbee.dev/mcp
```

No API key and no account. The server is read-only and covers published documentation only.

<Tip>
  For a one-off question about a single page, use the **Copy page** menu at the top to copy or open it straight in Claude or ChatGPT. The MCP server is for when you want an assistant to search the whole site on its own.
</Tip>

## Connect

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http bindbee-docs https://docs.bindbee.dev/mcp
    ```

    Confirm it registered with `claude mcp list`.
  </Tab>

  <Tab title="Claude">
    1. Open [Connectors](https://claude.ai/settings/connectors) in Claude settings.
    2. Click **Add custom connector**.
    3. Name it `Bindbee Docs` with URL `https://docs.bindbee.dev/mcp`.
    4. Click **Add**.
    5. In a chat, click the plus icon and select the server.
  </Tab>

  <Tab title="Cursor">
    Command palette, then `Open MCP settings`, then **Add custom MCP**. In `mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "bindbee-docs": {
          "url": "https://docs.bindbee.dev/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Create `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "bindbee-docs": {
          "type": "http",
          "url": "https://docs.bindbee.dev/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Codex">
    In `~/.codex/config.toml`:

    ```toml theme={null}
    [mcp_servers.bindbee-docs]
    url = "https://docs.bindbee.dev/mcp"
    ```

    Start a session and ask what tools are available to confirm.
  </Tab>

  <Tab title="Other clients">
    Most clients accept the same block:

    ```json theme={null}
    {
      "mcpServers": {
        "bindbee-docs": {
          "url": "https://docs.bindbee.dev/mcp"
        }
      }
    }
    ```

    Or install it from the command line:

    ```bash theme={null}
    npx add-mcp https://docs.bindbee.dev/mcp
    ```
  </Tab>
</Tabs>

## What it exposes

| Tool                                 | What it does                                                                         |
| ------------------------------------ | ------------------------------------------------------------------------------------ |
| `search_bindbee_docs`                | Searches across the docs, returning snippets with titles and links.                  |
| `query_docs_filesystem_bindbee_docs` | Reads a virtual filesystem of every page and OpenAPI spec with shell-style commands. |
| `submit_feedback`                    | Reports a page that is wrong, outdated, or confusing back to the docs team.          |

Agents usually chain the first two: search to find the right page, then read all of it. That matters on pages like [Create Time Off](/hris/time-off/create-time-off), where the provider-specific accordions are exactly the part a search snippet cuts off.

```bash theme={null}
ls /                                                 # the top-level structure
grep -rl passthrough /                               # every page that mentions a term
head -200 /api-reference/basics/authentication.mdx   # read a page in full
```

### Skill

The server also exposes a skill resource. MCP gives an agent access to the docs, and the skill tells it how to use them: covering auth headers, base URLs, pagination, rate limits, and the common endpoints per category. Clients that support MCP resources load it automatically, and the file is readable at [`/skill.md`](https://docs.bindbee.dev/skill.md) for tools that do not.

The skill is generated from these docs and regenerates as they change, so it always tracks published content.

## Try it

Once connected, ask in your own words:

* Which fields does the unified Employee model return for BambooHR?
* Write the request body to create a time off entry on ADP.
* Does Bindbee support writing timesheet entries, and on which connectors?
* Set up a custom field that pulls a badge number out of raw\_data.
* What is the difference between id and remote\_id in a passthrough call?

In an agentic coding tool this pairs with your own codebase. The assistant reads your integration code and the Bindbee reference in the same turn, so it writes against the real schema rather than a remembered one.

## Related

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/api-reference/basics/authentication">
    API keys and connector tokens for calling Bindbee itself.
  </Card>

  <Card title="Embedded SDK" icon="code" href="/guides/sdk/embedded-sdk">
    Embed the connector link flow in your product.
  </Card>

  <Card title="Model Context Protocol" icon="book" href="https://modelcontextprotocol.io">
    The open standard behind this server.
  </Card>

  <Card title="Contact support" icon="mail" href="mailto:support@bindbee.dev">
    Questions about the server or the docs.
  </Card>
</CardGroup>