MCP Server Integration

The Model Context Protocol (MCP) allows AI assistants like Cursor, Claude Desktop, and autonomous agents to discover and invoke auto-social.io actions directly.

Remote MCP Endpoint

auto-social.io exposes a standards-compliant Streamable HTTP MCP server:

https://auto-social.io/api/mcp

Supported Protocols

• Transport: Streamable HTTP and JSON-RPC 2.0 POST.
• Authentication: Bearer token via Authorization: Bearer ask_... or OAuth 2.0 PKCE.
• OAuth client registration: Pre-registered clients (Cursor, Claude) or Client ID Metadata Documents (CIMD).

OAuth client registration

auto-social.io supports two MCP authorization client registration paths:

1. Pre-registration for known integrations (Cursor, Claude).
2. Client ID Metadata Documents (CIMD) for third-party MCP clients with no prior relationship.

Discovery endpoints:

GET /.well-known/oauth-protected-resourceGET /.well-known/oauth-authorization-server

The authorization server advertises client_id_metadata_document_supported: true.

Pre-registered client (Cursor and Claude)

Use this when your MCP host already ships with a fixed OAuth client.

Supported redirect URIs:

http://127.0.0.1/oauth/callbackhttps://claude.ai/api/mcp/auth_callbackhttp://localhost:8787/callbackhttp://127.0.0.1:8787/callbackhttps://www.cursor.com/agents/mcp/oauth/callback

Cursor (OAuth, recommended) in .cursor/mcp.json:

{  "mcpServers": {    "auto-social": {      "url": "https://auto-social.io/api/mcp",      "auth": {        "CLIENT_ID": "auto-social-mcp",        "scopes": ["mcp:tools"]      }    }  }}

Claude uses the same pre-registered client_id with redirect URI https://claude.ai/api/mcp/auth_callback.

Need another redirect URI for a pre-registered integration? Open a support request or PR adding it to the mcp_oauth_clients allowlist.

Client ID Metadata Documents (third-party clients)

If you build your own MCP client, host a JSON metadata document at an HTTPS URL and use that URL as client_id.

Requirements:

• client_id URL uses https:// and includes a path (for example https://your-app.com/oauth/mcp-client.json).
• Document includes client_id, client_name, and redirect_uris.
• Document client_id matches the URL exactly.
• Authorization request redirect_uri is listed in redirect_uris.

Example metadata document:

{  "client_id": "https://your-app.com/oauth/mcp-client.json",  "client_name": "Your MCP Client",  "client_uri": "https://your-app.com",  "redirect_uris": [    "http://127.0.0.1:8787/callback",    "http://localhost:8787/callback"  ],  "grant_types": ["authorization_code"],  "response_types": ["code"],  "token_endpoint_auth_method": "none"}

On authorize, auto-social.io fetches the document, validates it, and caches it using HTTP cache headers when present.

Configuring Cursor

To use auto-social.io tools inside Cursor:

1. Open Cursor Settings, Features, MCP Servers.
2. Click Add New MCP Server.
3. Choose HTTP as transport type.
4. Set URL to https://auto-social.io/api/mcp.
5. Click Authenticate (OAuth with pre-registered auto-social-mcp) or set Authorization: Bearer ask_your_api_key.

Alternatively, configure your project's .cursor/mcp.json with OAuth (recommended) or an API key:

{  "mcpServers": {    "auto-social": {      "url": "https://auto-social.io/api/mcp",      "auth": {        "CLIENT_ID": "auto-social-mcp",        "scopes": ["mcp:tools"]      }    }  }}

API key fallback:

{  "mcpServers": {    "auto-social": {      "url": "https://auto-social.io/api/mcp",      "headers": {        "Authorization": "Bearer ask_your_api_key"      }    }  }}

Configuring Claude Code

claude mcp add --transport http auto-social https://auto-social.io/api/mcp

Complete the OAuth browser flow when prompted. You can also pass an API key with a Bearer header if your MCP host supports custom headers.

Available MCP Tools

When connected, your agent receives full schemas and descriptions for all registry tools (same set as REST and CLI). Highlights:

Brands

• list_brands / get_brand / create_brand / update_brand / delete_brand
• analyze_brand / get_brand_analysis_run
• assign_brand_integrations / set_brand_weekly_refresh

Prefer get_brand to read a profile. Call analyze_brand only when the user asked to analyze, or right after create_brand with URLs/accounts. See Brands.

Campaigns and account

• list_campaigns / get_campaign_status / pause_campaign / resume_campaign
• create_campaign / update_campaign
• list_integrations / get_account
• search_docs: product help (credits, plans, formats, MCP/CLI). Short English keyword query.

Posts and media

• list_posts / get_post / create_post
• generate_social_copy / generate_image_asset / generate_video_asset / generate_audio_asset
• preview_publication / publish_post
• update_published_post / delete_published_post
• list_account_posts / diagnose_publication_failure

All four media tools require post_id (from create_post or list_posts). They consume credits and do not use the sensitive confirmation_code flow. Image, video, and audio responses include a public CDN url in the compact payload (post_id, media_id, kind, url, status).

Typical content workflow: create_post → generate_* → preview_publication → publish_post.

Sensitive mutations (publish_post, campaign pause/resume/create/update, live update/delete, delete_brand) return a 6-digit confirmation_code on the first call. Retry with the same payload plus that code.

Full overview: Agent guide. OpenAPI: GET /api/v1/openapi.json.