Use Chirpie with ChatGPT

Verified against OpenAI's docs on 2026-10-04: the help center's Developer mode and MCP apps in ChatGPT, the developer docs' ChatGPT Developer mode, Connect and test your plugin and Authentication, and the Responses API guide to MCP servers. Chirpie's side (the server at https://chirpie.ai/mcp, its OAuth metadata with dynamic client registration, PKCE and refresh tokens) was checked against the live server the same day. The ChatGPT steps are as documented by OpenAI and have not yet been tested end to end by Chirpie, and OpenAI's two sets of docs place the settings differently, so the labels in your ChatGPT may differ.

How do I connect Chirpie to ChatGPT?

Turn on developer mode in ChatGPT on the web, create an app for the remote MCP server https://chirpie.ai/mcp with OAuth, and sign in to Chirpie when ChatGPT asks. On a ChatGPT Business, Enterprise or Education workspace, ChatGPT can then publish, schedule and thread posts on the X, Bluesky, LinkedIn, Mastodon and Telegram accounts you connected to Chirpie, save drafts, upload media, and read analytics and comments. Threads, Instagram and Facebook are coming soon.

On Pro, OpenAI limits developer-mode apps to read and fetch permissions, so ChatGPT can read your posts and analytics but not publish. Developers can reach the same server from the OpenAI Responses API with an API key, on any OpenAI API account.

Before you start

1. A Chirpie account. Sign up free.
2. At least one social account connected in the dashboard, or connect one later by asking ChatGPT.
3. ChatGPT on the web, at chatgpt.com. MCP apps are not available in the mobile apps.
4. Developer mode for your account:
   • Business: only workspace admins and owners can use developer mode. An admin turns it on, creates the Chirpie app and publishes it to the workspace, and members then use the published app.
   • Enterprise and Education: an admin grants developer mode under Workspace settings → Permissions & Roles → Connected Data, to everyone or to selected roles. You then switch it on for yourself.
   • Pro and Plus: you switch it on yourself. Pro gets read and fetch permissions only, as above.

Add Chirpie in ChatGPT

1. Turn on Developer mode. OpenAI's help center puts the switch at Settings → Apps → Advanced settings; its developer docs put it at Settings → Security and login. It is marked as an elevated-risk setting, because a developer-mode app can take write actions.
2. Create an app: Settings → Apps → Create (admins can also use Workspace settings → Apps → Create). OpenAI's developer docs show the same step as the + button on ChatGPT Plugins.
3. Enter a name (Chirpie), a short description such as "Publish and schedule social posts", and the MCP server URL:

https://chirpie.ai/mcp

4. Leave authentication on OAuth and leave any client ID and secret empty. Chirpie supports dynamic client registration, so ChatGPT registers itself as a client.
5. Select Scan Tools, complete the Chirpie sign-in when it opens (below), wait for the scan to list Chirpie's tools, then select Create.
6. The app appears as a draft, labelled Dev in your app settings, where you can switch individual tools off. On a workspace, an admin publishes it from Workspace settings → Apps → Drafts so others can use it.
7. In a new chat, select Chirpie from the tools menu in the message box, or mention it with @. Mention it again when a later message needs another Chirpie action.

The app dialog has no field for a custom header, so ChatGPT always uses sign-in rather than an API key.

What does the sign-in look like?

Chirpie's MCP server answers ChatGPT's first request with a 401 that points to https://chirpie.ai/.well-known/oauth-protected-resource, which names Chirpie as the authorization server. From there, as OpenAI documents it:

1. ChatGPT registers itself with Chirpie through dynamic client registration, once for this app.
2. ChatGPT opens the Chirpie sign-in page on chirpie.ai. Check the address before you type anything. If you are already signed in to chirpie.ai in that browser, it skips straight on.
3. ChatGPT exchanges the authorization code (with PKCE, S256) for an access token and sends it on every request to https://chirpie.ai/mcp. Chirpie advertises the offline_access scope, so ChatGPT also receives a refresh token and stays connected after the first token expires. ChatGPT never sees your Chirpie password or any social platform password.

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

Which tools ask before they run?

ChatGPT treats a tool as a write action unless it is marked read-only, and may ask you to confirm a write before it runs, depending on the app's permissions, the action's context and its potential impact. OpenAI's developer docs say write actions require confirmation by default, and that you can remember an approval for the rest of a conversation. Chirpie marks its read tools (listing posts and accounts, analytics, comments) read-only, so those run without a confirmation; posting, scheduling, editing, deleting and connecting accounts are writes. Review the app's permissions in your settings so you know when ChatGPT will ask.

Every tool's annotations are in the table under Which tools ask before they run? on the MCP Server page.

What can I ask ChatGPT 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."

If ChatGPT reaches for a different tool, name the app in the prompt, for example "use the Chirpie app to schedule this". Every tool and its parameters are on the MCP Server page.

Use Chirpie from the OpenAI Responses API

Add Chirpie as an mcp tool with server_url set to https://chirpie.ai/mcp, and put a Chirpie API key in authorization. The Responses API lists Chirpie's tools and lets the model call them. By default it pauses before every call with an mcp_approval_request, which you answer in a follow-up request.

import OpenAI from "openai";
const client = new OpenAI();

const chirpie = {
  type: "mcp" as const,
  server_label: "chirpie",
  server_description: "Publish, schedule and read social posts.",
  server_url: "https://chirpie.ai/mcp",
  authorization: process.env.CHIRPIE_API_KEY,
  require_approval: {
    never: { tool_names: ["chirpie_list_accounts", "chirpie_list_posts", "chirpie_analytics"] },
  },
};

// Your own approval step: show the tool and its arguments to a person and return their answer.
declare function askPerson(tool: string, args: string): Promise<boolean>;

let response = await client.responses.create({
  model: "gpt-6-astra",
  tools: [chirpie],
  input: "Post 'Release 2.0 is live' to my X account.",
});

// Publishing tools still need approval, and an approved call can lead to another request.
for (;;) {
  const requests = response.output.filter((item) => item.type === "mcp_approval_request");
  if (requests.length === 0) break;

  const answers = [];
  for (const request of requests) {
    answers.push({
      type: "mcp_approval_response" as const,
      approval_request_id: request.id,
      approve: await askPerson(request.name, request.arguments),
    });
  }

  response = await client.responses.create({
    model: "gpt-6-astra",
    tools: [chirpie], // authorization is not stored, so send it again
    previous_response_id: response.id,
    input: answers,
  });
}

console.log(response.output_text);

• The key: create one in the dashboard and narrow it with scopes, for example posts:read, posts:write, media:write, accounts:read and analytics:read. Leave out keys:write. OpenAI does not store the authorization value, so send it with every request, and keep it in your server's environment.
• OAuth instead: authorization also takes an OAuth access token. The Responses API does not run the sign-in for you, so your application would have to complete Chirpie's OAuth flow itself; an API key is simpler for a server.
• Approvals: the example skips approval for three read-only tools only, so a post, a schedule or a delete always waits for the mcp_approval_response. Each executed call comes back as an mcp_call item.
• Fewer tools: allowed_tools imports only the tools you name, which cuts the tokens spent on tool definitions.
• Model: gpt-6-astra is the model in OpenAI's own MCP examples; any model OpenAI lists as supporting the MCP tool works.

Frequently asked questions

Is Chirpie in the ChatGPT plugin directory?

Not yet. You add Chirpie yourself as a developer-mode app with the address https://chirpie.ai/mcp, which works without a directory listing.

Which ChatGPT plans can post through Chirpie?

OpenAI's help center makes full MCP support, the part that lets an app publish, available to ChatGPT Business, Enterprise and Education workspaces on the web. On Pro, developer mode connects MCP servers with read and fetch permissions only, so ChatGPT can read your Chirpie posts and analytics but not publish. OpenAI's developer docs also list Plus for developer mode without saying which permissions it gets. The free plan does not include developer mode, and MCP apps do not run in the mobile apps.

Can ChatGPT post to Instagram, Facebook or Threads through Chirpie?

Not yet. Instagram, Facebook and Threads are coming soon to Chirpie. Today ChatGPT can publish through Chirpie to X, Bluesky, LinkedIn, Mastodon and Telegram.

Should I connect with sign-in or with an API key?

In ChatGPT, use sign-in. There is no key to create or store, and you can remove the app at any time. With the OpenAI Responses API, send a Chirpie API key narrowed with scopes in the mcp tool's authorization field, and keep it in your server's environment rather than in code.

Does using Chirpie from ChatGPT cost anything extra?

Not on Chirpie's side. Posts made from ChatGPT count against your Chirpie plan's monthly post quota exactly as posts made from the API or the dashboard do, and the hosted MCP server is included on every Chirpie plan, including the free one. On OpenAI's side, developer mode needs a paid ChatGPT plan, and the Responses API bills the tokens used for tool definitions and calls with no extra fee per call.

Sources: Developer mode and MCP apps in ChatGPT (OpenAI Help Center), ChatGPT Developer mode, Connect and test your plugin, Authentication, MCP servers in the Responses API (OpenAI, read 2026-10-04).