Skip to content

Documentation

Connect your client

Two steps: create a token in the panel, then tell your client where the server is. The token travels in an Authorization header, so any client that can send one will work.

Create the token

  1. 1Open your panel, go to the account area and from there to the assistant connection tab.
  2. 2Give it a name you will recognise later, such as the machine you work from.
  3. 3Choose the scope: read only, read and write, or read, write and publish.
  4. 4Choose whether it reaches every page or only the ones you tick.
  5. 5Copy the token. It is shown once and never again; if you lose it, revoke it and create another.

Treat the token like a password. Whoever holds it does whatever its scope allows, without your password and without your second factor.

Configure your client

Replace YOUR_TOKEN with the token you copied. The server address is the same for everyone.

Claude Code
claude mcp add --transport http 1door https://1door.to/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Run it once in the terminal. Add --scope user to have it in every project.

Codex~/.codex/config.toml
[mcp_servers.onedoor]
url = "https://1door.to/api/mcp"
bearer_token_env_var = "ONEDOOR_TOKEN"

Goes in the Codex configuration file, under a server of its own.

Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "1door": {
      "url": "https://1door.to/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Goes in the MCP file Cursor reads, either the global one or the one in your project.

GitHub Copilot.vscode/mcp.json
{
  "servers": {
    "1door": {
      "type": "http",
      "url": "https://1door.to/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Goes in the MCP file of your workspace, and the editor asks before it starts the server.

Any other client
POST https://1door.to/api/mcp
Content-Type: application/json
Authorization: Bearer YOUR_TOKEN

Any other client needs the same three pieces: the address, the HTTP transport and the Authorization header.

Check that it works

Ask your assistant to list your pages. If the token is right, it comes back with your pages and their state. If it is wrong or revoked, the server answers 401 and nothing else happens.

You can revoke a token from that same tab whenever you want. The next call fails on the spot.