nexus-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@nexus-mcpwhat proposals are waiting for my approval?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
|
TypeScript SDK |
|
Schema validation | 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).
Related MCP server: orchestrator-mcp
Security model
Identity | How it authenticates | Nexus credential |
Human (Cursor, Claude Desktop, local agent) | GitHub SSO — device flow ( | Short-lived Nexus JWT via |
GitHub Actions / coding agents in GitHub | GitHub OIDC ( | Short-lived Nexus JWT via |
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 buildEnvironment
Variable | Required | Purpose |
| yes | e.g. |
| Actions OIDC | Tenant UUID matching OIDC trust policy; also preferred tenant for multi-membership humans |
| Actions | Must match Nexus |
| humans (device flow) | Public OAuth App client id for device flow |
| no | Default |
| 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 stderrGitHub 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.jsRegister 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 devRelated
meteo-static / units-static dogfood MCPs
Console uses the same
github_userexchange path
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for the Codex Security Cloud service, enabling agents to list, inspect, close, reopen findings, request PRs, and apply generated patches.74 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMulti-model agent orchestration MCP server that enables plan-code-review-deliver pipelines with configurable providers and models.-
- AlicenseNot gradedqualityBmaintenanceUnified control plane and runtime for the Model Context Protocol ecosystem, enabling plugin management, configuration, permissions, and API gateway services.5 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-