get_test_protocol — Maglev Parts MCP Tool Read-only
get_test_protocol
(get test protocol) is one of 17 tools on the
Maglev Parts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_test_protocol from your client
- Claude Code Maglev Parts get_test_protocol run in your project directory
- Claude Desktop Maglev Parts get_test_protocol ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Maglev Parts get_test_protocol ~/.cursor/mcp.json
- VS Code Maglev Parts get_test_protocol .vscode/mcp.json
- Zed Maglev Parts get_test_protocol ~/.config/zed/settings.json
- Windsurf Maglev Parts get_test_protocol ~/.codeium/windsurf/mcp_config.json
- Cline Maglev Parts get_test_protocol ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Maglev Parts get_test_protocol ~/.gemini/settings.json
- Grok Maglev Parts get_test_protocol .mcp.json (in your project root)
- ChatGPT Maglev Parts get_test_protocol Settings → Connectors → Advanced → Developer mode
- Claude.ai Maglev Parts get_test_protocol Settings → Connectors → Add custom connector
- LangChain Maglev Parts get_test_protocol pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http parts https://trymaglev.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.