Connect a board to Claude and talk to it in plain English.
Every list can hand out one extra link that turns it into an MCP connector. Paste that link into Claude once, and it can read the board and run it for you — what is still open, who has not finished anything, give the Maple St blocks to Dana, add three more items, lock it.
Connect it
On your organizer page, find Connect to AI in the panel beside
the board and press Create the link. You get a URL ending in
/mcp.
Open Settings → Connectors, choose Add custom connector, and paste the link. There is no sign-in step, no API key and no OAuth — see below for why that is deliberate.
Claude sees which list it is attached to, what is on it and what it may do. You do not have to learn any commands.
What it can do
Not a read-only view: a connector holds exactly what
/m/… holds over that one list, because withholding half of it
would only be surprising — the link already grants all of it through the
page.
view_list
add_items
assign_items
release_items
mark_items
remove_items
set_list_state
update_settings
A model handed a bare URL will try to fetch it like a web page, get a JSON-RPC error back and tell you the link is broken. It has to be told what the link is.
So the link travels with a prompt, and that is the button on top of the connector card: Copy prompt for AI. It is written to the assistant rather than to you — it names the URL as an MCP endpoint, says to connect and list the tools rather than fetch it, notes that no authentication is expected, and describes what the tools do. Paste it into a chat and it knows what it has been handed.
The steps above are the other route: adding it in Settings makes it a connector you keep, rather than something you hand over one conversation at a time. The raw endpoint is folded under How to connect it for anyone wiring it up by hand.
The capability lines in it are generated from the connector's own tool list, so the prompt cannot describe something the server does not do.
In practice
Most connectors ask you to sign in because the server needs to know which account is calling. There are no accounts here. A list is addressed by secrets in a URL, and the URL is the credential — that is true of the link you give volunteers, true of your organizer page, and true of the connector.
So there is nothing for a sign-in to establish. Claude will tell you the connector needs no authentication; that is the design working, not a piece of setup you have skipped.
What it means in practice is the thing worth taking seriously: anyone holding that link can run the list. Treat it exactly like your organizer link.
No. There are no accounts anywhere in yoink.team, so there is nothing to sign in to. The connector link itself is the credential — the same way the organizer link is. Claude will report the connector as needing no authentication, which is correct rather than a warning about something missing.
It is the same decision as pasting your organizer link into any other application: whoever holds it can run the list. That is why the connector is a separate link you mint on purpose, and why you can regenerate or turn it off in one click without disturbing your organizer link or the link your volunteers hold.
No. A connector link resolves to exactly one list, and no tool takes a list parameter — there is nothing for a model to fill in that would point it somewhere else. One list, one link.
Not with their link. The connector is minted from the organizer page and grants organizer powers, so it is yours to hand out deliberately. The volunteer link does nothing at the connector address, and the connector link opens no page.
The previous URL stops working immediately and anything using it loses access. That is what makes it a real remedy for a link that has gone somewhere it should not have.
Yes. It is a standard MCP server over HTTP, so any MCP client can connect to it. Claude is the one most people have.
It is a standard MCP server over HTTP at
/m/<connector token>/mcp, speaking both the
initialize handshake and the newer
server/discover revision. Any MCP client can talk to it.
An unknown token answers 404 rather than 401,
deliberately: a 401 would send a client hunting for an
authorization server that does not exist.
Make a list first — the connector is minted from its organizer page. How the two links work.