decode-event — Subtensor MCP MCP Prompt
decode-event
is one of 11 prompts on the
Subtensor MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke decode-event from your client
- Claude Code Subtensor MCP Prompt/decode-event run in your project directory
- Claude Desktop Subtensor MCP Prompt/decode-event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Subtensor MCP Prompt/decode-event ~/.cursor/mcp.json
- VS Code Subtensor MCP Prompt/decode-event .vscode/mcp.json
- Zed Subtensor MCP Prompt/decode-event ~/.config/zed/settings.json
- Windsurf Subtensor MCP Prompt/decode-event ~/.codeium/windsurf/mcp_config.json
- Cline Subtensor MCP Prompt/decode-event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Subtensor MCP Prompt/decode-event ~/.gemini/settings.json
- Grok Subtensor MCP Prompt/decode-event .mcp.json (in your project root)
- ChatGPT Subtensor MCP Prompt/decode-event Settings → Connectors → Advanced → Developer mode
- Claude.ai Subtensor MCP Prompt/decode-event Settings → Connectors → Add custom connector
- LangChain Subtensor MCP Prompt/decode-event pip install langchain-mcp-adapters
Other prompts on this server
Subtensor MCP also offers 20 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 5 November 2026.
A listing does not declare its prompts, 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 prompt's arguments.