Connect your AI assistant

Claude

In Claude (web, desktop or mobile): Settings → Connectors → Add custom connector, name it The Vault and paste this address:

Open Claude's Add custom connector dialog, filled in

Claude first shows a red notice that the connector came from an external link. That is expected: check that the name is The Vault and the address is https://mtgvault.cards/api/mcp, then press Continue. Seen on a real account on 2026-10-10.

https://mtgvault.cards/api/mcp

Then sign in on the Vault's page and approve. Tick Write only if the assistant may change your collection and decks. A listing in Claude's directory is coming; this page will show the button.

After a Vault update that adds tools: disconnect and connect The Vault again, so Claude reads the new tools.

ChatGPT

In ChatGPT: Plugins → Add → Add custom MCP server, name it The Vault, paste this address and keep OAuth:

https://mtgvault.cards/api/mcp

Then sign in on the Vault's page and approve. Tick Write only if the assistant may change your collection and decks. A listing in ChatGPT's directory is coming; this page will show the button.

After a Vault update that adds tools: ChatGPT reads the tools only when the app is added: delete it (not only uninstall) and add it again.

Perplexity

1. In the Perplexity web app open Connectors (https://www.perplexity.ai/computer/connectors) and choose Custom connector (Remote), then Add MCP connector. It needs a plan that offers custom connectors (the check ran on Pro).
2. Name it The Vault, leave the description optional, set the MCP server URL to https://mtgvault.cards/api/mcp, leave the advanced settings as they are, tick that you understand custom connectors can introduce risks, and add it.
3. Open the connector and press Add connector. Perplexity opens the Vault's page "Connect Perplexity (www.perplexity.ai) to your Vault?": sign in (a passkey, Google and so on; the page shows who is signed in) and press Allow.
4. The connector then shows Connected with the Vault's tools, each with a permission: Disable, Always ask or Allow.
5. Use it in Computer mode and mention the Vault in your question, for example "Using the Vault, what are my most valuable cards?". The connector shows Perplexity's plain plug icon, because Perplexity has no icon field for custom connectors.

https://mtgvault.cards/api/mcp

Seen in a real run on 2026-10-09 on a Pro plan; the documentation of Perplexity was not used. Comet (Perplexity's browser) was not looked at: not verified yet.

Make your assistant use it

An assistant only gives answers from The Vault when it calls The Vault. Claude and ChatGPT show the assistant the names of the Vault's tools, not the instructions that come with them, so a question that does not mention the Vault (“how does trample work against protection?”) can be answered from the assistant's own memory, which can be out of date. Paste this once into a Claude Project's instructions or your preferences, or start a chat with it:

For Magic rules, card text, rulings, decks, prices and my collection, use The Vault's tools before answering, and never quote a rule from memory.

When you see “Used The Vault” in the answer, it came from the tools. If it does not appear, ask again and name the Vault.

Claude Code (plugin: skills and tools together)

/plugin marketplace add colombod-personal/the-vault
/plugin install the-vault@the-vault

It asks for the Vault address (the default is this site) and your token once, and stores the token securely.

Any agent that reads skills (Claude Code, Codex, Cursor, Copilot and more): the skills

npx skills add colombod-personal/the-vault

Add --skill rules-judge for one skill, or -g to install for all your projects. Skills tell your assistant how to answer; pair them with the tools below.

Ready-made agents: a rules judge, a budget deck builder, a buyer, a collection curator

The Claude Code plugin above includes them (the-vault:vault-judge, vault-deckbuilder, vault-buyer, vault-curator); in Claude Code they can only use the Vault's tools. For Codex, Cursor and GitHub Copilot, copy the matching files from agent-definitions into the folder named there; what each tool actually restricts is in the README next to them (Copilot: only the Vault's tools; Codex: the Vault's read-only tools, read-only sandbox; Cursor: read-only mode and instructions only).

Claude Code

Add the server for all your projects, then sign in with your Vault account:

claude mcp add --transport http vault --scope user https://mtgvault.cards/api/mcp
claude mcp login vault

Without browser sign-in: create a personal access token (Account → Agents & API; read-only is enough), keep it in an environment variable named VAULT_TOKEN, and put this in the project's .mcp.json (Claude Code fills in the variable):

{
  "mcpServers": {
    "vault": {
      "type": "http",
      "url": "https://mtgvault.cards/api/mcp",
      "headers": {
        "Authorization": "Bearer ${VAULT_TOKEN}"
      }
    }
  }
}

Inside a session, /mcp does the sign-in too. The plugin above asks for the token once and stores it securely. Format from the tool's own documentation (Claude Code: MCP), read 2026-10-07.

Codex (CLI and IDE extension)

Add the server, then sign in with your Vault account:

codex mcp add vault --url https://mtgvault.cards/api/mcp
codex mcp login vault

Or by hand in ~/.codex/config.toml (Codex uses TOML here, not JSON):

[mcp_servers.vault]
url = "https://mtgvault.cards/api/mcp"

Without browser sign-in: create a personal access token (Account → Agents & API; read-only is enough), keep it in an environment variable named VAULT_TOKEN, and name it in the same table:

[mcp_servers.vault]
url = "https://mtgvault.cards/api/mcp"
bearer_token_env_var = "VAULT_TOKEN"

The CLI and the IDE extension share this configuration. Format from the tool's own documentation (Codex: MCP), read 2026-10-07.

Cursor

In .cursor/mcp.json (this project) or ~/.cursor/mcp.json (all projects); Cursor documents OAuth for servers that need it; if it shows no sign-in, use the token block below:

{
  "mcpServers": {
    "vault": {
      "url": "https://mtgvault.cards/api/mcp"
    }
  }
}

Without browser sign-in: create a personal access token (Account → Agents & API; read-only is enough), keep it in an environment variable named VAULT_TOKEN; Cursor fills in the variable:

{
  "mcpServers": {
    "vault": {
      "url": "https://mtgvault.cards/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VAULT_TOKEN}"
      }
    }
  }
}

The root key is mcpServers. Format from the tool's own documentation (Cursor: MCP), read 2026-10-07.

VS Code (GitHub Copilot)

Add The Vault to VS Code (VS Code's own install link; not tried on a real VS Code yet)

In .vscode/mcp.json (or run “MCP: Open User Configuration” for all workspaces); VS Code documents OAuth for servers that need it; if it shows no sign-in, use the token block below:

{
  "servers": {
    "vault": {
      "type": "http",
      "url": "https://mtgvault.cards/api/mcp"
    }
  }
}

Without browser sign-in: create a personal access token (Account → Agents & API); VS Code asks for it once, hides it and stores it:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "vault-token",
      "description": "The Vault personal access token",
      "password": true
    }
  ],
  "servers": {
    "vault": {
      "type": "http",
      "url": "https://mtgvault.cards/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:vault-token}"
      }
    }
  }
}

The root key is servers here, not mcpServers. Format from the tool's own documentation (VS Code: MCP servers, VS Code: MCP configuration reference), read 2026-10-07.

GitHub Copilot CLI

Add the server:

copilot mcp add --transport http vault https://mtgvault.cards/api/mcp

Or by hand in ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "vault": {
      "type": "http",
      "url": "https://mtgvault.cards/api/mcp",
      "tools": [
        "*"
      ]
    }
  }
}

Without browser sign-in: create a personal access token (Account → Agents & API). In a Copilot CLI session run /mcp add, choose HTTP, enter the address above and type this into the HTTP Headers prompt (not into a command):

{
  "Authorization": "Bearer vault_pat_..."
}

The Copilot CLI documentation we read describes headers for remote servers and does not describe a browser sign-in, so this block uses the token. Format from the tool's own documentation (GitHub Docs: add MCP servers to Copilot CLI), read 2026-10-07.