nexus-mcp
MCP server for the Plugin Federation Nexus control plane, enabling coding agents and humans to inspect catalogs, plugins, proposals, and run governance actions via GitHub SSO or OIDC.
README
nexus-mcp
TypeScript MCP server for the Plugin Federation Nexus control plane. Coding agents and humans can inspect catalogs, judge opinions, plugins, proposals, and run governance writes — without pasting long-lived Nexus API tokens.
MCP protocol
| Item | Value |
|---|---|
| Spec revision | 2026-07-28 (stateless modern core) |
| TypeScript SDK | @modelcontextprotocol/server@^2 (MCP SDK v2) |
| Schema validation | Zod v4 (zod/v4) |
| Transport | stdio (primary); protocol versions advertised include modern + 2025-era fallbacks |
Configured in src/mcp-protocol.ts via
supportedProtocolVersions (modern 2026-07-28 first).
Security model
| Identity | How it authenticates | Nexus credential |
|---|---|---|
| Human (Cursor, Claude Desktop, local agent) | GitHub SSO — device flow (GITHUB_OAUTH_CLIENT_ID) or existing gh auth login session |
Short-lived Nexus JWT via provider: github_user (memory only) |
| GitHub Actions / coding agents in GitHub | GitHub OIDC (permissions: id-token: write) + tenant OIDC trust policy |
Short-lived Nexus JWT via provider: github_actions (memory only) |
Not supported (by design):
NEXUS_ACCESS_TOKEN/NEXUS_BEARER_TOKEN(static control-plane secrets)- Gateway enrollment / workload / bootstrap credential tools
- Recording tool catalogs or analyses from chat (CI + OIDC Actions own evidence)
Nexus remains the only issuer of API JWTs (ADR 0008).
Tools (v0.1)
Orientation: get_session, get_tenant, list_pipeline_checks
Plugins: list_plugins, create_plugin, get_plugin_draft, replace_plugin_draft,
compose_plugin_draft, list_plugin_variants, list_plugin_revisions
Quality: get_tool_catalog, list_tool_analyses, list_tool_judges,
get_tool_judge, create_tool_judge, update_tool_judge,
get_latest_schema_verification, summarize_source_quality,
find_fix_suggestions_for_tool
Governance: get_proposal, create_proposal,
create_proposal_from_schema_verification, decide_proposal (confirm),
release_plugin_revision (confirm), promote_plugin_revision (confirm)
Exports: get_compatibility_report, create_export, get_export_job
Audit: list_audit_events
Setup
npm install
npm run build
Environment
| Variable | Required | Purpose |
|---|---|---|
NEXUS_URL |
yes | e.g. https://api.nonprod.plugin-federation.com |
TENANT_ID |
Actions OIDC | Tenant UUID matching OIDC trust policy; also preferred tenant for multi-membership humans |
NEXUS_OIDC_AUDIENCE |
Actions | Must match Nexus NEXUS_OIDC_GITHUB_AUDIENCE (defaults to NEXUS_URL) |
GITHUB_OAUTH_CLIENT_ID |
humans (device flow) | Public OAuth App client id for device flow |
NEXUS_MCP_ALLOW_GH_CLI |
no | Default true — use gh auth token when device flow client id unset |
NEXUS_MCP_GITHUB_USER_TOKEN |
no | Optional GitHub user OAuth token injected by a host (still exchanged; never a Nexus JWT) |
Human (local)
# Option A: GitHub CLI already SSO'd
gh auth login
export NEXUS_URL=https://api.nonprod.plugin-federation.com
export TENANT_ID=<optional-preferred-tenant>
npx tsx src/index.ts
# Option B: device flow
export GITHUB_OAUTH_CLIENT_ID=<public-oauth-app-client-id>
npx tsx src/index.ts
# Follow the verification URL + user code on stderr
GitHub Actions / coding agent
permissions:
id-token: write
contents: read
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "22"
- run: npm ci && npm run build
working-directory: path/to/nexus-mcp
- name: Run agent with Nexus MCP
env:
NEXUS_URL: ${{ vars.NEXUS_URL }}
TENANT_ID: ${{ vars.TENANT_ID }}
NEXUS_OIDC_AUDIENCE: ${{ vars.NEXUS_OIDC_AUDIENCE }}
run: node path/to/nexus-mcp/dist/index.js
Register owner/repo (immutable ids) on a Nexus OIDC trust policy with the
roles the agent needs (contributor / approver / etc.).
MCP client config (stdio example)
{
"mcpServers": {
"nexus": {
"command": "node",
"args": ["/absolute/path/to/nexus-mcp/dist/index.js"],
"env": {
"NEXUS_URL": "https://api.nonprod.plugin-federation.com",
"TENANT_ID": "11111111-1111-4111-8111-111111111111",
"GITHUB_OAUTH_CLIENT_ID": "Ov23li…"
}
}
}
}
Development
npm run typecheck
npm run dev
Related
- ADR 0008 Human GitHub SSO
- meteo-static / units-static dogfood MCPs
- Console uses the same
github_userexchange path
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。