I lost the key.
Reopen the install screen from the end of signup and choose Re-issue key. A new key is shown once; the old one stops working immediately, so update every agent that had it.
Install NORG's private MCP
Growth plan — full-scope endpoint with an API key
Your plan is active and the install screen has shown you an API key. Put the endpoint and that key into the AI agent you use, and your agent finishes the setup with you over MCP.
Your endpoint and key
The Growth plan gives your agent the full private NORG MCP: one endpoint, authenticated with an API key sent as a bearer token.
What you have
MCP endpoint: https://content-craft-api.norg.ai/mcp
API key: a norg_ak_… key, shown once on the install screen at the end of signup. It is sent on every request as Authorization: Bearer <key>.
The key is shown once
Copy it into your agent before you leave the install screen. If you lose it, reopen that screen and choose Re-issue key: the old key stops working the moment a new one is issued, so update every agent that had the old one.
Treat it like a password. It grants full access to your NORG workspace, so never paste it into a chat message, a ticket or a shared document — only into your agent's own configuration.
Claude Desktop
Add the server to claude_desktop_config.json (Settings → Developer → Edit config), then restart Claude Desktop.
{
"mcpServers": {
"norg": {
"type": "http",
"url": "https://content-craft-api.norg.ai/mcp",
"headers": {
"Authorization": "Bearer norg_ak_<your-key>"
}
}
}
}Claude Code
One command registers the server with the key; no sign-in step follows.
claude mcp add norg --transport http https://content-craft-api.norg.ai/mcp \
--header "Authorization:Bearer norg_ak_<your-key>"ChatGPT
Settings → Connectors → Create. Enter the name and URL, and choose bearer-token authentication with your key.
{
"name": "norg",
"type": "mcp",
"url": "https://content-craft-api.norg.ai/mcp",
"auth": {
"type": "bearer",
"token": "norg_ak_<your-key>"
}
}ChatGPT presents these as form fields rather than JSON; the block above shows which value goes where. There is no OAuth sign-in on the Growth endpoint — the key is the credential.
Gemini CLI
Add the server under mcpServers in ~/.gemini/settings.json.
{
"mcpServers": {
"norg": {
"httpUrl": "https://content-craft-api.norg.ai/mcp",
"headers": {
"Authorization": "Bearer norg_ak_<your-key>"
}
}
}
}Other agents
Cursor, Windsurf and any other MCP client are similar installs.
Add the endpoint as a remote (HTTP) MCP server and set a request header of Authorization: Bearer norg_ak_<your-key>. Every client that supports remote MCP servers has a place for custom headers; that is the only NORG-specific piece. Claude Code users can also run the key through the same claude mcp add command shown above from inside any project.
Verify with curl
Two requests confirm the endpoint accepts your key. A 401 on the first one means the key is wrong, revoked or missing its Bearer prefix.
# 1. Handshake: a 200 with server info means the key is accepted.
curl -s https://content-craft-api.norg.ai/mcp \
-X POST \
-H "Authorization: Bearer norg_ak_<your-key>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'
# 2. List the tools: express_setup should be among them.
curl -s https://content-craft-api.norg.ai/mcp \
-X POST \
-H "Authorization: Bearer norg_ak_<your-key>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'The first thing your agent should do
Your agent finishes the setup the wizard used to walk you through — website addresses to crawl, tone of voice, the knowledge-base build — over MCP.
Tell your agent
"Connect to NORG and call express_setup with action=get_manifest, then follow its call order."
The manifest lists the fields the agent can set, the order to call things in, and how to poll for the build. When the knowledge base is ready, the same endpoint answers questions about your business — the key you installed today is the one your agent keeps using.
Questions
The endpoint returns 401.
The key is wrong, has been re-issued, or the header is malformed. It must read exactly "Authorization: Bearer norg_ak_…" — the word Bearer, one space, then the key.
Does this key work with the Claude directory connector or the ChatGPT connector?
No. Those Starter-plan connectors use an OAuth sign-in and reject API keys. The Growth key is for the private /mcp endpoint on this page.
Can several agents share one key?
Yes — the key identifies your workspace, not the agent. Re-issuing it invalidates it everywhere at once, which is also how you cut off an agent you no longer use.
What can the agent do with it?
Everything the NORG MCP exposes for your workspace, starting with finishing setup via express_setup. Ask the agent to describe its tools, or see the tool reference linked below.
Talk to us
If the endpoint rejects your key, or your agent cannot see the NORG tools after connecting, write to solutions@norg.ai and include:
- which agent you are connecting (Claude Desktop, Claude Code, ChatGPT, Gemini CLI, other)
- the first eight characters of your key (never the whole key)
- the exact response the endpoint returned, if you tried the curl check
On the Starter plan instead? See the Starter install guide. For every tool the connector surface exposes, see the MCP tool reference.