Cloud9

Cloud9 MCP Server

A remote Model Context Protocol server published on cloud9.gg and advertised through RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. It is the WordPress MCP adapter fronting the Cloud9 content estate, exposed at the WordPress REST namespace `mcp` with two servers — mcp-oauth-server and mcp-adapter-default-server — plus the companion wp-abilities/v1 namespace. Authorization is OAuth 2.1 authorization code with PKCE (S256), a single coarse `mcp` scope, public clients (token_endpoint_auth_method none) and client-ID metadata documents rather than RFC 7591 dynamic registration. An anonymous tools/list call returns 401 with a well-formed WWW-Authenticate Bearer challenge carrying the resource_metadata pointer, so the live tool list and per-tool inputSchema require an authorized session. No tool inventory is published anywhere public, so none is recorded here.

GitHub

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/cloud9/refs/heads/main/mcp/cloud9-mcp.yml
🔗
ToolCrosswalk
https://raw.githubusercontent.com/api-evangelist/cloud9/refs/heads/main/mcp/cloud9-tool-crosswalk.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/cloud9/refs/heads/main/scopes/cloud9-scopes.yml

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/mcp-server"
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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: cloud9:mcp-server
name: Cloud9 MCP Server
description: A remote Model Context Protocol server published on cloud9.gg and advertised through RFC
  8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. It is the WordPress
  MCP adapter fronting the Cloud9 content estate, exposed at the WordPress REST namespace `mcp` with two
  servers — mcp-oauth-server and mcp-adapter-default-server — plus the companion wp-abilities/v1 namespace.
  Authorization is OAuth 2.1 authorization code with PKCE (S256), a single coarse `mcp` scope, public
  clients (token_endpoint_auth_method none) and client-ID metadata documents rather than RFC 7591 dynamic
  registration. An anonymous tools/list call returns 401 with a well-formed WWW-Authenticate Bearer challenge
  carrying the resource_metadata pointer, so the live tool list and per-tool inputSchema require an authorized
  session. No tool inventory is published anywhere public, so none is recorded here.
humanURL: https://cloud9.gg/
baseURL: https://cloud9.gg/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Content
properties:
- type: MCPServer
  url: mcp/cloud9-mcp.yml
- type: ToolCrosswalk
  url: mcp/cloud9-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/cloud9-scopes.yml
x-evidence:
  authorization_server: https://cloud9.gg/.well-known/oauth-authorization-server
  protected_resource: https://cloud9.gg/.well-known/oauth-protected-resource
  http_status: 200
  tools_list_status: 401
  fetched: '2026-08-09'