get_element_properties — EOxElements MCP Tool Read-only
get_element_properties
(get element properties) 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_properties from your client
- Claude Code EOxElements get_element_properties run in your project directory
- Claude Desktop EOxElements get_element_properties ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EOxElements get_element_properties ~/.cursor/mcp.json
- VS Code EOxElements get_element_properties .vscode/mcp.json
- Zed EOxElements get_element_properties ~/.config/zed/settings.json
- Windsurf EOxElements get_element_properties ~/.codeium/windsurf/mcp_config.json
- Cline EOxElements get_element_properties ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EOxElements get_element_properties ~/.gemini/settings.json
- Grok EOxElements get_element_properties .mcp.json (in your project root)
- ChatGPT EOxElements get_element_properties Settings → Connectors → Advanced → Developer mode
- Claude.ai EOxElements get_element_properties Settings → Connectors → Add custom connector
- LangChain EOxElements get_element_properties 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.