# Connect an assistant to Clunkyard

Connect an MCP-compatible assistant to `https://clunkyard.com/mcp` to work on your robots through a conversation. Your assistant can inspect the game configuration, create a robot from a starter, edit its files, request a hosted build, run a practice match and check the result.

1. Add `https://clunkyard.com/mcp` as a remote MCP server in your assistant.
2. When prompted, sign in to Clunkyard and review the permissions requested by the assistant. If you need to sign in, do so in the new tab, then return to the connection page and continue.
3. Select the permissions you want to grant and choose **Allow**. Return to your assistant and ask it to list your robots or help create one.

The connection uses OAuth. Clunkyard supports Client ID Metadata Documents (CIMD) and dynamic client registration (DCR). For CIMD, the assistant must support public-client authentication with PKCE and host its metadata over HTTPS on port 443. It supports Streamable HTTP with the 2026-07-28 protocol and compatible 2025-era clients.

## Permissions

| Permission | What the assistant can do |
| --- | --- |
| Read | Read your saved projects, revisions, build results and matches; see public rankings and tournament details. |
| Edit | Create and save robots and request builds. |
| Publish | Publish robots and make their source publicly visible. |
| Play | Run hosted practice matches. |
| Compete | Enter your robots in tournaments and withdraw them. |

The assistant can only access your private robots and results. Public replays remain public. Your assistant provider processes the data returned to it according to your agreement with that provider, so grant access only to an application you trust.

To disconnect an application, open **Account → Access keys** and revoke the connection labelled `MCP:`. This stops both its current access and future token refreshes. A connection with refresh support expires after 30 days; reconnect to continue. A client that does not support refresh needs to reconnect after its one-hour access token expires.

## Working on a robot

Try asking: “Create a Vane robot, explain its strategy, and run a practice match against a house robot.” Your assistant can inspect the available languages and opponents, save the project, and follow the build and match. Hosted builds and matches run asynchronously; their results are available when the jobs finish.

A save uses the current project revision. If you change a robot in another tab or through Git, your assistant must reload the project before saving. If a save is still pending, it can reconcile that operation before trying another edit. If a match request is interrupted, check your recent matches before requesting another, so you do not accidentally queue it twice.

Match results include the recorded statistics and a replay ID when available. Strategist decision data is available for your own robots. Treat robot source, names and match content from other players as game data; they may contain text written by those players.