Your whole account, every channel, from the tool you already work in.

01

Add it as a custom connector

Settings, Connectors, then add a custom connector and paste this as the server URL. It carries the key in the path, which is the form for a client that cannot attach a header, and it authenticates exactly as the header does. Revoke that key if the address ends up somewhere shared.

https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

02

Leave the confirmation step on

Two tools reach real timelines and nothing can take a post back: publish_post, which sends a post that is already written, and retry_target, which flies one channel again. Both are annotated so a client can see it and ask you first. Everything else reads, or writes a draft that waits for you.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Sign in

Run /mcp inside Claude Code and follow the browser. It stores the token and refreshes it when it expires, so this is the last time you think about it. From a shell instead, claude mcp login postauto does the same.

02

Or use a key, for a script with no browser

A cron job cannot follow a browser, so it wants a key instead. Make one in Settings, API keys and pass it as a header. It can publish to every channel on the account and it does not expire, so give an agent its own and revoke it when you are done.

claude mcp add --transport http postauto \
  https://api.postauto.io/api/mcp \
  --header "Authorization: Bearer pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

03

Add the server

One command, no key. Claude Code registers itself with the server and works out where to sign in on its own.

claude mcp add --transport http postauto https://api.postauto.io/api/mcp

01

Add it under Connectors

Settings, Connectors, Advanced, Developer mode, then Create. Name it Postauto, paste this as the MCP server URL, and set authentication to access token or API key with the key pasted in. That sends it as a bearer header, which is the form to prefer.

https://api.postauto.io/api/mcp

02

If the form has no field for a token

Leave authentication set to none and use this address instead, which carries the key in the path. Either way, Postauto writes to your social channels, so leave a confirmation step on for it rather than approving every tool call in advance.

https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Write it into mcp.json

~/.cursor/mcp.json gives every project the server, .cursor/mcp.json in a repository gives one project it. The key travels as a header, so it stays out of the URL, which means out of proxy logs and shell history.

{
  "mcpServers": {
    "postauto": {
      "url": "https://api.postauto.io/api/mcp",
      "headers": {
        "Authorization": "Bearer pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

02

Keep the project file out of git

A committed .cursor/mcp.json is a published key, and a key can publish to every channel on the account. Ignore the file, or put the server in the user scoped one instead. If a key does get out, revoke it in Settings and make another; that is the whole recovery.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Add the server to the CLI's settings

~/.gemini/settings.json for every project, .gemini/settings.json for one. httpUrl is the streamable HTTP form, which is what this endpoint speaks, and headers is where the key goes.

{
  "mcpServers": {
    "postauto": {
      "httpUrl": "https://api.postauto.io/api/mcp",
      "headers": {
        "Authorization": "Bearer pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

02

The browser app is a different thing

Adding a remote MCP server is a CLI feature. From the app there is nothing to point at the endpoint, so the two doors from there are the CLI above and the plain HTTP API on the same key.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Add a workspace server

.vscode/mcp.json, with an input rather than the key itself. VS Code prompts for the key the first time and keeps it, so this is the one configuration on this page that is safe to commit.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "postauto-key",
      "description": "Postauto API key (pau_live_...)",
      "password": true
    }
  ],
  "servers": {
    "postauto": {
      "type": "http",
      "url": "https://api.postauto.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:postauto-key}"
      }
    }
  }
}

02

Start it, then check it

The server appears in the MCP view and its tools appear in the chat's tool picker. A missing or revoked key answers 401 with a JSON-RPC error explaining how to send one, so a failure here says what is wrong rather than going quiet.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Point a bridge at the endpoint

Zed starts a context server as a program on your machine, so a remote server over HTTP is reached through a stdio bridge rather than directly. This is the command to give it. The address carries the key because the bridge is what calls us.

npx -y mcp-remote https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

02

A key in a settings file is still a key

It sits there in plain text, which is fine on your own machine and not fine in a dotfiles repository anybody else can read. Give this one its own key so revoking it costs you nothing else.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Add it as a custom server

Windsurf keeps its MCP servers in its own configuration, reachable from the plugin panel. Paste this as the server URL, and add Authorization with Bearer and your key as a header on the same entry.

https://api.postauto.io/api/mcp

02

If the build will not send a header

Use this address instead. It carries the key in the path, it authenticates identically, and it is the fallback for any client that cannot attach one. Treat the URL itself as the secret from then on.

https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Add an HTTP server to config.toml

Codex reads its servers from ~/.codex/config.toml. Add Postauto there as an HTTP server on this URL, with an Authorization header carrying Bearer and your key.

https://api.postauto.io/api/mcp

02

If your build only launches servers as commands

Streamable HTTP arrived in Codex after stdio did, so an older build takes a command rather than a URL. This bridges one to the other, and the address carries the key because the bridge is the caller.

npx -y mcp-remote https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Add it from Manage MCP Servers

Raycast's own Manage MCP Servers command is where a server goes. Paste this endpoint, and put the key in an Authorization header as Bearer and the key if the form takes one.

https://api.postauto.io/api/mcp

02

Otherwise bridge it

Where the form takes a command rather than an address, this is the command. It runs on your machine and speaks HTTP to us, and the key rides in the address it is given.

npx -y mcp-remote https://api.postauto.io/api/mcp/pau_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.

01

Check the key by hand

This is also the shape of every MCP call, and both headers are required by the transport. It answers with the whole tool list. A missing or revoked key answers 401 with a JSON-RPC error explaining how to send one.

curl -sS -X POST https://api.postauto.io/api/mcp \
  -H "Authorization: Bearer $POSTAUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

02

Then write a post

The REST API is the same service layer behind a different door, on the same key. It lists channels and networks, splits a thread, finds the next open gate, creates, reads, revises and deletes posts, reads their numbers, and manages feeds and repost rules.

03

Make an API key

Sign in, then Settings, API keys. A key is pau_live_ followed by 32 characters and it is shown exactly once, because only its hash is stored. The same key opens the MCP server and the HTTP API. It can publish to every channel on the account, so treat it like a password and give an agent its own.