Medusa MCP Server

Related Servers

Alternatives to Medusa MCP Server

No user-submitted related servers found.

Related Servers

Example MCP SSE Server
Autonomous Agents Developer Tools
keepview
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables real-time communication using Server-Sent Events (SSE), providing standardized model management and resource templating capabilities.
Updated a year ago (2025-06-11 04:42 UTC)
-
MCP Boilerplate
RAG Systems Agent Orchestration Developer Tools
iamsrikanthnani
A
license
Not graded
quality
D
maintenance
A server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.
Updated a year ago (2025-05-12 06:05 UTC)
8 npm
11
MIT
Cosmic MCP Server
Content Management Systems Developer Tools
patgpt
A
license
Not graded
quality
D
maintenance
A production-ready Model Context Protocol server for interacting with Cosmic headless CMS, providing comprehensive tools for managing objects, types, and media in your Cosmic bucket.
Updated a year ago (2025-10-27 10:24 UTC)
2 npm
MIT
database-mcp-server
Databases Developer Tools
cenmiao
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server for unified database access and management, supporting multiple databases with CRUD operations, transactions, metadata queries, and built-in security features.
Updated 7 months ago (2026-03-07 07:04 UTC)
4 npm
1
MIT
OpenAPI MCP Server
Developer Tools API Testing
oneWalker
A
license
Not graded
quality
D
maintenance
A server that implements the Model Context Protocol (MCP) with StreamableHTTP transport, enabling standardized interaction with model services through a RESTful API interface.
Updated a year ago (2025-07-24 14:40 UTC)
620 npm
2
MIT
mcp-server-dev-test
Developer Tools Cloud Platforms
yxb123456cy
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server implementation using Node.js, TypeScript, and Bun, designed for serverless and edge deployments on Vercel and Cloudflare.
Updated 3 months ago (2026-06-29 03:42 UTC)
1
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored 2026-04-18 10:40 across 48 tools

Disambiguation5/5

Every tool has a distinct purpose targeting specific resources and actions, such as GetCartsId for retrieving a cart by ID, PostCarts for creating a cart, and PostCartsIdComplete for completing a cart. The naming and descriptions clearly differentiate between retrieval, creation, update, and other operations, with no overlapping or ambiguous tools.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, using 'Get' for retrieval, 'Post' for creation or action, and specific identifiers like 'Id' or 'Code'. Examples include GetProductsId, PostCartsIdLineItems, and PostActor_typeAuth_provider, all adhering to a predictable and readable convention.

Tool Count2/5

With 48 tools, the count is excessive for an MCP server, making it cumbersome for agents to navigate and increasing the risk of misselection. While the server covers a broad e-commerce domain, a more streamlined set of 15-25 tools would be more appropriate for usability and coherence.

Completeness5/5

The tool set provides comprehensive coverage of the e-commerce domain, including CRUD operations for carts, products, orders, customers, and authentication, as well as specialized actions like payment processing, shipping, and returns. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.