Connect your AI agents to Alloy

Use Claude, Codex, Gemini, or Cursor as Alloy AI teammates — with full access to your workspace knowledge, tools, and shared context.

Recommended

Install the Alloy plugin

For Claude Code and Codex, install work-with-alloy from the Alloy marketplace. One command wires up the hosted-MCP connection and the work-with-alloy skill — so your agent doesn’t just call Alloy’s tools, it learns to read shared knowledge first and write durable artifacts back as it works.

  1. 1

    Set your Alloy token

    Open your AI teammate in Alloy, go to the PATs tab, and create a token. Export it in the shell you launch Claude Code from — the plugin’s bundled MCP reads it from ALLOY_TOKEN. Open Alloy
    export ALLOY_TOKEN="<your-alloy-token>"
  2. 2

    Add the marketplace and install the plugin

    Run these in Claude Code. The first registers the Alloy marketplace, the second installs work-with-alloy — the Alloy MCP connection plus the source-of-truth skill.
    /plugin marketplace add Alloy-Systems/alloy-marketplace
    /plugin install work-with-alloy@alloy-marketplace
  3. 3

    Restart and verify

    Restart Claude Code so it loads the bundled MCP, then run claude mcp list — you should see plugin:work-with-alloy:alloy connected. The work-with-alloy skill is now active.

Manual setup — any MCP client

Any MCP-compatible agent — Gemini CLI, Cursor, and others — can connect to Alloy’s hosted endpoint directly with a bearer token. Claude Code and Codex can use this path too if you’d rather wire up the raw MCP connection without the plugin.

How it works: Alloy hosts an MCP server for each AI teammate. External agents connect to it using a bearer token — from that point on, they act as that teammate: same tools, same knowledge, same permissions.
  1. 1

    Get your MCP config from Alloy

    Open your AI teammate in Alloy, go to the PATs tab, and create a token. Alloy generates a ready-to-paste config — copy it. Open Alloy
  2. 2

    Add to your Claude Code settings

    Paste the config into ~/.claude/settings.json under the mcpServers key. If the file or key doesn’t exist yet, create it using the template below.
    {
      "mcpServers": {
        "alloy": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@latest",
            "https://api.alloy.cx/mcp",
            "--header",
            "Authorization: Bearer ${ALLOY_TOKEN}"
          ],
          "env": {
            "ALLOY_TOKEN": "YOUR_TOKEN"
          }
        }
      }
    }

    Replace YOUR_TOKEN with the token you copied from Alloy.

  3. 3

    Verify the connection

    Run claude mcp list — you should see alloy listed. Start a new Claude Code session and ask your AI teammate something — it will respond as that Alloy teammate.
  4. 4

    Add the work-with-alloy skill (recommended)

    The MCP connection gives your agent Alloy’s tools — the work-with-alloy skill is what teaches it to read shared knowledge first and write durable artifacts back. Grab the host-neutral skill from the plugin repo and drop it into your agent’s skills directory. View the repo
    git clone https://github.com/Alloy-Systems/work-with-alloy.git
    # Copy the skill into your agent's skills directory.
    # Claude Code example:
    cp -r work-with-alloy/skills/work-with-alloy ~/.claude/skills/

    Clients without a skills folder can load skills/work-with-alloy/SKILL.md as a rules or system-prompt file.