specific-metrics — coderegistry MCP Prompt

specific-metrics is one of 4 prompts on the coderegistry MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke specific-metrics from your client

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

Other prompts on this server

• batch-analysis
• comparison
• first-analysis

coderegistry also offers 34 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 24 September 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.