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

# BotShield MCP server

> Register the BotShield MCP server so Employee agents can reach the Agents Ask tools.

Register the **BotShield MCP server** to give Employee agents a way to reach the Agents Ask tools over the Model Context Protocol. This extends the *reach* of BotShield to more agent surfaces. The packaged Apex actions remain the **hard gate**. MCP is not a configuration or admin surface.

## Register the server

<Steps>
  <Step title="Open MCP Servers in Setup">
    Go to **Setup → MCP Servers → External Servers → New**.
  </Step>

  <Step title="Enter the connection">
    | Field | Value |
    | - | - |
    | Server URL | `https://mcp.botshield.ai/mcp` |
    | Identity Provider URL | `https://mcp.botshield.ai` |
    | Auth | OAuth 2.0, **client credentials** |
    | Scope | `queue` |
    | Client ID | your agent's name |
    | Client Secret | your BotShield agent key |
  </Step>

  <Step title="Approve the tools">
    Allow the BotShield tools you want the agent to use.
  </Step>
</Steps>

<Note>
  Using the **Staging** environment? Use `https://mcp-staging.botshield.ai/mcp` and `https://mcp-staging.botshield.ai` instead.
</Note>

## Tools

| Tool | Purpose |
| - | - |
| `bind_session` | Start linking a human to the session. |
| `check_binding` | Confirm the link. |
| `propose_resolution` | Propose a sensitive action for human confirmation. |
| `check_resolution_status` | Poll for the verdict. |
| `cancel_resolution` | Cancel a pending proposal. |

<Warning>
  **MCP is reach; the packaged Apex actions are the hard gate.** An agent reaching BotShield over MCP still can't take a sensitive action without an approved, signed resolution. The server-side Apex enforces it regardless of how the agent connects.
</Warning>