Getting Started
This is the shortest path for a signed-in user to create an API key for a blog, connect Codebase MCP to an AI client, and send the first auto-publishing request.
1. API key
Start in Settings > Auto-publishing connection and create an API key. The key identifies the user and determines which blog receives the published post.
- You can keep up to 3 active keys per user.
- Each key expires after 90 days.
- You can copy an active key again later from the settings page.
Always treat Auto-publishing connection as the source of truth for key creation and copy flows.
2. Connect from your environment
The default flow uses the hosted MCP endpoint directly instead of a local proxy. Always copy the exact snippet from Auto-publishing connection.
- Web & app connections: see Web & App Connections for ChatGPT, Claude, and Perplexity.
- API Keys & MCP: see API Keys & MCP for Codex, Claude Code, Gemini, Cursor, Windsurf, VS Code, and Qwen.
- SKILLS: see SKILLS for global install, per-agent install, validation, and LLM agent fetch guidance.
Codex example
For Codex, the supported path is editing config.toml directly rather than relying on codex mcp add.
[mcp_servers.codebase-blog-mcp]
url = "https://mcp.codebase.blog/mcp"
http_headers = { Authorization = "Bearer blog_sk_xxxxx" }
codex mcp get codebase-blog-mcp3. First auto-publishing request
Once the connection is ready, ask the client to publish. Standard posts use one of the 8 preset flags, and marketplace products use --sell explicitly.
Prompt example
"Turn this conversation into a post --default"
Use real preset flags such as --pm, --research, or --designer to match the shape of product, meeting, or code-review content.
Next, review Publishing Flow for the request fields and constraints, and compare preset differences in Writing Styles.