SocialSpool MCP connector
Connect ChatGPT or any remote MCP client to SocialSpool to list accounts, validate posts, create drafts, schedule publishing, publish now, and check status.
ChatGPT should connect to the MCP transport endpoint:
https://mcp.socialspool.com/mcpOAuth authorization uses the existing SocialSpool account session at https://socialspool.com.
Run the standalone MCP service locally:
bun run mcp:devUse this transport URL while testing with an HTTPS tunnel:
http://localhost:8787/mcpChatGPT connects to SocialSpool over OAuth. Do not paste API keys into ChatGPT. Authorization opens the SocialSpool web session at https://socialspool.com/oauth/authorize.
MCP endpoint:
https://mcp.socialspool.com/mcp{
"mcpServers": {
"socialspool": {
"url": "https://mcp.socialspool.com/mcp"
}
}
}For local development, start the MCP service and point Cursor at http://localhost:8787/mcp.
{
"mcpServers": {
"socialspool-local": {
"url": "http://localhost:8787/mcp"
}
}
}SocialSpool ships a Streamable HTTP MCP server. Claude Desktop local config needs a stdio command that bridges to the remote endpoint and opens the OAuth browser flow.
{
"mcpServers": {
"socialspool": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.socialspool.com/mcp"
]
}
}
}For local testing, run bun run mcp:dev first and replace the bridge URL with http://localhost:8787/mcp.
The public socialspool/agent-skill repo is not published yet. Until then, use the local repo-ready files in agent-skill/ or the packaged CLI skill at packages/cli/SKILL.md.
# Future public install path after the repo exists:
npx skills add socialspool/agent-skillThe connector uses OAuth 2.1 authorization code flow with PKCE. The MCP server is the protected resource and the existing SocialSpool web app is the authorization server.
- Protected resource metadata:
https://mcp.socialspool.com/.well-known/oauth-protected-resource(path-aware clients may also requesthttps://mcp.socialspool.com/.well-known/oauth-protected-resource/mcp) - Authorization server metadata:
https://socialspool.com/.well-known/oauth-authorization-server - Authorization endpoint:
https://socialspool.com/oauth/authorize - Token endpoint:
https://socialspool.com/oauth/token
Access is gated by the same SocialSpool account, workspace, email verification, and plan checks as the public API.
SocialSpool is listed on Smithery for hosted MCP discovery:
https://smithery.ai/servers/TheSethRose/SocialSpool
Additional directory listings are planned for Glama Registry, Cursor Directory, and the official MCP registry after those server pages are published.
Tool definitions are generated from the shared public action contracts, so MCP, CLI, OpenAPI, and /api/v1 stay aligned.
socialspool_me_getVerify the connected SocialSpool workspace and granted connector scopes.
socialspool_capabilities_getGet SocialSpool workspace limits, feature availability, and platform publishing capabilities.
socialspool_accounts_listList connected SocialSpool publishing accounts available for scheduling or publishing.
socialspool_analytics_workspaceGet lightweight SocialSpool workspace analytics, including recent post performance and collection status.
socialspool_analytics_postGet proof-of-publish and latest analytics metrics for one SocialSpool post.
socialspool_posts_listList SocialSpool posts in the current workspace, optionally filtered by status.
socialspool_posts_getGet a single SocialSpool post by id.
socialspool_posts_timelineGet lifecycle events and target publishing status for a SocialSpool post.
socialspool_posts_validateValidate SocialSpool post content against selected accounts and platform constraints before scheduling or publishing.
socialspool_posts_createCreate a SocialSpool draft, scheduled post, or immediate publish request.
socialspool_posts_scheduleSchedule an existing SocialSpool draft for future publishing.
socialspool_posts_publish_nowQueue an existing SocialSpool draft for immediate publishing.
- Social platform tokens are never exposed through MCP.
- Write tools use SocialSpool idempotency storage for safe retries.
- Cancel, delete, webhook management, and media upload tools are not exposed in the ChatGPT connector v1.
- Revoked, expired, wrong-audience, suspended, unverified, or unpaid accounts are rejected at tool-call time.
API-key based automation remains documented in the public API docs.