Connect an AI

Settings → Connectors → Add custom connector. Name it Post Social and paste the address above. Claude opens Post Social; sign in and press Allow.

A connector added in Claude also works in Claude Code when Claude Code is signed in with the same Claude plan.

Settings → Apps & Connectors → Advanced settings → turn on Developer mode. Then Create a connector with the address above and sign in when asked.

ChatGPT connectors don't carry over to Codex, so set Codex up separately.

Only needed if Claude Code isn't signed in with your Claude plan (for example, with an API key). Add the server, then run /mcp in Claude Code and choose Authenticate:

claude mcp add --transport http post-social https://www.postsocial.xyz/mcp

Prefer a key (for scripts and CI)? Create one under API keys on the Connect your AI page in Post Social and add it as a header:

claude mcp add --transport http post-social https://www.postsocial.xyz/mcp --header "Authorization: Bearer ps_live_..."

For the Codex CLI, the IDE extension and the ChatGPT desktop app. Run both lines; the second opens your browser to approve:

codex mcp add post-social --url https://www.postsocial.xyz/mcp
codex mcp login post-social

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project), then press Connect next to Post Social in Cursor's MCP settings:

{
  "mcpServers": {
    "post-social": {
      "url": "https://www.postsocial.xyz/mcp"
    }
  }
}

On grok.com, open grok.com/connectors → New Connector → Custom, paste the address above, then sign in. For the Grok CLI, run this and press i in /mcps to sign in:

grok mcp add --transport http post-social https://www.postsocial.xyz/mcp

Muse connects with an API key. On the Connect your AI page in Post Social, open the Muse tab and choose Create a key for Muse. Then send Muse this message and paste the key into Muse's secure form when it asks (never into the chat):

Connect a custom MCP server called Post Social at https://www.postsocial.xyz/mcp. It's a remote MCP server (streamable HTTP, JSON-RPC over POST) that takes a bearer token in the Authorization header. Don't open the address in a browser: it only answers MCP requests. Use "Muse" as the clientInfo name when you initialize. Ask me for the token in your secure credential form, then list the tools to check it works and save it as a skill.

Add this to ~/.hermes/config.yaml, then run /reload-mcp. Hermes prints a link to approve Post Social the first time:

mcp_servers:
  post-social:
    url: "https://www.postsocial.xyz/mcp"
    auth: oauth

Run both lines; the second opens your browser to approve:

openclaw mcp add post-social --url https://www.postsocial.xyz/mcp --transport streamable-http --auth oauth
openclaw mcp login post-social

Add a remote MCP server with the address above. Most apps sign in automatically; for apps that only take keys, send Authorization: Bearer ps_live_....

{
  "mcpServers": {
    "post-social": {
      "url": "https://www.postsocial.xyz/mcp"
    }
  }
}

No AI app needed: the command line takes JSON in and gives JSON out, and the REST API uses an API key.