Token Registry — MERX - TRON Resource Exchange MCP Resource
Token Registry
is one of 14 resources on the
MERX - TRON Resource Exchange
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Token Registry from your client
- Claude Code MERX - TRON Resource Exchange Resource/Token Registry run in your project directory
- Claude Desktop MERX - TRON Resource Exchange Resource/Token Registry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MERX - TRON Resource Exchange Resource/Token Registry ~/.cursor/mcp.json
- VS Code MERX - TRON Resource Exchange Resource/Token Registry .vscode/mcp.json
- Zed MERX - TRON Resource Exchange Resource/Token Registry ~/.config/zed/settings.json
- Windsurf MERX - TRON Resource Exchange Resource/Token Registry ~/.codeium/windsurf/mcp_config.json
- Cline MERX - TRON Resource Exchange Resource/Token Registry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MERX - TRON Resource Exchange Resource/Token Registry ~/.gemini/settings.json
- Grok MERX - TRON Resource Exchange Resource/Token Registry .mcp.json (in your project root)
- ChatGPT MERX - TRON Resource Exchange Resource/Token Registry Settings → Connectors → Advanced → Developer mode
- Claude.ai MERX - TRON Resource Exchange Resource/Token Registry Settings → Connectors → Add custom connector
- LangChain MERX - TRON Resource Exchange Resource/Token Registry pip install langchain-mcp-adapters
Other resources on this server
MERX - TRON Resource Exchange also offers 30 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 24 September 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.