Alloy

Name: Alloy
Author: Alloy-Systems

by Alloy-Systemsversion 1.0.0i★ –iRuns in the cloud

Registry namecx.alloy/alloy

Install

Overview

Description from the maker (original English)

AI workspace — shared knowledge, skills, and tools for AI agents

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Search & AI memory
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http alloy https://api.alloy.cx/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "alloy": {
      "url": "https://api.alloy.cx/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "alloy": {
      "type": "http",
      "url": "https://api.alloy.cx/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Bearer token from your Alloy AI teammate's PATs tab (format: Bearer )

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain alloy.cx (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 5654 servers in this category
Published to the registry more recently than 17% of the other 5654 servers in this category
Basic checks equal to or better than 100% of the other 5654 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Alloy safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Read shared organizational knowledge before answering: company docs, decisions, knowledge notes, communication history, and context maintained by all AI agents and humans.
Write durable artifacts back to Alloy: proposals, research, summaries, specs, logs, decisions, and reusable notes that future agents can pick up.
Access approved business systems through Alloy-controlled MCP: the agent connects once to Alloy, while Alloy governs which upstream MCPs, APIs, files, secrets, and actions are available.
Work across connected tools without each agent configuring every integration separately: CRM, support, docs, calendars, email, databases, internal systems, and private gateways.
Call Alloy cloud AI agents for delegated work, then continue from their outputs and artifacts.
Create or configure Alloy AI teammates, instruction skills, and executable workflows so repeatable work becomes a governed organizational process.
Coordinate multi-agent operations where AI agents hand off tasks through MCP/API triggers.
Keep organizational learning portable across agents: knowledge, artifacts, access rules, and audit trail.

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

Codex installs work-with-alloy from the marketplace entry pointing at a tagged release. After install, Codex reports the plugin as enabled and exposes the work-with-alloy:work-with-alloy skill plus the bundled alloy MCP server.

Claude Code

The Claude plugin manifest at .claude-plugin/plugin.json references the same ./skills/ and ./.mcp.json as the Codex side. Install flow once the Alloy marketplace is published:

/plugin marketplace add Alloy-Systems/alloy-marketplace

/plugin install work-with-alloy@alloy-marketplace

Claude Code's plugin installer clones plugin source from GitHub over SSH by default. Before /plugin install, make sure one of these is true:

A working GitHub SSH key on this machine (test: ssh -T git@github.com).
A global git URL rewrite that pushes plugin clones through HTTPS:

  git config --global url."https://github.com/".insteadOf "git@github.com:"

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

After install, restart Claude Code and confirm registration:

claude mcp list   # expect plugin:work-with-alloy:alloy as connected

Versioning policy

This project follows semantic versioning with synchronized releases across Claude Code and Codex wrappers. A single version applies to the whole release: the shared skill content in skills/work-with-alloy/, both plugin.json manifests, the .mcp.json config, and this README. Both .codex-plugin/plugin.json and .claude-plugin/plugin.json always carry the same version field.

Semver semantics for this plugin

Bump	What it means	Examples
Patch (`0.1.0` → `0.1.1`)	Cosmetic only. Typo, wording tweak, broken link, clarification. No change in how the agent behaves.	Fix a typo in `SKILL.md`. Update a stale URL in `references/`.
Minor (`0.1.0` → `0.2.0`)	Backward-compatible addition. New rule, new Quick Reference row, new reference playbook, new optional manifest field. Prior usage still works.	Add a new rule to Core rules. Add a new entry to a Quick Reference table. Add a new playbook under `references/`.
Major (`0.x` → `1.0`, `1.x` → `2.x`)	Breaking change. A canonical path, file name, required field, or required rule changes in a way that prior consumers may break.	Rename `Personal/ /.knowledge/knowledge.md` to a different path. Remove a Core rule. Restructure `references/` so existing links break.

Pre-1.0 (0.x) signals "still stabilizing - minor bumps may include breaking changes". The 1.0.0 line will be cut when the canonical paths and Core rules are confirmed stable.

Release flow

Work happens on feature branches, merged into main via PR.
When main is in a state worth releasing, bump both .codex-plugin/plugin.json and .claude-plugin/plugin.json version fields in the same commit.
Cut a git tag on the merge commit: git tag vX.Y.Z && git push origin vX.Y.Z.
Bump the corresponding ref field in the Alloy-Systems/alloy-marketplace repo's marketplace.json entry for work-with-alloy. Users receive the new version through /plugin update only after this marketplace bump.
Untagged commits on main are visible to anyone reading the repo but are not delivered through /plugin install or /plugin update until the marketplace points at a new tag.

Cadence

Tags are cut per logical release, not on every commit. A typical trigger is a new Core rule landing, a new reference playbook being added, or a breaking restructure being completed and ready to ship. Cosmetic-only changes can accumulate in main and be released as a patch bump when convenient.

License

Apache License 2.0.

Alloy

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Work with Alloy

About Alloy

Use Cases

Layout

Shared Skill

Prerequisites

1. ALLOY_TOKEN environment variable

2. Host restart after install

Codex

Claude Code

Versioning policy

Semver semantics for this plugin

Release flow

Cadence

License

1. `ALLOY_TOKEN` environment variable