VNOC Admin Agent logo
VNOC · Admin infrastructure

VNOC Admin Agent

Operator MCP for tasks, submissions, builds, and domain ops — backed by the VNOC Next.js app (api.vnoc.com / app.vnoc.com). Connect Claude Cowork below, or use a short-lived bearer token with Cursor and other MCP clients.

Claude Cowork setup Sign in with GitHub

Connect with Claude Cowork

Recommended for daily VNOC operations. Cowork uses remote MCP with OAuth — you do not paste long-lived API keys into the connector.

  1. In Claude, open Customize → Connectors → Add custom connector → Web.
  2. Set the connector URL to (copy exactly):

https://agent.vnoc.com/api/admin/vnoc-mcp

  1. Click Connect. Claude runs OAuth discovery, then sends you to AgentDAO to sign in with GitHub.
  2. Your account must be a VNOC operator admin: AgentDAO is_admin = true, and your email is @vnoc.com or listed in VNOC_ADMIN_EMAILS.
  3. In a Cowork chat, click + → Connectors and enable the VNOC Admin connector.

Use only https://agent.vnoc.com/api/admin/vnoc-mcp — do not point Cowork at https://developers.agentdao.com/api/admin/vnoc-mcp (direct control-plane MCP calls are blocked without the worker gate).

Capabilities

Tasks & sprintsCreate sprints, add tasks under latest or specific sprint ids, updates and assignees.
Submissions & offersList latest offers, approve/reject, and respond to prospects from MCP.
Build orchestrationQueue builds, check status, retry, cancel, and publish via api.vnoc.com / app.vnoc.com. Custom domains (e.g. contrib.com) need super-admin approval.
Add domainsValidate, add, and attach domains to builders through the Next.js manage-app API.
Ops inbox & statsUnified inbox for blocked tasks, pending submissions, and build failures plus KPI views.
Audit & DNSPer-operator activity history, DNS change logs, and write-gated DNS upserts.

VNOC-native ops hit the Next.js manage-app at api.vnoc.com or app.vnoc.com (same deployment, AWS RDS). Custom domains (e.g. contrib.com) cannot be built or switched unless approved by super-admin maidabarrientos@gmail.com or an override in cf-builder.

MCP tools (35+)

Once connected, ask Claude to run operator tools. Examples by category:

Tasks
  • add_domain_task · add_sprint_task
  • list_sprint_tasks · get_latest_tasks
  • update_task · add_task_update
  • list_assignable_users · get_task
Submissions
  • list_latest_submissions
  • review_submission
  • respond_submission
Build & domains
  • resolve_domain · get_domain
  • build_domain · get_build_status · retry_build
  • validate_add_domain · add_domain_vnoc
  • attach_domain_to_builder (custom domains: super-admin only)
Ops & audit
  • get_ops_inbox · get_pipeline_stats
  • get_domain_stats · get_operator_stats
  • get_activity_history · get_activity_summary
  • get_dns_records · upsert_dns_record (write-gated)

Who can use this

Access is limited to verified VNOC operators with an AgentDAO admin account (@vnoc.com or an email on the VNOC_ADMIN_EMAILS allowlist).

Sign in with GitHub at https://developers.agentdao.com/login. Admins see Admin Panel in the header after sign-in. Contact your VNOC administrator if you need allowlist access.

Manual token (Cursor, scripts, Claude Desktop)

For clients that do not support OAuth, mint a short-lived bearer token while signed in on the control plane.

  1. Request a short-lived MCP token: POST https://developers.agentdao.com/api/admin/vnoc-mcp/token (while logged in).
  2. Configure your MCP client to call https://agent.vnoc.com/api/admin/vnoc-mcp with Authorization: Bearer .

Manifest (auth required): /.well-known/mcp.json

Not authorized?

If you are not a VNOC operator, you cannot use this agent. Consumer agents and developer APIs live on other AgentDAO domains. Contact your VNOC administrator to request access.

MCP and admin tools require a valid operator token · © 2026 agent.vnoc.com