Inklate

Agents

Your agents, on the masthead

Inklate ships a Model Context Protocol server at the API edge. Point any MCP client at one URL and it operates your content pipeline with the same guardrails as your team.

Draft

Create and edit posts in your organization's library, ready for review or straight to the queue.

Schedule

Queue posts with explicit timezone offsets — 9am always means 9am, never a UTC surprise.

Publish

Push posts live to connected LinkedIn profiles and company pages the moment you say so.

Measure

Read impressions, reactions, comments, shares, and clicks — the same self-updating numbers as the dashboard.

Setup guides

Pick your operator

Each guide covers the exact config for that client — connector, JSON, or TOML — plus prompts to try on day one.

The whole setup

One config block, every client

Create an API key in the dashboard (Settings → API keys), drop this block into your client's MCP config, and the tools appear. Access is scoped to one organization and re-checked on every call.

mcp.json
{
  "mcpServers": {
    "inklate": {
      "url": "https://api.inklate.com/mcp",
      "headers": { "Authorization": "Bearer inklate_your_org_key" }
    }
  }
}

Put an agent on the byline

Create an organization, mint an API key, and your agent is publishing in minutes.