apimesh-xyz-mcp.yml
APIMesh ships two first-party MCP servers, both distributed as npm packages that run locally over stdio. @mbeato/apimesh-mcp-server (v1.8.2, 2026-04-26) registers 76 tools that call the pay-per-call marketplace APIs on *.apimesh.xyz — 74 analysis tools plus wallet_usage and wallet_set_cap — and is listed in the official MCP registry as io.github.mbeato/apimesh, on Smithery and on Glama. @mbeato/agentcontext-mcp (v0.1.2, 2026-04-29) is the MCP face of the agentsmd wedge with two tools (read_agent_context, convert_agent_context). The provider operates no remote MCP endpoint: RETIRED.md names a former self-hosted HTTP server at mcp.apimesh.xyz, which now returns {"error":"Not found"}, and the apex /mcp path returns 401.
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.
Documentation
Documentation link · transport
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.