mcpbeat Sign in

StudioMeyer Crew MCP Server

answering

StudioMeyer Crew is answering right now. Last checked 11 min ago.

Agent personas for Claude. 16 tools, 13 personas, 3 workflows. Zero extra API cost. Free.

Uptime history 47 days of history · worst day 90%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
278 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check StudioMeyer Crew 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 11 min ago.

run in your terminal
claude mcp add crew --transport http https://crew.studiomeyer.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "crew": {
      "url": "https://crew.studiomeyer.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.crew]
url = "https://crew.studiomeyer.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "crew": {
      "url": "https://crew.studiomeyer.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "crew": {
      "url": "https://crew.studiomeyer.io/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://crew.studiomeyer.io/mcp streamable-http sign-in 266 ms 11 min ago

Alternatives to StudioMeyer Crew

same job, measured the same way
ToolAPI
by toolapi

Free public MCP for AI agents — 193 tools, 44 workflows. No API key.

193 tools answering
Aichat
by rcgalbo

Inter-agent communication for multi-agent Claude Code workflows.

51 installs/wk local only
AgentUtility Browser Workflow
by agentutility

MCP server for the @agentutility browser-workflow cluster — pay-per-call x402 tools, no API keys…

69 installs/wk local only
Pallas Athena Tools
by nous-ehr

athenahealth DataView, API, and workflow tools for Claude Code with learning loop

29 installs/wk local only
Slang Workflows
by shofer-dev

Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor).

32 installs/wk local only
MCP Cost Tracker Router
by dbsectrainer

Real-time cost awareness for MCP agent workflows

25 installs/wk local only
0pi
by dizzydes

Free, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.

40 installs/wk local only
tokencast
by krulewis

Pre-execution cost estimation for LLM agent workflows with calibration learning

41 installs/wk local only

StudioMeyer Crew — questions

Answers built from our own checks of this server.

Why is there no tool list for StudioMeyer Crew?
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 StudioMeyer Crew working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 278 ms. The bar chart above shows every period we have measured.
How do I connect StudioMeyer Crew?
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 StudioMeyer Crew?
No API key is involved. StudioMeyer Crew 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 StudioMeyer Crew?
It answers our handshake in 278 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.