Central MCP

One MCP server for the whole LMS/COP platform: LMS (production & staging), task board, GenAI gateway, cluster/infra, and databases. SUPER_ADMIN only — signed in through central auth (communityop.com). Every call is audited.

Endpoint

https://mcp.communityop.com/mcp?profile=core

Profiles: core (default — context, ops, board, infra, db) · marketing · all. Systems with a staging environment take environment: "production" | "staging" — reads default to production; writes require the environment explicitly.

Setup

Two ways in: OAuth (interactive clients — your browser opens central sign-in) or a personal gateway token (CLI configs — mint one on this page after signing in, bottom of this page).

Claude Code

claude mcp add --transport http communityop "https://mcp.communityop.com/mcp" --header "Authorization: Bearer $MCP_TOKEN"

Cursor — add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "communityop": {
      "url": "https://mcp.communityop.com/mcp",
      "headers": { "Authorization": "Bearer $MCP_TOKEN" }
    }
  }
}

Claude Desktop / ChatGPT connector — paste the endpoint URL above; the browser flow uses central sign-in automatically.

zcode — add to ~/.zcode/cli/config.json

{
  "mcp": { "servers": {
    "communityop": {
      "type": "http",
      "url": "https://mcp.communityop.com/mcp",
      "headers": { "Authorization": "ApiKey $MCP_TOKEN" }
    }
  } }
}

curl

curl -X POST "https://mcp.communityop.com/mcp" \
  -H "Authorization: ApiKey $MCP_TOKEN" \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Replace $MCP_TOKEN with your personal gateway token (below) or an OAuth access token from central auth.

Systems

System	Environments	Status	Covers
LMS / COP	production · staging	P2/P4	error logs, queues, auth audit, storyhaven, brand, landing pages, campaigns, drips, ads
Task board + agent fleet	production	P5	board, cards, milestones, tickets, agent runs
GenAI gateway	production	P2	call log, usage, keys, chains, kill switch, provider ops
Cluster / infra	production	P2	pods, deployments, jobs, cron, events, logs, backups; safe ops
Databases	production · staging	P3	read-only SQL; two-phase guarded writes (confirm + caps + rollback)

Tokens

The raw token is shown once — store it in your client config. Tokens expire after 90 days and can be revoked here.

Operational notes

Every call is audited: who, which tool, which environment, outcome.
Destructive tools (restarts, DB writes) are annotated as such and require the explicit environment; DB writes are two-phase (dry run → confirm token) with row caps and rollback.
Access requires the SUPER_ADMIN role on the central account — enforced at the gateway and again at each system.