# MCP server

> Connect Claude, ChatGPT, Codex, Cursor and other MCP clients to the border.bot remote MCP server, with OAuth sign-in.

Source: https://staging.border.bot/docs/mcp
Last updated: 2026-10-10

> Documentation index: https://staging.border.bot/llms.txt. Every page is Markdown at its URL + `.md`.


The border.bot MCP server classifies products, calculates landed cost, infers country of origin and checks restricted goods from inside an MCP client.

|           |                                                                            |
| --------- | -------------------------------------------------------------------------- |
| URL       | `https://staging-mcp.border.bot/mcp`                                                                  |
| Transport | Streamable HTTP                                                            |
| Auth      | OAuth 2.1; the client opens a sign-in page, no API key                     |
| Credits   | Tools that run the engine spend the workspace's credits, like the REST API |

The assistant acts for the person who connected it and bills their workspace. Results are estimates to check with the customs authority or a licensed broker, not customs, tax or legal advice; see the [terms of service](https://staging.border.bot/legal/terms) and [privacy policy](https://staging.border.bot/legal/privacy).

## Connect

Add `https://staging-mcp.border.bot/mcp` as a remote (HTTP) MCP server in your client. For example, in Claude Code:

```bash
claude mcp add --transport http borderbot https://staging-mcp.border.bot/mcp
```

Or in an `mcp.json` file (Cursor, VS Code and others):

```json
{
  "mcpServers": {
    "borderbot": { "url": "https://staging-mcp.border.bot/mcp" }
  }
}
```

Step-by-step setup for every client, including Claude, ChatGPT, Codex, Cursor, VS Code and Gemini CLI, is on the [MCP server page](https://staging.border.bot/mcp). The menu at the top of this page also connects Cursor and VS Code in one click.

Connected before October 2026 with `https://staging-api.border.bot/mcp`? That address keeps working for existing connections. Use `https://staging-mcp.border.bot/mcp` when you connect a client again.

## Tools

Every tool with its input schema is public at [https://staging-mcp.border.bot/mcp/tools.json](https://staging-mcp.border.bot/mcp/tools.json), and the server card at [https://staging.border.bot/.well-known/mcp/server-card.json](https://staging.border.bot/.well-known/mcp/server-card.json).

Every tool result carries the id the call was logged under in `_meta["border.bot/requestId"]`, the same UUID as the response's `X-Request-Id`. Quote it when you ask support about a call; it also finds the call in your workspace's request log.