What is MCP?
MCP is an open protocol that connects AI assistants to external tools and data sources. Instead of copying and pasting API calls, your AI assistant can interact with Kavio directly.Available tools
Kavio exposes a full set of MCP tools for end-to-end content workflows. See the Tools reference for parameters and examples.How it works
n MCP access requires an active trial or subscription. New accounts get a 7-dayn trial automatically - no credit card required to start. Seen [Plans & billing](/knowledge-base/plans-and-billing) for details.n1
Add the Kavio MCP server in your assistant
Use your assistant’s MCP configuration to add a remote HTTP server pointing
to
https://app.getkavio.app/mcp/kavio. Each client guide
below has the exact command or settings file.2
Sign in through your browser
The first time the assistant calls a tool, Kavio opens a browser window
asking you to sign in and authorize the connection. Click Allow and
you’re done — the assistant holds the OAuth token from then on, with
automatic refresh.
3
Start using natural language
Ask your assistant to manage your Kavio account. For example: “Create a new
post for LinkedIn next Tuesday at 9am” or “List all my scheduled posts.”
Server URL
Authentication
Kavio’s MCP server uses OAuth 2.1 with Dynamic Client Registration (DCR), PKCE, and themcp:use scope. Modern MCP clients (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, GitHub Copilot in IDE, Gemini CLI, OpenCode, Codex) detect this automatically from the .well-known discovery endpoints — you only point them at the URL and the browser sign-in handles the rest.
Bearer token fallback (CI, scripts, or clients without OAuth)
Bearer token fallback (CI, scripts, or clients without OAuth)
If your environment can’t open a browser — for example a CI pipeline, the GitHub Copilot cloud coding agent, or a client that doesn’t speak OAuth yet — you can authenticate with a Personal Access Token instead. Create one in Settings > API Keys on the Kavio dashboard and send it as
Authorization: Bearer YOUR_API_KEY. The same token works for both the REST API and the MCP endpoint.Keep the token in a secret store, not committed to source. Rotate from Settings > API Keys if a key leaks.Troubleshooting
HTTP 402 — Active subscription required
HTTP 402 — Active subscription required
Your token is valid and the config is correct — the account behind it just
doesn’t have an active trial or subscription. Open
app.getkavio.app, start a trial or pick a plan
(no card required to start the trial), then reconnect the MCP server.
HTTP 401 — Unauthenticated
HTTP 401 — Unauthenticated
The OAuth session expired and refresh failed, or (in the Bearer fallback)
the token is missing/malformed/revoked. Re-run the assistant’s connect flow
to re-authenticate, or issue a new PAT from Settings > API Keys.
Server shows as “Failed to connect”
Server shows as “Failed to connect”
Run the connection probe your assistant exposes (for example
claude mcp list). The HTTP status from the probe tells you which case you’re in: 402- see above;
401- re-authenticate; anything else - contact support.
Browser doesn't open during sign-in
Browser doesn't open during sign-in
Some clients print the authorize URL to the terminal instead of launching
the browser when running over SSH or inside a container. Copy the URL into a
local browser, complete the flow, and the assistant will pick up the
callback automatically. If the callback port is blocked, use the Bearer
fallback.
Next steps
Claude Code
CLI assistant by Anthropic.
Claude Desktop
Desktop app by Anthropic.
Cursor
AI-powered code editor.
Windsurf
Editor with Cascade AI.
VS Code
Native MCP support in Copilot Chat.
GitHub Copilot
Copilot agent mode.
Gemini CLI
CLI assistant by Google.
OpenCode
Open-source CLI assistant.
Codex
CLI agent by OpenAI.
Antigravity
AI agent by Google.