open-bounties — APEX EVM Reads MCP Resource
open-bounties
is one of 4 resources on the
APEX EVM Reads
MCP server. Connect the server and your client can attach it as context.
by client
How to attach open-bounties from your client
- Claude Code APEX EVM Reads Resource/open-bounties run in your project directory
- Claude Desktop APEX EVM Reads Resource/open-bounties ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor APEX EVM Reads Resource/open-bounties ~/.cursor/mcp.json
- VS Code APEX EVM Reads Resource/open-bounties .vscode/mcp.json
- Zed APEX EVM Reads Resource/open-bounties ~/.config/zed/settings.json
- Windsurf APEX EVM Reads Resource/open-bounties ~/.codeium/windsurf/mcp_config.json
- Cline APEX EVM Reads Resource/open-bounties ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI APEX EVM Reads Resource/open-bounties ~/.gemini/settings.json
- Grok APEX EVM Reads Resource/open-bounties .mcp.json (in your project root)
- ChatGPT APEX EVM Reads Resource/open-bounties Settings → Connectors → Advanced → Developer mode
- Claude.ai APEX EVM Reads Resource/open-bounties Settings → Connectors → Add custom connector
- LangChain APEX EVM Reads Resource/open-bounties pip install langchain-mcp-adapters
Other resources on this server
APEX EVM Reads also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 13 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.