Connect

Your agent drafts. Now let it ship

Two minutes of setup turns drafts and plans into scheduled, published, measured posts — through the same guarded surface your team uses.

What you get

Six skills that execute

Setup

Connected in two minutes

Five steps, two of them copy-paste. Your agent confirms the connection itself at the end.

  1. 1

    Start a free trial

    Create your organization and connect your channels — LinkedIn, X, Instagram, Facebook and more. The 14-day trial covers everything.

  2. 2

    Create an org API key

    In the dashboard: Settings → API keys → New key. The key scopes every agent call to this one organization and can be revoked anytime.

  3. 3

    Point your agent at the MCP

    Paste the config into your agent's MCP settings (Claude Code shown; every MCP client uses the same URL + header).

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

    Install the Inklate skills

    One command adds publish, schedule-week, preflight, inbox, and analytics-review to your agent.

    terminal
    npx skills add inklate/skills
  5. 5

    Say “set up Inklate”

    The inklate-setup skill verifies the connection, lists your channels, and pre-fills your social-context.md from what's actually connected.

Questions

Before you connect

Is it free to try?

Yes — every Inklate plan starts with a 14-day free trial, no feature gates. The skills themselves are MIT-licensed and free forever; the trial covers the publishing layer behind them.

What can my agent do once connected?

Everything the dashboard can, scoped to one organization: create posts, validate them against each channel's real rules, fix violations, schedule placements, publish, read the inbox, and pull per-post metrics. It cannot touch other organizations or exceed the key's scope.

How is access secured?

Your agent authenticates with an organization API key (or OAuth 2.1). Every call is re-checked against organization membership server-side — the same guard ladder as the dashboard — and keys are revocable at any time from Settings → API keys.

Do I need the general skills too?

They pair naturally — cross-post drafts, publish ships — and both read the same social-context.md, so your setup carries over. But the Inklate skills work standalone if your drafts come from anywhere else.