TRACK_RECORD.md — decker MCP Resource

TRACK_RECORD.md is one of 2 resources on the decker MCP server. Connect the server and your client can attach it as context.

by client

How to attach TRACK_RECORD.md from your client

• Claude Code decker Resource/TRACK_RECORD.md run in your project directory
• Claude Desktop decker Resource/TRACK_RECORD.md ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor decker Resource/TRACK_RECORD.md ~/.cursor/mcp.json
• VS Code decker Resource/TRACK_RECORD.md .vscode/mcp.json
• Zed decker Resource/TRACK_RECORD.md ~/.config/zed/settings.json
• Windsurf decker Resource/TRACK_RECORD.md ~/.codeium/windsurf/mcp_config.json
• Cline decker Resource/TRACK_RECORD.md ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI decker Resource/TRACK_RECORD.md ~/.gemini/settings.json
• Grok decker Resource/TRACK_RECORD.md .mcp.json (in your project root)
• ChatGPT decker Resource/TRACK_RECORD.md Settings → Connectors → Advanced → Developer mode
• Claude.ai decker Resource/TRACK_RECORD.md Settings → Connectors → Add custom connector
• LangChain decker Resource/TRACK_RECORD.md pip install langchain-mcp-adapters

Other resources on this server

• operation_rules/RULES.yaml

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.