One URL for every client
The server lives at https://api.inklate.com/mcp. Claude, Claude Code, Cursor, Codex, and Windsurf all speak to it natively.
Live today
MCP server× Inklate
Inklate ships an MCP server at the API edge — not a community wrapper, the product itself. Any MCP client authenticates with an organization API key or OAuth 2.1 and gets the same guarded actions as the dashboard: draft, schedule, publish, measure.
OAuth 2.1 or API keys
Interactive agents use the OAuth flow; headless ones use organization API keys. Both scope every call to one tenant.
The same guarded surface
MCP tools call the exact API the dashboard uses — roles, plan entitlements, and row-level security apply identically.
Any MCP client
{
"mcpServers": {
"inklate": {
"url": "https://api.inklate.com/mcp",
"headers": { "Authorization": "Bearer inklate_your_org_key" }
}
}
}Questions
Good to know
Which agents are supported?
Any MCP client. We keep setup guides for Claude, Claude Code, Cursor, Codex, and Windsurf under /agents.
What can an agent actually do?
Create and edit drafts, schedule with explicit timezone offsets, publish to connected channels, list channels, and read per-post analytics.
More integrations
Give your agents a content platform
Create an organization, connect a channel, and let your team and your agents publish together.