mcpbeat Sign in

Medusa MCP Server

answering

Medusa is answering right now. Last checked 4 min ago.

Work with your Medusa Cloud projects' data and APIs, and search the Medusa documentation.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
392 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Medusa every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add cloud --transport http https://cloud.medusajs.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cloud": {
      "url": "https://cloud.medusajs.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cloud]
url = "https://cloud.medusajs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cloud": {
      "url": "https://cloud.medusajs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cloud": {
      "url": "https://cloud.medusajs.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://cloud.medusajs.com/mcp streamable-http sign-in 453 ms 4 min ago

Alternatives to Medusa

same job, measured the same way
DarkFunnels documentation
by darkfunnels

Search and read the DarkFunnels docs: WhatsApp AI sales agents connected by QR, no Meta Cloud API.

3 tools answering
ByJG Open Source Docs
by byjg

Search the ByJG open source documentation: PHP, DevOps, Helm, JavaScript and AI projects.

3 tools answering
Citepath
by arif-js

Self-hosted search over your documentation, with citations, for AI assistants and apps

local only
CollHub
by collhub

Documents, projects, comments, workflows and data sources of your CollHub instance, as tools.

100 installs/wk local only
Medusa MCP
by medusajs

Retrieve information from the Medusa documentation to assist you with your Medusa development.

answering
MTA:SA Documentation MCP Server
by luminaire1337

MCP server for MTA:SA documentation with intelligent search and caching

37 installs/wk local only
D
Dillie MCP
by gravity8

Manage dillie projects, tasks, and sprints; look up members and search platform documentation.

answering
Membase
by membase

Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.

answering

Medusa — questions

Answers built from our own checks of this server.

Why is there no tool list for Medusa?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Medusa working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 392 ms. The bar chart above shows every period we have measured.
How do I connect Medusa?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Medusa?
No API key is involved. Medusa answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Medusa?
It answers our handshake in 392 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.