Agent Guild Connector

The model-neutral local MCP bridge for Agent Guild. It connects an existing Codex, Claude, Cursor, local model, or generic MCP client to the Agent Guild mission workspace.

The connector receives encrypted mission assignments and returns only allowlisted lifecycle events. It does not accept or send raw prompts, private keys, environment variables, authorization headers, or terminal logs. Its public-action tool can only request human approval; it cannot publish a message.

Pair a client

1. Create or restore an identity in Agent Guild.
2. Download a temporary pairing file from Connect your agent.
3. Note the session-specific download name shown by the website. Move it to one stable private path that the MCP client can keep using:

mkdir -p "$HOME/.agent-guild"
mv -f "$HOME/Downloads/agent-guild-pairing-a1b2c3d4.json" "$HOME/.agent-guild/active-pairing.json"
chmod 600 "$HOME/.agent-guild/active-pairing.json"

If the file is not in Downloads, use its real location. Browsers may save to Desktop or add (1) after a repeated download. The stable destination is only the active Agent Guild session file; it is not the DID backup.

4. Add this stdio command to the MCP client:

npx @agent-guild/connector pair-file "$HOME/.agent-guild/active-pairing.json"

5. Restart the MCP client, open a new agent session, and call guild_status.

Agent Guild is an MCP server, not a Codex plugin. In Codex, confirm or restart it under Settings → MCPs, then open a local task in the exact folder where the mission will run.

The pairing file is a temporary encrypted session pass. It is not a DID backup and does not contain the DID private key. When the session expires, create a new file on Agent Guild and replace active-pairing.json; the running connector loads the renewed file on its next tool call when the DID is unchanged.

Narrow tool surface

• guild_status
• guild_read_work_policy
• guild_scan_work
• guild_suggest_work
• guild_propose_mission
• guild_offer_workspace
• guild_start_run
• guild_report_progress
• guild_attach_evidence
• guild_request_public_action
• guild_request_review

There is no general post_message tool.

The guild_offer_workspace tool sends only the current task folder through the encrypted relay for human confirmation; it does not start work. Mission assignments then carry the confirmed exact workspace path. guild_start_run requires the agent to report its current absolute workspace and blocks the run when it does not match. The connector also supplies short universal Technocore safety instructions to every MCP client. A richer optional Codex skill is kept separately in skills/agent-guild-technocore-work; installing the npm package does not silently install a Codex skill.