Connect over MCP

Point Claude or any MCP client at Inklate's Streamable HTTP server — the short version, with the full tool reference in the MCP tab.

Inklate exposes a Model Context Protocol server, so any MCP client — Claude Code, Claude Desktop, Cursor, your own agent — can discover channels, then draft, validate, schedule, and publish posts in one composed call, and measure what shipped. The agent drives the same procedures the dashboard uses, so an agent and a human can never diverge.

Transport: Streamable HTTP
URL: https://api.inklate.com/mcp (local dev: http://localhost:3000/mcp)
Auth: Authorization: Bearer <token> — an Organization API key (prefix inklate_) or an OAuth 2.1 access token

claude mcp add inklate https://api.inklate.com/mcp -t http \
  -H "Authorization: Bearer inklate_XXXXXXXX"

The full reference lives in the MCP tab

Every tool has its own page, generated from the tool definitions the server mounts — so the inputs you read are the inputs it validates.

MCP overview

Transport, the shape of the tool surface, timestamps, and how refusals read.

Connect a client

API key, the OAuth handshake, Cursor and Claude Desktop config, and a local stdio server.

Available tools

Every tool, grouped by what it acts on.

Security model

What an agent can reach through MCP, and what stops it.

API keys

Create and scope an Organization API key in the dashboard.

Agent recipes

End-to-end tool sequences: one call to a scheduled post, and pull analytics.