SocialBee MCP Server

Undocumented but live first-party Model Context Protocol server mounted in the WordPress REST namespace of socialbee.com. Discoverable entirely through standards — an RFC 9728 protected resource metadata document names the endpoint and an RFC 8414 authorization server metadata document describes the OAuth 2.1 authorization code + PKCE (S256) flow that guards it, with a single scope "mcp". An anonymous JSON-RPC tools/list returns a well-formed MCP 401 (mcp_unauthorized), confirming a real MCP implementation; the tool set itself is auth-gated and has not been enumerated. Note this is an agent surface over the WordPress content property, not over the SocialBee scheduling product.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/socialbee-mcp"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: socialbee:socialbee-mcp
name: SocialBee MCP Server
description: Undocumented but live first-party Model Context Protocol server mounted in the WordPress
  REST namespace of socialbee.com. Discoverable entirely through standards — an RFC 9728 protected resource
  metadata document names the endpoint and an RFC 8414 authorization server metadata document describes
  the OAuth 2.1 authorization code + PKCE (S256) flow that guards it, with a single scope "mcp". An anonymous
  JSON-RPC tools/list returns a well-formed MCP 401 (mcp_unauthorized), confirming a real MCP implementation;
  the tool set itself is auth-gated and has not been enumerated. Note this is an agent surface over the
  WordPress content property, not over the SocialBee scheduling product.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://socialbee.com
baseURL: https://socialbee.com/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agent Surface
- Authentication
tags_raw:
- MCP
- Model Context Protocol
- Agent Surface
- OAuth
properties:
- type: MCPServer
  url: mcp/socialbee-mcp.yml
- type: Authentication
  url: authentication/socialbee-authentication.yml
- type: OAuthScopes
  url: scopes/socialbee-scopes.yml
- type: ErrorCatalog
  url: errors/socialbee-problem-types.yml