Virto Commerce MCP
Virto Commerce ships a real, published MCP surface, and it is a LOCAL STDIO one. The supported path is the Commerce Operations Foundation (COF) MCP server run over stdio with Virto's own adapter (@virtocommerce/mcp-onx) loaded into it; the adapter then calls a Virto Commerce Platform instance over its REST API using an api_key header. There is no Virto-hosted remote MCP endpoint an agent can POST to: the platform is self-hosted, so the "server" is always something the operator runs, either as the npx stdio process below or — separately — by installing the experimental vc-module-mcp-server module into their own platform deployment, which then exposes /api/mcp on THEIR host.
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 stdio
Tools
create-sales-order—update-order—cancel-order—get-orders—fulfill-order—get-fulfillments—get-customers—get-products—get-product-variants—get-inventory—create-return—get-returns—
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.