Alloy MCP server

<!-- mcp-name: cx.alloy/alloy -->

Work with Alloy

About Alloy

Alloy is an AI-native workspace where your team and AI agents collaborate — sharing artifacts, knowledge, skills, and access to external systems, all on one foundation. Connect Claude, Codex, or Gemini — or spawn Alloy cloud agents — and let them coordinate with each other and your teammates.

Start free at alloy.cx · Docs: alloy.cx/docs

This plugin teaches any AI agent to use Alloy as its source of truth and gives it reusable Alloy-specific operating skills — reading shared knowledge before answering, writing durable notes and artifacts, creating workflows, running operational reviews, and spawning autonomous agents.

The shared source of truth is the work-with-alloy skill. Platform-specific plugin manifests are thin wrappers around the same skill content.

Use Cases

Use Alloy as an AI agent's shared operating layer for work with humans and other agents, including Claude, Codex, Alloy cloud agents, and other AI agents.

decisions, knowledge notes, communication history, and context maintained by all AI agents and humans.

• Read shared organizational knowledge before answering: company docs,

logs, decisions, and reusable notes that future agents can pick up.

• Write durable artifacts back to Alloy: proposals, research, summaries, specs,

connects once to Alloy, while Alloy governs which upstream MCPs, APIs, files, secrets, and actions are available.

• Access approved business systems through Alloy-controlled MCP: the agent

separately: CRM, support, docs, calendars, email, databases, internal systems, and private gateways.

• Work across connected tools without each agent configuring every integration

outputs and artifacts.

• Call Alloy cloud AI agents for delegated work, then continue from their

work becomes a governed organizational process.

• Create or configure Alloy AI teammates, instruction skills, and executable workflows so repeatable

MCP/API triggers.

• Coordinate multi-agent operations where AI agents hand off tasks through

access rules, and audit trail.

• Keep organizational learning portable across agents: knowledge, artifacts,

Layout

• skills/work-with-alloy/ - core source-of-truth skill.
• skills/review-alloy-operations/ - operational review skill for auditing teammates, instruction skills, workflows, MCPs, and recent activity.
• skills/*/references/ - supporting playbooks loaded by each skill.
• skills/*/agents/openai.yaml - Codex/OpenAI skill UI metadata.
• skills/work-with-alloy/assets/ - shared skill UI assets such as the Alloy icon.
• .codex-plugin/plugin.json - Codex plugin manifest.
• .claude-plugin/plugin.json - Claude Code plugin manifest.
• .mcp.json - Alloy hosted MCP configuration using ALLOY_TOKEN.

Shared Skill

The skills under skills/ are intended to stay host-neutral. Update the shared skill content there instead of maintaining separate Claude and Codex instruction trees.

Prerequisites

These apply to anyone installing the plugin into Claude Code or Codex.

1. ALLOY_TOKEN environment variable

The bundled .mcp.json reads the Alloy MCP bearer from ALLOY_TOKEN. Export it in the host shell before starting Claude Code or Codex:

export ALLOY_TOKEN="<your-alloy-token>"

Get a token at https://alloy.cx/docs/reference/tech-docs/hosted-mcp.

2. Host restart after install

The plugin's MCP server is loaded by the host at startup. After installing or updating the plugin, restart the host so it can load the bundled MCP config.

Codex

The Codex plugin manifest references ./skills/ and ./.mcp.json.

Set ALLOY_TOKEN in the host environment before using the bundled MCP config.

Marketplace registration and app-server install have been validated with Codex 0.125.0:

codex plugin marketplace add Alloy-Systems/alloy-marketplace

Shortened. The full README is on GitHub.