Inklate

Anthropic · terminal & IDE agent

Publish with Claude Code

Claude Code lives where the work happens. Wire Inklate into it and the same session that merges the PR can draft the announcement, schedule it for the right morning, and report back on how the last one did.

Start free trialSetup guide

What Claude Code can do

The full pipeline, by prompt

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

Connected in three steps

You'll need an Inklate organization and, for key-based setups, an API key from Settings → API keys in the dashboard.

  1. 1

    Add the Inklate MCP server

    Register the server with your organization API key (create one in the dashboard under Settings → API keys).

    Terminal
    claude mcp add --transport http inklate https://api.inklate.com/mcp \
  --header "Authorization: Bearer inklate_your_org_key"
  2. 2

    Verify the connection

    Run /mcp inside Claude Code to confirm Inklate is connected and its tools are listed.

    Claude Code
    /mcp
  3. 3

    Put it to work

    Ask for drafts, schedules, or analytics in plain language — or add it to CLAUDE.md so every session knows publishing is on the table.

Try these first

Prompts that earn their keep

“We just merged the dark-mode PR. Draft a LinkedIn post about it and schedule it for tomorrow 9:15 AM IST.”
“List everything scheduled this week and flag anything that collides.”
“Write a launch-day thread from RELEASE_NOTES.md and queue the first post for Monday.”

Questions

Claude Code × Inklate, answered

Where does the API key live?

In the command above it's passed as a header; for teams, keep it in an environment variable and reference it from your MCP config instead of committing it.

Project or user scope?

Both work. Add it with --scope user to publish from any repo, or per-project so only your product repo can post.

Also works with

ClaudeCursorCodexWindsurf

Give Claude Code a content platform

Create an organization, connect LinkedIn, and your agent publishes with the same guardrails as your team.

Start free trialSee pricing