Cloud9 MCP Server

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'