← The packet · 10 of 14The Field Guide
NO ONE WORKS HEREPaul Cheek
PARADE.PAULCHEEK.COM  •  PAUL@CHEEK.ORG
01110000 01100001 01110010 01100001 01100100 01100101PARADE WEEK / Cheat sheets
Cheat Sheet: Connecting Your Agent ·  © Cheek LLC 2026
Parade Week Packet  ·  Cheat sheets

Cheat Sheet: Connecting Your Agent

Every company system is an MCP server at one URL. This page gets any agent connected in about three minutes per system.

The URL pattern

https://parade.paulcheek.com/mcp/<system>/<join-code>

The host is on the room screen. The join code is printed on your team card: it is the credential, so treat it like one. The systems and their path segments:

System Path segment
AirBook CRM crm
AirWare ERP 4.7 erp
FloatDesk support
AirMail comms
The Breeze social
Balloon Payments finance
The Gary Graph gary

Your team card lists which systems are yours. Every team has AirMail and the Gary Graph.

Connecting on claude.ai

  1. Sign in to claude.ai with your program seat.
  2. Create your team's Project and name it after your department (for example: Customer Ops Agent, Grand Inflation).
  3. Open Settings, then Connectors, then Add custom connector. Paste your team's URL for the system. No OAuth, no keys: the join code in the URL is the whole handshake.
  4. Repeat for each system on your team card.
  5. Paste your completed Agent Role Definition into the Project instructions. Design before build: the ARD comes first, always.
  6. Verify: ask the agent to list its tools, then to pull one real record (a ticket, an account, a batch, the helium ledger). If it can do both, you are live.

Claude Desktop

Works identically. Same URLs, same connector flow, nothing extra to set up for the lab.

Managed agents (shared credential vault)

If your platform wraps connectors in a managed-agent credential vault, it will run an authorization step when you add each system. This is automatic: the servers speak OAuth and auto-approve, so the vault completes and stores a credential without any login, and without you pasting a key. The join code in the URL is still the whole credential — the authorization is just a formality the vault requires. If the vault ever prompts you to paste a key, you can leave it blank; the URL is enough.

Any other platform

MCP is an open standard. Any client that speaks MCP over streamable HTTP connects with the same URLs: another vendor's agent builder, an orchestration framework, or a bare SDK. The servers are stateless JSON-RPC over POST (initialize, tools/list, tools/call), with no auth handshake beyond the URL itself.

When it does not work

Symptom What it means The fix
401 invalid join code Typo in the URL, or your team was frozen from the Tower Retype the code from your team card, character by character. Still failing: flag the facilitator
403 team does not have access Working as designed: that system is not in your charter You are not missing a permission; you are missing a teammate. The information moves over AirMail, so ask the team that owns the system
Connected but no tools The client cached a failed handshake Remove the connector entirely and add it again fresh
"Authorization failed" in a managed-agent vault The vault cached an authorization attempt from before OAuth was available, or mid-deploy Remove the connector and add it again; the authorization now auto-approves. Any "paste a key" prompt can be left blank
Tools work, but the world never changes The clock is paused, by design outside live play Nothing is broken. Ask the facilitator if you believe the world should be moving

Rule of thumb: the URL is the entire configuration. If something is wrong, it is almost always the URL.

← Worksheet: The Tool vs Teammate MapCheat Sheet: Prompting Patterns for Agent Builders →
© Cheek LLC 2026