apiary-mcp.yml
Apiary publishes NO Model Context Protocol server — not remote, not stdio. The tools below are a CANDIDATE surface derived by API Evangelist from the nine operations Apiary actually publishes, so an agent author can see what an Apiary MCP server would expose. Nothing here is callable today.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
Tools
get_me— Get the authenticated Apiary user, including the teams they belong to.list_my_apis— List the API Projects the authenticated user can access — personal and team, public and private.list_team_apis— List the API Projects belonging to one team.fetch_blueprint— Fetch the published API description document (API Blueprint or Swagger) for one API Project.publish_blueprint— Replace the published API description document for one API Project. DESTRUCTIVE — overwrites the current revision with no server-side undo.create_api_project— Create a new API Project from an API description document.list_authorization_tokens— List the account's authorization tokens by description (values are not returned).create_authorization_token— Mint a new authorization token.delete_authorization_token— Revoke an authorization token by its description.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.