SocialiQDocs
PlaygroundOpenAPIGet API key

Agent access

MCP server

Connect AI clients to SocialiQ through the Model Context Protocol. MCP clients authorize through SocialiQ sign-in, so users do not need to copy a REST API key into the client.

Server URL

Use the hosted Streamable HTTP endpoint:

[ .MCP ]
https://api.socialiq.dev/mcp

Authorization

Remote MCP clients discover SocialiQ's OAuth endpoints from the MCP server and send users through SocialiQ sign-in. The issued token is scoped to v1:read, expires automatically, and maps to the same billing account as REST API usage.

Tools

  • socialiq_resolve resolves URLs, handles, and IDs into canonical resource addresses.
  • socialiq_search_posts and socialiq_search_users search normalized posts and profiles.
  • socialiq_get_post and socialiq_get_user fetch individual normalized resources.
  • socialiq_list_post_comments, socialiq_list_user_posts, and socialiq_trending_feed page through common collections.
  • socialiq_get_company, socialiq_list_company_posts, and socialiq_search_jobs cover LinkedIn-style company and job workflows.

Billing and safety

  • MCP calls are read-only and use the same normalized response envelopes as REST.
  • Billable live calls count against the authorizing SocialiQ account.
  • Use REST API keys for server-to-server integrations that do not have a human OAuth authorization step.