Your collection, with the agent you choose.

Before you connect

Connect from your agent and sign in or sign up when prompted. Your Tomebound account is created during connection; you can start with an empty collection and ask the agent to import a pasted list, CSV, or deck link after reviewing a preview. Your client needs remote MCP over Streamable HTTP and a supported sign-in method. The local web demo is not available to external agents.

OAuth sign-in opens Tomebound in your browser. Check the client name, redirect host, and requested access before choosing Approve. collection.read reads your account; collection.write also permits edits. Write access must be requested by the client. If it only requests read access, reconnect with write access enabled in that client when you need to edit.

You direct Tomebound to share tool results with the agent platform you connect. Read the connected apps privacy policy. Client menus and availability depend on your plan and workspace settings.

ChatGPT / OpenAI dots

Once Tomebound is listed in the OpenAI plugin directory, find it by name and connect your account. Until then, add it as a custom MCP plugin:

1. In ChatGPT on the web, open Plugins, select the plus button, then choose Add custom MCP server. Your workspace administrator may need to enable access.
2. Name it Tomebound and enter https://api.tomebound.app/mcp as the Server URL.
3. Choose OAuth with dynamic client registration. Leave static client credentials empty, review the connection warning, and select Create as a plugin.
4. Open Tomebound in your personal plugins and select the plus button to install it. Complete the Tomebound sign-in and consent flow when prompted.
5. Start a Work chat, type @ in the prompt box, and select Tomebound.

OpenAI plugin setup instructions

Claude

Tomebound is in Claude's connectors directory. On Claude web, desktop or mobile:

1. Open Tomebound in the directory (or Customize → Connectors → Browse connectors and search for Tomebound).
2. Click Connect, sign in to Tomebound, and approve the requested access. Team or Enterprise owners may need to allow it in organization settings first.
3. Enable Tomebound in the conversation's connectors menu, then ask about your collection.

You can also add it as a custom connector with the URL https://api.tomebound.app/mcp. Claude custom connector instructions

Meta Muse

1. Ask Muse: “Add a custom connector for Tomebound at https://api.tomebound.app/mcp. Start with read-only access to my Magic collection.”
2. If Muse offers OAuth, complete the Tomebound sign-in and consent page. Custom connector support can vary; an unsupported callback cannot complete sign-in.
3. If the connector supports secure Bearer credentials instead, create a read-only token in Tomebound Settings → Access tokens. Add it through the connector's secure credential control, then ask Muse to show your collection summary. Keep tokens out of conversation text.

This custom setup has not been verified end to end with Tomebound. If Muse cannot use the endpoint or securely accept credentials, use another client above. A public Muse listing requires separate approval through the Muse Connector Platform.

OpenClaw

Merge this entry into ~/.openclaw/openclaw.json, keeping your existing settings. Current OpenClaw uses mcp.servers for its main configuration; mcpServers is used in other client and plugin formats.

{
  "mcp": {
    "servers": {
      "tomebound": {
        "transport": "streamable-http",
        "url": "https://api.tomebound.app/mcp",
        "auth": "oauth",
        "oauth": { "scope": "collection.read" }
      }
    }
  }
}

1. Run openclaw mcp login tomebound, open the authorization URL, and approve access in Tomebound.
2. Run openclaw mcp doctor tomebound --probe to check the connection. Reload or restart the OpenClaw process that runs your agent.
3. For edits, change the scope to collection.read collection.write and authenticate again. Review the new consent request.

{
  "transport": "streamable-http",
  "url": "https://api.tomebound.app/mcp",
  "headers": {
    "Authorization": "Bearer ${TOMEBOUND_TOKEN}"
  }
}

OpenClaw MCP setup · Configuration and credentials

Codex

Run these commands, then complete the Tomebound sign-in and consent page:

codex mcp add tomebound --url https://api.tomebound.app/mcp
codex mcp login tomebound --scopes collection.read

Or merge this into ~/.codex/config.toml and run the same login command:

[mcp_servers.tomebound]
url = "https://api.tomebound.app/mcp"

For explicit write access, run codex mcp login tomebound --scopes collection.read,collection.write and review the consent request. Start a new session and ask Codex to use Tomebound.

Codex MCP instructions

Claude Code

claude mcp add --transport http tomebound https://api.tomebound.app/mcp

Inside Claude Code, run /mcp, select Tomebound, and authenticate. Review the requested permissions in Tomebound before approving, then ask Claude Code to use the connected tools.

Claude Code MCP instructions

Tomebound CLI

Requires Node.js 22 or newer. Install, sign in with read access, and inspect your collection:

npm install -g tomebound
tomebound login
tomebound summary
tomebound search "finish=foil order by price desc" --limit 10

For edits, sign in with write access. The CLI previews changes and asks before applying:

tomebound login --write
tomebound search "name=Sol Ring" --json
tomebound move "<itemKey>" --to "container:commander staples"

bp is a short alias for tomebound. Use --json for scripts and --dry-run to stop at the preview. The validate-deck and card-allocation commands analyze decks without changing your cards. Run tomebound help for all commands.

For a headless setup, create a personal access token in Settings → Access tokens and provide it through the TOMEBOUND_TOKEN environment variable. tomebound logout clears local OAuth credentials; revoke the connection in Tomebound to stop its server access.

Other MCP clients

{
  "mcpServers": {
    "tomebound": { "url": "https://api.tomebound.app/mcp" }
  }
}

{
  "servers": {
    "tomebound": {
      "type": "http",
      "url": "https://api.tomebound.app/mcp"
    }
  }
}

Other clients need Streamable HTTP with OAuth and PKCE S256, or a securely stored personal access token sent as a Bearer credential. OAuth discovery starts at https://api.tomebound.app/.well-known/oauth-protected-resource. Unsupported redirect hosts cannot connect through OAuth.

What you can ask

Name Tomebound in your request and attach the file or paste the card list when needed. Importing and creating decks require write access; ask to review the preview first.

• “Import my attached Moxfield export into Tomebound. Show me the proposed changes and any unresolved cards before saving.”
• “What's my collection worth? Show the currency, price coverage, and any cards without a price.”
• “Do I own the cards for this deck, and what would the rest cost? Include alternate printings and cards used in other decks.”
• “Build a deck from this list in Tomebound. Show the recipe first; don't add cards to my owned inventory.”
• “Export my Tomebound collection to ManaBox.”

Prices are estimates from available card data. Missing prices are unknown, not zero, and deck recipes do not mean you own those cards. Your client's enabled tools determine which requests it can complete.

Revoke access or recover a change

Open Settings → Connected apps in Tomebound and choose Revoke to stop an OAuth connection's access and refresh tokens. Manage personal access tokens separately in Settings → Access tokens. Revocation does not erase copies already held by the agent platform.

Ask your agent to undo its last Tomebound change. Undo succeeds only while the affected data is still safe to reverse; otherwise ask it to list recovery points and preview a restore. Review a restore carefully because it can replace later edits.