ChirpieDocs
MCP

Use Chirpie with Claude

Add Chirpie from the Claude Connectors Directory, or add https://chirpie.ai/mcp to Claude Code, and let Claude publish, schedule and track posts.

Verified 2026-09-28 against Claude's help center, the Claude Code MCP docs and Chirpie's live OAuth metadata. Directory listing added 2026-10-04.

How do I connect Chirpie to Claude?

In claude.ai and Claude Desktop, add Chirpie from its listing in the Claude Connectors Directory and sign in to Chirpie when Claude asks. You can also add https://chirpie.ai/mcp yourself as a custom connector under Customize → Connectors. In Claude Code it is one command, claude mcp add --transport http chirpie https://chirpie.ai/mcp, followed by /mcp to sign in. Nothing is installed and no API key is pasted.

Once connected, Claude can publish, schedule and thread posts on X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook and Telegram, save drafts, upload media, read analytics and answer comments, using the accounts you connected to Chirpie.

Add Chirpie from the Claude Connectors Directory

Chirpie is listed in the Claude Connectors Directory as Chirpie, by Fireflo LLC. This is the shortest route in claude.ai and Claude Desktop:

  1. Open the Chirpie listing, signed in to Claude.
  2. Connect it, then sign in to Chirpie in the window that opens and choose Full access or Read only.
  3. In a chat, open the + menu in the message box and switch Chirpie on under connectors for that conversation.

The listing and a custom connector reach the same server at https://chirpie.ai/mcp, with the same tools and the same sign-in, so use one or the other, not both.

Add Chirpie as a custom connector

Both claude.ai and Claude Desktop use the same connector list, because remote connectors are stored on your Claude account and called from Anthropic's servers rather than from your computer. Add Chirpie once and it appears in both.

  1. In claude.ai open Customize → Connectors. In Claude Desktop open Settings and choose Connectors.
  2. Click +, then Add custom connector.
  3. Enter the URL:
https://chirpie.ai/mcp
  1. Leave Advanced settings empty. Chirpie registers Claude as a client automatically, so there is no client ID or secret to supply.
  2. Click Add, then Connect, and sign in to Chirpie in the window that opens.
  3. In a chat, open the + menu in the message box and switch Chirpie on under connectors for that conversation.

On Team and Enterprise plans only an owner can add a custom connector, under Organization settings → Connectors. Members then find Chirpie in Customize → Connectors, marked Custom, and click Connect to sign in with their own Chirpie account.

The connector dialog has no field for a custom header, so claude.ai and Claude Desktop always use the sign-in flow rather than an API key.

Claude Code

Add the hosted server over HTTP:

claude mcp add --transport http chirpie https://chirpie.ai/mcp

Then run /mcp inside Claude Code, pick chirpie and complete the sign-in in your browser. claude mcp login chirpie does the same from your shell.

Add --scope user to make Chirpie available in every project, or --scope project to write it to the project's .mcp.json so your team gets it too:

claude mcp add --transport http chirpie --scope user https://chirpie.ai/mcp

For CI or a headless session with no browser, send an API key instead of signing in. Create one in the dashboard, ideally narrowed with scopes:

claude mcp add --transport http chirpie https://chirpie.ai/mcp \
  --header "Authorization: Bearer chirpie_sk_YOUR_KEY"

The Chirpie plugin (/plugin marketplace add Firefloco/chirpie-skills, then /plugin install chirpie@chirpie-skills) registers the same server and adds the Chirpie skills. See MCP Server.

What happens when I sign in?

Chirpie's MCP server uses OAuth 2.1 with PKCE (S256) and dynamic client registration, advertised at https://chirpie.ai/.well-known/oauth-protected-resource. In practice:

  1. Claude calls https://chirpie.ai/mcp, gets a 401 with a pointer to that metadata, and registers itself with Chirpie.
  2. A browser window opens on the Chirpie sign-in page. If you are already signed in to chirpie.ai it skips straight on.
  3. Chirpie asks what Claude may do: Full access (the default) or Read only. Pick one and choose Allow.
  4. Chirpie hands Claude an access token for the MCP server and the window closes. Claude refreshes the token on its own afterwards.

With Read only, Claude is offered only the tools that read (listing accounts, posts and comments, reading a post and its analytics) and Chirpie refuses anything else on that connection, naming the permission it would need. See Read only or full access.

If you have no Chirpie account yet, choose Sign up in the window that opens. Once you have verified your email you go straight back to choosing Full access or Read only, and Claude is connected. Then connect at least one social account in the dashboard, or ask Claude to connect one.

A sign-in grant cannot create, list or revoke API keys, or remove your own X developer app: those four tools are only offered to a connection that authenticates with an API key. With Full access, everything else, including connecting social accounts, works the same.

Which tools ask before they run?

Every Chirpie tool carries a title and the standard MCP annotations. Claude can run the read-only ones (listing posts and accounts, analytics, comments) without asking, and asks before a destructive one (deleting a post or comment, disconnecting or deactivating an account, editing a queued post) unless you have allowed it. The full table is in Which tools ask before they run?.

What can I ask Claude to do?

  • "Post 'We just shipped dark mode' to X and Bluesky, and give Bluesky a shorter version."
  • "Schedule a LinkedIn post for Tuesday at 9am New York time announcing the webinar, and save a draft of the follow-up."
  • "How did yesterday's X post do? Summarize the replies and draft answers for the questions."

More prompts, and every tool's parameters, are on the MCP Server page. For an X walkthrough from connecting the account to the first post, see Post to X from Claude.

Frequently asked questions

Is Chirpie in the Claude Connectors Directory?

Yes. Chirpie is listed in the Claude Connectors Directory as Chirpie, by Fireflo LLC, at claude.ai/directory/chirpie. Add it from the listing and sign in to Chirpie; there is no URL to paste. Adding it as a custom connector with https://chirpie.ai/mcp reaches the same server.

Which Claude plans can add Chirpie as a custom connector?

Custom connectors are available on the Free, Pro, Max, Team and Enterprise plans. Free is limited to one custom connector. On Team and Enterprise an owner adds Chirpie under Organization settings, then each member connects it for themselves.

Does Claude ask before it posts or deletes something?

Claude reads each tool's annotations. Read-only tools such as listing posts or reading analytics can run without asking. Destructive tools such as deleting a post, deleting a comment or disconnecting an account prompt you first unless you have allowed them. Publishing tools are neither read-only nor destructive, so how Claude treats them follows your permission settings.

Why don't I see the API key tools in claude.ai?

When you connect by signing in, Chirpie leaves out the four tools that create, list or revoke API keys or remove your own X developer app, because a revocable sign-in should not be able to mint a key that outlives it. Manage keys in the Chirpie dashboard instead. Connecting with an API key in Claude Code keeps those tools.

Can I give Claude read-only access to Chirpie?

Yes. After you sign in, Chirpie asks whether Claude gets Full access or Read only. Read only lets Claude list your accounts and read your posts, analytics and comments, and Claude is not offered any tool that publishes, edits, deletes or connects anything. To switch, remove the connector, add it again and choose the other option.

Is my Chirpie password shared with Claude?

No. You sign in on chirpie.ai, and Claude receives an access token for the MCP server rather than your password. Removing the connector in Claude ends its access.

Which networks can Claude post to through Chirpie?

X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook and Telegram. Claude posts to whichever of these accounts you have connected to Chirpie.

Sources: Get started with custom connectors using remote MCP, Connect Claude Code to tools via MCP.

On this page