Everything an operator or client needs to put an AI agent on the 8genC MCP server. Budget about four minutes once your account is approved.
POSThttps://mcp.8genc.com/mcp Operational
01
Prerequisites
The hosted endpoint is protected. Before you can connect you need:
An approved 8genC account. Register at mcp.8genc.com/access, verify your email, and wait for an admin to approve you and assign your track.
An MCP-capable client. Claude, Cursor, or Windsurf — anything that speaks Streamable HTTP MCP.
A credential. Either browser OAuth at connect time, or a personal access token minted in the portal.
Running locally over stdio? Platform discovery and the core skill tools work with zero credentials. Only skill_search and skill_sync need a ZeroDB account.
02
Authentication
Every request to POST /mcp must carry a valid credential for an approved account. Pick whichever method your client supports — both are gated on account status approved.
OAuth 2.1 — browser sign-in
The server is its own authorization server (RFC 9728 metadata + PKCE). Clients that support MCP OAuth open a browser, you sign in and consent, and the client receives a scoped token automatically.
Recommended for Claude
Personal access token
Create a token in the portal and pass it as a Bearer header. Best for headless clients and CI. Revoke it any time from /access.
Seeing 401 Unauthorized? Your account is likely still pending. Check your approval status in the portal — the channel stays closed until an admin approves you.
05
First commands
You're on the channel. Start with discovery, then load a skill.
Discover the platformUse prd_suggest_stack for "an agent that remembers user preferences and stores files"
Find a skillskill_search "turn a SOP into an automated system"
The portal at /access has two personas and a strict approval gate.
Users
Register, verify email, manage profile and password, create & revoke personal access tokens, and see approval status plus connection instructions.
Admins
Approve or reject pending accounts, block / unblock, reset passwords, assign tracks, and elevate verified users to admin.
Default-closed
New accounts are pending until approved. The first admin is seeded and must rotate its password on first login. Sessions are JWT-backed; tokens are revocable.