Use PostWire inside CoreSpeed, Composio or any MCP gateway

Register https://postwire.io/api/mcp as a remote MCP server in the gateway, with OAuth, and each person signs in to their own PostWire account. PostWire's server publishes its OAuth discovery (RFC 9728 and RFC 8414) and accepts dynamic client registration (RFC 7591) with any https:// redirect, so CoreSpeed, Composio and self-hosted gateways register themselves. Your agents keep the gateway's memory, approvals and logs, and get PostWire's tools: a native draft per network, publishing to TikTok, Instagram, Facebook Pages, YouTube, LinkedIn, Bluesky, Mastodon, Telegram and Discord (X, Threads and Reddit are not available).

Prefer OAuth: every member connects their own social accounts and nobody shares a key. Use an API key only when the gateway cannot do OAuth, and keep it in the gateway's encrypted secret store.

Updated . Written from PostWire's own code; vendor prices read on Oct 4, 2026. Live networks: TikTok, Instagram, YouTube, LinkedIn (personal profiles), Facebook Pages, Bluesky, Mastodon, Telegram, Discord — not X, Threads, Reddit or Pinterest.

CoreSpeed, step by step

An organization admin registers the connector once; each member then signs in to PostWire from CoreSpeed's dashboard.

  1. Open Connectors as an organization admin

    In CoreSpeed go to Dashboard → Connectors (app.corespeed.io/connectors) and add a remote MCP server. Only org admins can register one; it is visible only to your organization.

  2. Register PostWire with OAuth

    URL https://postwire.io/api/mcp, slug postwire, auth mode oauth. CoreSpeed discovers PostWire's authorization server and registers itself with the redirect https://app.corespeed.io/connectors/callback, which PostWire accepts. From a terminal, the same thing:

    cs remote add postwire --url https://postwire.io/api/mcp --auth oauth --name PostWire
  3. Each member signs in to PostWire

    From the dashboard each member authorizes their own account: an email and a 6-digit code, which also creates a free PostWire account if they have none. The tools appear in tools/list once that member has signed in.

  4. Connect the social networks

    Ask the agent to call org__postwire__create_connect_link. It returns a one-hour link; the member signs in to each network on the network's own page. PostWire never shows the agent, or CoreSpeed, a platform token.

  5. Write, approve, publish

    org__postwire__generate_posts writes a draft per network and publishes nothing. Show the drafts, get a yes, then org__postwire__post_to_social with the approved drafts as per_platform. A CoreSpeed approval policy such as "ask me before anything is posted publicly" adds a second check.

Static bearer instead of OAuth: CoreSpeed's static_bearer mode sends one org-wide Authorization: Bearer pw_live_… (encrypted at rest on their side). Every member then posts through the same PostWire account and its connected networks, which suits one shared company account, not a team with separate brands.

Adding PostWire to each gateway

From each gateway's own docs, read on Oct 4, 2026.

GatewayHow you add a remote MCP serverSign-in optionsWho can add it
CoreSpeedDashboard → Connectors, the manage__remote_add tool, POST /connectors/org, or cs remote addOAuth per member (auto registration), one org-wide bearer, or noneAn organization admin
ComposioAPI or SDK only (experimental): custom toolkits upsertDCR OAuth, API key in a header, or noneAnyone with the project API key
Pipedream ConduitSelf-hosted: Settings → Connectors → MCP (remote)OAuth (dynamic registration or your client), header token, or noneA Conduit admin

Checked on Oct 4, 2026 (2026-10-04) on each vendor's own pricing or docs page, linked in the first column and below. Monthly billing in USD unless noted. "Not listed" means we could not find it on their page, not that it is missing.

Where the others are ahead of PostWire

  • What a gateway adds on top of PostWire: memory shared between agents and approval policies (CoreSpeed), hundreds of other toolkits in one session (Composio), audit logs and spend caps. PostWire itself only writes and publishes posts.
Sources, all read on Oct 4, 2026:

Composio

Composio's Custom MCP is experimental and API-only (no dashboard yet). Register PostWire as a custom toolkit with OAuth (dynamic registration) or with an API key, then connect an account and add the CUSTOM_POSTWIRE toolkit to a session.

curl --request POST \
  --url https://backend.composio.dev/api/v3.1/custom/toolkits/upsert \
  --header "x-api-key: $COMPOSIO_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "slug": "POSTWIRE",
    "toolkit_config": {
      "name": "PostWire",
      "app_url": "https://postwire.io/api/mcp",
      "auth_schemes": [
        { "mode": "DCR_OAUTH", "discovery_url": "https://postwire.io/.well-known/oauth-authorization-server" }
      ]
    }
  }'

For a key instead, use { "mode": "API_KEY", "headers": { "Authorization": "Bearer {{generic_api_key}}" } } and store the PostWire key (dashboard → API & MCP) on the connected account. Composio says app_url and auth_schemes cannot change after registration (a change answers 409: delete and register again), and new tools need a manual sync. Composio does not document the redirect URI its OAuth registration uses; PostWire accepts any https:// one.

Pipedream and any other gateway

Pipedream: its hosted MCP serves Pipedream's own apps; adding an arbitrary server is done in Conduit, its self-hosted gateway, under Settings → Connectors → MCP (remote), by URL, with OAuth (dynamic registration), a header token, or none.

Any other gateway or client that speaks Streamable HTTP: add https://postwire.io/api/mcp. What PostWire's server offers, so you can check your gateway supports it:

  • Protected resource metadata: https://postwire.io/.well-known/oauth-protected-resource/api/mcp (RFC 9728), pointing at the authorization server https://postwire.io.
  • Authorization server metadata: https://postwire.io/.well-known/oauth-authorization-server (RFC 8414): authorization code with PKCE (S256), refresh tokens, dynamic client registration (RFC 7591), the iss response parameter (RFC 9207), client ID metadata documents.
  • Redirect URIs: any https:// URL, or http://localhost / http://127.0.0.1 on any port. Custom schemes (app://…) are refused.
  • Or an API key as Authorization: Bearer pw_live_….
  • initialize, tools/list and list_platforms answer without credentials, so a gateway can list the tools before anyone signs in.

For one agent instead of a gateway, the one-line setup is set up https://postwire.io/SKILL.md (the skill), and every client's config is on /mcp/.

Questions people ask

Can I add PostWire to CoreSpeed?

Yes. An organization admin registers https://postwire.io/api/mcp as a remote connector in Dashboard → Connectors (or with cs remote add), with OAuth; each member then signs in to their own PostWire account. Its tools appear as org__postwire__… .

Does Composio support PostWire's MCP server?

Through Composio's Custom MCP, which is experimental and API-only on Oct 4, 2026: register a custom toolkit with app_url https://postwire.io/api/mcp and DCR_OAUTH (or an API key header), then connect an account and add CUSTOM_POSTWIRE to a session.

Does the gateway or the agent see my social media passwords or tokens?

No. Each network is connected on the network's own page through a PostWire connect link; the platform tokens are stored encrypted by PostWire and never returned by any tool. The gateway holds only the PostWire OAuth token (or API key) it uses to call PostWire.

Which networks can an agent post to through PostWire?

TikTok, Instagram (business or creator), Facebook Pages, YouTube, LinkedIn (personal profiles), Bluesky, Mastodon, Telegram and Discord. X, Threads and Reddit are not available on PostWire today.

What does it cost?

PostWire's free plan is 1 business, 20 posts a month and 2 networks per post, no card and no time limit; paid plans start at $9 a month. The gateway bills separately under its own plan.