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