Connect posterly to Muse
Add posterly to Muse as a custom connector and let Muse line up your posts across every platform you have connected. Nothing goes live until you approve it. posterly is not listed in the Muse directory yet, so you add it yourself in a couple of minutes.
Preview what is copied
# Connect posterly to Muse as a Custom Connector
Use Muse Custom Connector. Do not treat posterly as a listed Muse directory app.
Primary contract: OpenAPI plus a Bearer API key.
- OpenAPI: https://www.poster.ly/api/openapi
- Interactive API reference: https://www.poster.ly/reference
- Agents overview: https://www.poster.ly/agents
- Muse Custom Connector page: https://www.poster.ly/muse
Auth (primary):
- After paid signup, the user copies a Bearer key that starts with pst_live_ from Dashboard, API and MCP.
- Header: Authorization: Bearer pst_live_...
- Prefer OAuth if Muse Custom Connector accepts https://www.poster.ly/.well-known/oauth-protected-resource and https://www.poster.ly/.well-known/oauth-authorization-server.
- Never invent keys. Never collect card details, posterly passwords, or social-network passwords.
Optional secondary: hosted MCP, only if Muse Custom Connector accepts JSON-RPC over a single POST.
- MCP setup: https://www.poster.ly/mcp
- Hosted MCP endpoint: POST https://www.poster.ly/api/mcp
- MCP server card: https://www.poster.ly/.well-known/mcp/server-card.json
- MCP OAuth resource: https://www.poster.ly/.well-known/oauth-protected-resource/api/mcp
- Wire format: JSON-RPC 2.0 over a single POST. No SSE and no streamable HTTP in v1.
- GET https://www.poster.ly/api/mcp returns server info without auth.
- If Muse Custom Connector requires streamable HTTP, do not pretend hosted MCP works. Stay on the OpenAPI connector and tell the user about this gap.
What you can do through the posterly API:
- List connected social accounts
- Schedule posts after the user confirms the exact caption, account, media, and time
- Create browser connect sessions so the user authorises Instagram, Meta, YouTube, LinkedIn, X, and the rest in their own browser
Approval gates:
- Call whoami, then list accounts
- Prefer validate_post or REST dry_run: true first
- Show the preview
- Wait for an explicit yes
- Only then call create_post with confirm: true, or make the live REST request
- Publish and go-live always need that confirmation
- Social account connect stays in the browser via connect sessions (POST /api/v1/connect/{platform}/sessions). Poll GET /api/v1/connect/sessions/{id}
- Do not invent Autopilot behaviour or prices
Signup and Stripe:
- Start paid access with POST /api/v1/signup or send the user to https://www.poster.ly/agents/signup
- Signup uses the existing posterly Stripe checkout handoff. No API key before billing is active.
- API and MCP access is an add-on ($3/month Starter/Pro, $5/month Power, or $29/month Agency) on a paid plan.
posterly publishes to 18 platforms: Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Pinterest, Threads, Google Business, Telegram, Bluesky, Discord, Slack, Mastodon, Dev.to, Hashnode, WordPress, Lemmy.
Hosted MCP exposes 87 tools when the optional JSON-RPC POST transport is accepted. Do not scrape the dashboard. Use OpenAPI, the reference, or list_platforms.
This is the Custom Connector setup, not a listing in the Muse directory.
What Muse can do through posterly
Muse talks to the public posterly API. Keep a human in the loop for every go-live.
See your accounts
Muse works with the social accounts you have already connected to posterly.
Line up posts
Muse drafts the post, you check the caption, account, media and time, then approve.
You stay in control of logins
New social accounts are connected by you, in your own browser. Muse never sees a password.
Start with OpenAPI
Start with the OpenAPI contract and a Bearer key. Hosted MCP is optional. Paste the OpenAPI URL and a Bearer key that starts with pst_live_ from Dashboard, API and MCP after paid signup. Prefer OAuth if Muse accepts posterly well-known metadata.
OpenAPI
https://www.poster.ly/api/openapiPrimary Muse Custom Connector contract. Start here with a Bearer key.
API reference
https://www.poster.ly/referenceHuman-readable request and response docs for the same REST surface.
MCP hub
https://www.poster.ly/mcpSetup for hosted HTTP MCP and local stdio.
Hosted MCP
POST https://www.poster.ly/api/mcpOptional. JSON-RPC 2.0 over a single POST. No SSE or streamable HTTP in v1.
Hosted MCP transport gap
posterly hosted MCP is JSON-RPC 2.0 over a single POST to https://www.poster.ly/api/mcp. It does not implement SSE or streamable HTTP in v1. If Muse Custom Connector requires streamable HTTP, use the OpenAPI connector and treat hosted MCP as unsupported until that transport exists.
Copy-paste Muse setup prompt
Paste this into Muse when you create the Custom Connector. It includes the OpenAPI URL, reference, agents page, MCP endpoint, approval gates, and browser connect sessions.
# Connect posterly to Muse as a Custom Connector
Use Muse Custom Connector. Do not treat posterly as a listed Muse directory app.
Primary contract: OpenAPI plus a Bearer API key.
- OpenAPI: https://www.poster.ly/api/openapi
- Interactive API reference: https://www.poster.ly/reference
- Agents overview: https://www.poster.ly/agents
- Muse Custom Connector page: https://www.poster.ly/muse
Auth (primary):
- After paid signup, the user copies a Bearer key that starts with pst_live_ from Dashboard, API and MCP.
- Header: Authorization: Bearer pst_live_...
- Prefer OAuth if Muse Custom Connector accepts https://www.poster.ly/.well-known/oauth-protected-resource and https://www.poster.ly/.well-known/oauth-authorization-server.
- Never invent keys. Never collect card details, posterly passwords, or social-network passwords.
Optional secondary: hosted MCP, only if Muse Custom Connector accepts JSON-RPC over a single POST.
- MCP setup: https://www.poster.ly/mcp
- Hosted MCP endpoint: POST https://www.poster.ly/api/mcp
- MCP server card: https://www.poster.ly/.well-known/mcp/server-card.json
- MCP OAuth resource: https://www.poster.ly/.well-known/oauth-protected-resource/api/mcp
- Wire format: JSON-RPC 2.0 over a single POST. No SSE and no streamable HTTP in v1.
- GET https://www.poster.ly/api/mcp returns server info without auth.
- If Muse Custom Connector requires streamable HTTP, do not pretend hosted MCP works. Stay on the OpenAPI connector and tell the user about this gap.
What you can do through the posterly API:
- List connected social accounts
- Schedule posts after the user confirms the exact caption, account, media, and time
- Create browser connect sessions so the user authorises Instagram, Meta, YouTube, LinkedIn, X, and the rest in their own browser
Approval gates:
- Call whoami, then list accounts
- Prefer validate_post or REST dry_run: true first
- Show the preview
- Wait for an explicit yes
- Only then call create_post with confirm: true, or make the live REST request
- Publish and go-live always need that confirmation
- Social account connect stays in the browser via connect sessions (POST /api/v1/connect/{platform}/sessions). Poll GET /api/v1/connect/sessions/{id}
- Do not invent Autopilot behaviour or prices
Signup and Stripe:
- Start paid access with POST /api/v1/signup or send the user to https://www.poster.ly/agents/signup
- Signup uses the existing posterly Stripe checkout handoff. No API key before billing is active.
- API and MCP access is an add-on ($3/month Starter/Pro, $5/month Power, or $29/month Agency) on a paid plan.
posterly publishes to 18 platforms: Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Pinterest, Threads, Google Business, Telegram, Bluesky, Discord, Slack, Mastodon, Dev.to, Hashnode, WordPress, Lemmy.
Hosted MCP exposes 87 tools when the optional JSON-RPC POST transport is accepted. Do not scrape the dashboard. Use OpenAPI, the reference, or list_platforms.
Approval gates
These rules stay the same as every other posterly agent.
Validate the post, show the preview, and wait for an explicit yes before publish or go-live.
Social account connect stays in the browser via connect sessions. Agents never collect provider passwords.
Signup uses the existing posterly Stripe checkout handoff. No API key before billing is active.
Post to 18 platforms
Once connected, Muse can schedule through posterly to every supported social platform.
Pricing
One Stripe subscription: your plan plus API and MCP. Charged now, no free trial.
API, MCP and Agent Access
Starter $7 + API $3, charged now. No free trial on this path.
- Muse Custom Connector uses OpenAPI first. Hosted MCP is optional when the JSON-RPC POST transport is accepted
- 87 hosted HTTP MCP tools for accounts, connect sessions, scheduling, media, and analytics
- 100 create-post requests/hour plus separate media/read limits
- All 18 supported platforms
Muse questions
Is posterly listed in the Muse directory?+
Not yet. Today you add posterly yourself as a custom connector, which takes a couple of minutes. We will update this page if posterly is added to the Muse directory.
Does Muse Custom Connector use MCP or OpenAPI?+
Start with OpenAPI at https://www.poster.ly/api/openapi and a Bearer key that starts with pst_live_. Hosted MCP is optional. If Muse accepts MCP, use POST https://www.poster.ly/api/mcp. Hosted MCP is JSON-RPC 2.0 over a single POST. It does not implement SSE or streamable HTTP in v1. If Muse Custom Connector requires streamable HTTP, stay on OpenAPI and treat hosted MCP as a known gap.
How does Muse authenticate to posterly?+
After paid signup, copy a Bearer API key that starts with pst_live_ from Dashboard, API and MCP. Prefer OAuth if Muse Custom Connector accepts posterly well-known metadata at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. Never invent keys or collect card details in chat.
Can Muse publish a post without asking me?+
No. Validate first, show the exact caption, account, media, and time, then wait for an explicit yes. Live create_post needs confirm: true. Social account connection stays in the user browser through connect sessions.
How does Stripe checkout work from Muse?+
Agent signup uses the existing posterly Stripe checkout handoff from POST /api/v1/signup or /agents/signup. No API key is issued before billing is active.
Related setup
Muse is one Custom Connector into the same API and MCP layer.
AI agents
Every client that can speak MCP or REST.
MCP hub
Hosted HTTP and local stdio setup.
Agent discovery
Safe discover, confirm, and schedule flow.
More: agents, agent signup, API reference.