Muse Custom Connector
Connect posterly to Muse as a Custom Connector. Start with OpenAPI and a Bearer key. Hosted MCP is optional. Not a Muse directory listing.
Connect posterly to Muse with a Custom Connector. Start with OpenAPI and a Bearer key. Hosted MCP is optional.
The public setup page is /muse. posterly is not listed in the Muse directory yet, so you add it yourself as a Custom Connector, which takes a couple of minutes.
What Muse can do
- 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 social accounts in their own browser
Primary: OpenAPI plus Bearer
- OpenAPI: https://www.poster.ly/api/openapi
- API reference: /reference
After paid signup, copy a Bearer key that starts with pst_live_ from Dashboard → API & MCP. Prefer OAuth if Muse accepts the well-known metadata at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
Optional: hosted MCP
- MCP setup: /mcp
- Hosted MCP:
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.
Approval gates
- Validate first, show the preview, and wait for an explicit yes before publish or go-live
- Social connect stays in the browser via connect sessions
- Signup uses the existing posterly Stripe checkout handoff
Copy the agent-facing setup prompt from /muse.