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

# Global-e Documentation MCP

Connect this documentation to Claude, Cursor, VS Code, or any assistant that speaks the Model
Context Protocol (MCP), and it searches these pages on demand while you work.

**Server address (streamable HTTP):** `https://docs.global-e.com/mcp`

<Note>
  Read-only: your assistant can search and read the published documentation, not change it. No
  sign-in and no API key.
</Note>

## Add the server

**Claude Code**

```bash theme={null}
claude mcp add --scope user --transport http globale-docs https://docs.global-e.com/mcp
```

`--scope user` makes it available in every project. Check it with `claude mcp list`.

**Cursor.** Add to `~/.cursor/mcp.json`, or your project's `.cursor/mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "globale-docs": { "url": "https://docs.global-e.com/mcp" }
  }
}
```

**VS Code.** Add to `.vscode/mcp.json`:

```json theme={null}
{
  "servers": {
    "globale-docs": { "type": "http", "url": "https://docs.global-e.com/mcp" }
  }
}
```

**Claude desktop and web.** Go to **Settings > Connectors**, click **Add custom connector**, and
paste the address. Select it from the attachments menu in a conversation.

**Codex.** Add to `~/.codex/config.toml`, then restart your `codex` session:

```toml theme={null}
[mcp_servers.globale-docs]
url = "https://docs.global-e.com/mcp"
```

**Any other client.** Point it at the address above. No key, no headers, no OAuth.

<Warning>
  Restart your assistant afterwards. Most clients read their MCP configuration only at startup, so
  a session that was already open will not see the server even though it reports as connected.
</Warning>

## Tell your assistant to use it

Connecting the server makes it available; it does not make your assistant reach for it. Put this
in the file your tool reads for standing instructions (`AGENTS.md`, `CLAUDE.md`, or a Cursor rule):

```md theme={null}
You have MCP tools named `search_global_e_docs` and `query_docs_filesystem_global_e_docs`.
They search the published Global-e documentation, which is more current and more specific
than your training data. Use them for any question about Global-e behaviour, API fields,
endpoints, configuration or integration steps, and cite the page you used.
```

Otherwise, name the documentation in the question: *"using the Global-e docs, …"*.

## What it can do

| Tool | What it does |
| - | - |
| **`search_global_e_docs`** | Searches the documentation and returns matching content, with links to the pages |
| **`query_docs_filesystem_global_e_docs`** | Reads a full page. Search returns extracts; this returns the whole thing |
| **`submit_feedback`** | Reports a problem with a page to the Global-e documentation team |

If your assistant surfaces a page that is wrong or out of date, ask it to submit feedback. The
report reaches the documentation team without a support ticket.

## What it covers

* **Published pages on this site only.** Not drafts, internal material, or anything behind a
  sign-in. A page is reachable as soon as it is published.
* **Documentation, not a product API.** It answers questions about the documentation; it does not
  place orders, read your account, or run anything against Global-e systems.