texttcgSign in
Blog

Point your agent at your collection

Your texttcg collection isn't just yours to browse — it's yours to automate. Every account can mint personal API tokens, and the whole product is exposed to agents two ways: plain HTTP docs your agent can read, and first-class MCP tools it can call. Here's the zero-to-working setup with the Claude CLI, though any MCP client works.

Step 1 — Mint a token

Head to Settings → Agent and create a personal API token. It's shown once — copy it somewhere safe. The token IS your account (everything it does happens to your collection), so treat it like a password; you can revoke it from the same tab anytime. Agent access rides your subscription — either tier.

Step 2 — Paste it into Claude

The zero-setup way:you don't have to configure anything at all. Open the Claude CLI and just tell it to hit our API for you:

Read https://texttcg.com/api/agent and use my texttcg token for every request
(Authorization: Bearer ttcg_YOUR-TOKEN-HERE) — then add OP01-001
to my collection for $5.

Claude reads the self-documenting API and makes the HTTP calls itself — nothing to install or register. There's a paste-ready version of that prompt (drop your token in, copy, go) at texttcg.com/agent.

Prefer first-class tools? One command registers texttcg's MCP server instead — drop your token in where the placeholder is:

claude mcp add --transport http texttcg https://texttcg.com/api/mcp \
  --header "Authorization: Bearer ttcg_YOUR-TOKEN-HERE"

Claude then sees tools like add_card, list_cards, search_catalog, and sell_card— plus the shopping list, price alerts, and the rest. Not on Claude? Any MCP client takes the same URL and header, and either path lands on the same API, scoped to your token's account.

Step 3 — Just talk

From here you don't write API calls — you say collection things in your own words, and your agent parses them and hits our MCP with the structured version. Try:

The agent does the parsing — names, numbers, prices, tags — and calls the right tool with the right arguments; our side resolves cards against the catalogs exactly like the texting bot does. Anything it logs shows up in your portfolio immediately, and everything is scoped to the token's account — an agent can never touch anyone else's collection.

Full API reference (endpoints, fields, the MCP tool list): https://texttcg.com/api/agent — readable by you or your agent, no auth needed for the docs themselves.