get_element_slots — EOxElements MCP Tool Read-only
get_element_slots
(get element slots) is one of 10 tools on the
EOxElements
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_element_slots from your client
- Claude Code EOxElements get_element_slots run in your project directory
- Claude Desktop EOxElements get_element_slots ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EOxElements get_element_slots ~/.cursor/mcp.json
- VS Code EOxElements get_element_slots .vscode/mcp.json
- Zed EOxElements get_element_slots ~/.config/zed/settings.json
- Windsurf EOxElements get_element_slots ~/.codeium/windsurf/mcp_config.json
- Cline EOxElements get_element_slots ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EOxElements get_element_slots ~/.gemini/settings.json
- Grok EOxElements get_element_slots .mcp.json (in your project root)
- ChatGPT EOxElements get_element_slots Settings → Connectors → Advanced → Developer mode
- Claude.ai EOxElements get_element_slots Settings → Connectors → Add custom connector
- LangChain EOxElements get_element_slots pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http eoxelements https://elements.mcp.eox.atOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.