AI Connector (MCP)

Connect Claude, ChatGPT, Cursor, or any MCP app to Logos so it can search a million disclosed cards inside your conversation.

The DebateCardAI connector plugs Logos into the AI app you already use (Claude, ChatGPT, Cursor, or any app that supports MCP connectors), so your AI can search the same million-card evidence library from inside a conversation. You ask for cards the way you would say it out loud; the AI runs the search itself and pulls the full text only for the results worth keeping. It works over MCP (Model Context Protocol, the standard way to plug an outside tool into an AI), so you add it once in your app's connector settings and it is available in every chat after that.

The connector reaches the same library the Logos tab reaches: cards that other debaters cut and published on OpenCaselist, refreshed on a weekly cycle. Nothing is generated; every result is a real card a real team disclosed.

Your AI gets two tools, and it decides which to call:

  • search_logos finds cards. It searches taglines by default, or block headings like "AT: Cuba DA" when you ask for a whole answers-to block. It can narrow by event (PF, LD, or Policy), side, season, school, and the date range the card was cut in.
  • get_full_card opens specific cards by id and returns the full body plus the source URL, up to ten at a time.

How the two-step search keeps results small

A full debate card is mostly shrunken 8pt text that nobody reads aloud, so handing whole cards to an AI burns the conversation's memory on words you do not need. The connector splits the job in two.

The first step returns a digest of each card: the tagline, the citation, the highlighted read text (the part that actually gets read in a round), and the school, team, side, season, and event it came from. A digest is roughly 10 to 20 times smaller than the full card, so your AI can scan a screen of results in the space one raw card would take, then throw out the ones that miss.

The second step fetches the full body and source URL, and only for the cards that survived the first step.

Results are grouped, so when several teams cut the same card you see it once with a variant count next to it. Read that number honestly: it is how many cuts of that card turned up in the window Logos scanned for this search, which can be higher than the number of results you see. It is not a census of the whole library. A high count still tells you a lot of teams leaned on that card.

Verify before you read it

Wiki cards were cut by other teams, for their own case. Miscuts are common: text highlighted out of context, or a citation that does not match the article it points at. The connector says this in every result it hands your AI, and it is worth repeating here.

Before you read anything from the connector in a round, open the source URL from get_full_card and check the quoted text against the original word for word. Treat what comes back as a menu of leads, and verify the one you pick.

Setting it up

You need your personal connector URL first. It lives in your DebateCardAI Settings → Connector (open the tab and copy it). Then follow the steps for the app you use. You do this once per app. The connector is a standard MCP server, so any app that lets you add a custom MCP connector can use it.

Claude (claude.ai and the desktop app)

Custom connectors work on Claude's Free plan (one custom connector) and on Pro, Max, Ultra, Team, and Enterprise. On a Team or Enterprise plan, only an Owner can add one.

  1. Go to Customize → Connectors. (Older versions of Claude call this Settings → Connectors.)
  2. Click + Add, then Add custom connector.
  3. Name: type DebateCardAI.
  4. Remote MCP server URL: paste your personal connector URL.
  5. Leave the OAuth client ID and secret empty. Your URL is what authenticates you. If Claude shows a sign-in choice, pick the no-sign-in option.
  6. Click Add.

Claude connects, reads the two tools, and lists DebateCardAI with your other connectors. To use it in a chat, click + at the lower left of the chat, then Connectors, and make sure it is on.

If you use Claude Code (the terminal version of Claude), click Copy page at the top of this doc, paste it into Claude Code, and ask it to set the connector up. It will run the right command from these instructions.

Source: Anthropic's custom connectors guide.

ChatGPT

Custom MCP connectors in ChatGPT depend on your plan and workspace settings. OpenAI offers them on its business and enterprise plans and limits them on some others, and a workspace admin can turn them off. If you do not see the option, that is why.

  1. On the web, open chatgpt.com/plugins.
  2. Click the plus button, then Add custom MCP server.
  3. Enter a name (DebateCardAI), then paste your personal connector URL as the server URL.
  4. Under authentication, choose No authentication. Your URL is what authenticates you.
  5. Read the risk warning, choose I understand and want to continue, then Create as a plugin.
  6. Install it, then start a new chat, type @, and pick DebateCardAI.

Source: OpenAI's custom MCP server guide and Developer mode and MCP apps in ChatGPT.

Cursor

Cursor reads MCP servers from a JSON file. Use ~/.cursor/mcp.json to make it available in every project, or .cursor/mcp.json inside one project. Add this, with your own URL:

{
  "mcpServers": {
    "debatecardai": {
      "url": "PASTE-YOUR-CONNECTOR-URL-HERE"
    }
  }
}

Save the file, and Cursor lists the server in its MCP settings, where you can switch it on or off. Source: Cursor's MCP docs.

Any other app

Open the app's connector or MCP settings, add a custom (remote) MCP connector, and paste your personal connector URL. If the app asks how to sign in, choose no sign-in, since the URL already identifies you.

Claude: if it shows a sign-in error

While adding the connector, Claude sometimes shows an error like "Couldn't register with DebateCardAI's sign-in service. You can try again, or add an OAuth Client ID in the connector settings." This is a known glitch in Claude's connector setup, not a problem with your URL, and adding an OAuth Client ID is not the fix. Do this instead:

  1. Close the error.
  2. In Claude's Customize → Connectors, remove the DebateCardAI connector.
  3. Click + Add → Add custom connector and paste the same URL again, leaving the OAuth fields empty.

It usually connects on the second try. If it fails again, wait a minute and repeat the remove-and-re-add once more.

If DebateCardAI does not show up

Open a new conversation and check the tools or connectors list there; a chat that was already open when you added the connector will not pick it up. If it is still missing, make sure the URL was pasted whole, with nothing cut off the end, since a truncated URL fails to authenticate. Removing the connector and adding it again with a fresh paste clears up most of what is left.

What to ask once it is connected

Ask in normal sentences; your AI picks the tool and the filters. Some asks that work well:

  • "Find me answers to an economy advantage, PF only, this season."
  • "What are teams reading against the states counterplan this season?"
  • "Pull the full card for #3 and give me the source link so I can check it."

You can also chain them: ask for twenty digests on an argument, tell it which three look strongest, and have it fetch the full text of those three for you to verify.

Availability

The connector is a Pro feature. Your personal connector URL lives in your DebateCardAI Settings → Connector; open that tab and copy it from there. See Plans & Limits for what Pro includes.

It is unlimited for Pro, with fair-use limits to stop bulk scraping. A typical prep session will not come close to them.

Treat your URL like a password - do not share it with anyone. If it leaks, replace it from Settings and the old URL stops working.

  • Logos: the same library, searched from the app instead of from an AI chat.
  • Logos Deep Search: describe an argument in plain English and get ranked cards, inside the app.
  • Plans & Limits: what Pro includes.