get_how_we_work — MERA Robotics MCP Tool Read-only
get_how_we_work
(get how we work) is one of 13 tools on the
MERA Robotics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_how_we_work from your client
- Claude Code MERA Robotics get_how_we_work run in your project directory
- Claude Desktop MERA Robotics get_how_we_work ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MERA Robotics get_how_we_work ~/.cursor/mcp.json
- VS Code MERA Robotics get_how_we_work .vscode/mcp.json
- Zed MERA Robotics get_how_we_work ~/.config/zed/settings.json
- Windsurf MERA Robotics get_how_we_work ~/.codeium/windsurf/mcp_config.json
- Cline MERA Robotics get_how_we_work ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MERA Robotics get_how_we_work ~/.gemini/settings.json
- Grok MERA Robotics get_how_we_work .mcp.json (in your project root)
- ChatGPT MERA Robotics get_how_we_work Settings → Connectors → Advanced → Developer mode
- Claude.ai MERA Robotics get_how_we_work Settings → Connectors → Add custom connector
- LangChain MERA Robotics get_how_we_work pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mera https://merarobotics.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.