Work With Alloy

MCP文档知识

提供方 Alloy-Systems

文档知识 未标注 API Key 社区 / 第三方 ClaudeCursorGemini CLICodex

Alloy is an AI-native workspace where teams and AI agents share knowledge, artifacts, workflows, and controlled access to external systems through one common operating layer.

一句话选型结论

按资料字段整理

Work With Alloy 属于文档知识类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、Gemini CLI 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

mcpworkspaceagents

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Gemini CLI,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Work With Alloy当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Alloy-Systems上游标注的维护方 Alloy-Systems
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

7.4 KB
来自项目仓库与上游目录的原文,未做删改

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&#x27;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:```bash
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&#x27;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.&quot;https://github.com/&quot;.insteadOf &quot;git@github.com:&quot;
  ```

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

  1. Work happens on feature branches, merged into main via PR.
  2. 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.
  3. Cut a git tag on the merge commit: git tag vX.Y.Z &amp;&amp; git push origin vX.Y.Z.
  4. 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.
  5. 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.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Work With Alloy 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Work With Alloy 怎么在 Claude、Cursor、Gemini CLI 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Work With Alloy 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Work With Alloy 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Work With Alloy 支持哪些客户端?

资料标注支持 Claude、Cursor、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Work With Alloy 能提供哪些能力?

资料显示能力标签包括 mcp、workspace、agents、knowledge、workflow。具体工具清单以官方文档为准。

Work With Alloy 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。