AI agents

Connect your AI agent for social media posting

LitPost has an MCP server, so the AI agent you already use can work on your posts from the chat. It reads the starting points LitPost found in your real work, saves drafts, schedules posts and publishes them when you say so, to the accounts you connect in LitPost: X, LinkedIn, Mastodon and Bluesky.

Connecting takes a minute: paste one address into your agent, sign in to LitPost and allow it. Agents that ask for a key instead get a personal API key.

By Yannis Azouz, founder of LitPost
Updated

How it works

MCP, the Model Context Protocol, is the standard AI agents use to connect to apps. LitPost's MCP server gives your agent a short list of tools, and you sign in once.

The addresshttps://litpost.app/mcp
  1. Add the address to your agent as a custom connector or an MCP server. The steps for each agent are below.
  2. Sign in to LitPost, choose what the agent may do, and click Allow. Untick publishing to keep it to drafts and scheduling, or untick writing too to keep it read-only. The page also tells you where you go back to.
  3. Ask in plain words. For example: "Show me my LitPost starting points for this week", "Turn the second one into a LinkedIn post in my voice and save it as a draft", "Schedule it for tomorrow at 9am", "What do I have scheduled this week?"

Set it up in your agent

Every agent below signs in through LitPost: no API key to copy. Menu names can move between versions of each app; the address and the sign-in stay the same.

Each of these agents has its own page, with what you can ask it:

  • WEB, DESKTOP AND MOBILE APPS

    Claude

    Open LitPost in Claude's directory and click Connect. On the LitPost page that opens, choose what Claude may do and click Allow.

    Can't find it? Settings, then Connectors, then Add custom connector. Name it LitPost, paste the address and leave the OAuth client fields empty.

  • WEB

    ChatGPT

    Open Plugins in the sidebar, click Add, then Add custom MCP server. Name it LitPost, paste the address and choose OAuth if it asks how to sign in. Allow it on the LitPost page, then turn it on from the + menu in a chat.

  • ALWAYS-ON AGENTS

    ChatGPT dots

    A dot uses the plugins on your ChatGPT account. Add LitPost as for ChatGPT, then turn it on in your dot's profile, Customize, Plugins. In Custom rules, set publishing through LitPost to Ask before taking action, so your dot never posts without your yes. Dots need ChatGPT Pro (not yet in the EEA, the UK or Switzerland) or Business Premium.

  • GEMINI CLI

    Gemini

    Run this once, then start gemini and approve LitPost in the browser window it opens.

    gemini mcp add -s user -t http litpost https://litpost.app/mcp

    The custom apps of the Gemini web app aren't supported yet.

  • EDITOR

    Cursor

    Add LitPost to Cursor in one click and confirm in Cursor, or paste the config block from Any other agent into ~/.cursor/mcp.json. The first time the agent uses LitPost, Cursor opens it so you can allow it.

  • TERMINAL

    Claude Code

    Run this, then type /mcp in Claude Code, pick litpost and choose Authenticate.

    claude mcp add --transport http litpost https://litpost.app/mcp
  • TERMINAL

    Codex

    Add the server, then sign in once.

    codex mcp add litpost --url https://litpost.app/mcp
    codex mcp login litpost
  • COMET AND PERPLEXITY APPS

    Perplexity

    Settings, then Connectors, then add a custom remote connector with the address and OAuth authentication, and allow it on the LitPost page.

  • TERMINAL

    Grok Build and other terminal agents

    Add an MCP server with the address in your agent's settings. On first use it opens LitPost in your browser so you can allow it.

  • ANYTHING THAT SPEAKS MCP

    Any other agent

    Agents set up with a file take this block. Clients that only run local servers can reach LitPost through mcp-remote.

    {
      "mcpServers": {
        "litpost": {
          "type": "http",
          "url": "https://litpost.app/mcp"
        }
      }
    }
    npx mcp-remote https://litpost.app/mcp

Agents that take an API key

Some agents can't open a sign-in page: Manus, Cue, Hermes Agent, or an agent running on a server. They take a personal API key instead.

  1. In LitPost, open Settings, then Agents, then API keys.
  2. Name the key after the agent and tick what it may do: create and schedule drafts, publish right away, or only read.
  3. Copy the key: it's shown once. In your agent, add the address with the header Authorization: Bearer followed by the key.
{
  "mcpServers": {
    "litpost": {
      "type": "http",
      "url": "https://litpost.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LITPOST_KEY"
      }
    }
  }
}

Treat a key like a password: anyone who has it can act in LitPost within what you ticked. Remove it in the same place when you stop using it.

What your agent can do, and what it can't

The page where you allow an agent lists the same things, and lets you untick writing or publishing.

It can

  • See your connected accounts and your timezone
  • Read your starting points, with the real event each one comes from
  • List your drafts, scheduled and published posts
  • Create and edit drafts, and schedule them
  • Publish a post right away, if you allowed it

It can't

  • Delete a post
  • Connect or disconnect a social account
  • See the passwords or tokens of your social accounts
  • Change your LitPost password or touch your billing
  • Attach images or videos (text posts for now)

You stay the author

An agent that posts for you can drift into posting things you never said. LitPost's instructions to every agent are the same as its own rules: write only from what you told it or from a starting point, never invent a number, a result or a claim, and keep your voice.

The agent is also told to show you the final text, the accounts and the time, and to schedule or publish only once you agree. A scheduled post goes out at its time without asking you again in LitPost, so read it in the chat before you say yes. Without your yes, it saves a draft that waits for you in LitPost.

The starting points your agent reads come from what you actually did: a release on GitHub, a milestone on Stripe, a traffic spike on Plausible, a past post that worked. Each one cites the event behind it.

Security and removing access

  • Your agent gets its own token, which only opens these tools. It isn't your LitPost login, and it never sees the tokens of your social accounts.
  • LitPost only hands a connection to agents that send you back to an address it trusts, such as claude.ai, chatgpt.com or your own computer, so a look-alike app can't collect one.
  • Tokens and API keys are stored as hashes. An agent's token lasts an hour and renews while the agent is in use.
  • In LitPost, Settings, then Agents lists every connected agent and key, with when it was last used. Remove cuts it off right away.

The details are in the privacy policy.

Questions

Do I need a paid plan?

LitPost needs an active plan or the 7-day free trial. On the agent's side it depends on the agent: some only let you add your own connector on a paid plan, others on any plan.

Is this an autopilot?

No. Nothing is posted on a schedule you didn't set. The agent acts when you ask it to, on posts you've seen, and LitPost never invents what you say. Always-on agents such as ChatGPT dots work on their own, so set them to ask you before they publish.

Which networks can my agent post to?

The accounts you connect in LitPost: X, LinkedIn, Mastodon and Bluesky.

Can an agent read my feed or my messages?

No. It works on your LitPost posts and starting points only.

My agent isn't listed. Will it work?

If it can add an MCP server and open a sign-in page, use the address. If it only takes a key, create one. If it refuses to connect, write to support@litpost.app and we'll look at it.

Bring your agent. Keep your voice.

Start a LitPost trial, connect your accounts and your agent, and post from the chat.

Start for free

7-day free trial. No credit card.