http_trace_review — knowledge commons MCP Prompt
http_trace_review
is one of 3 prompts on the
knowledge commons
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke http_trace_review from your client
- Claude Code knowledge commons Prompt/http_trace_review run in your project directory
- Claude Desktop knowledge commons Prompt/http_trace_review ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor knowledge commons Prompt/http_trace_review ~/.cursor/mcp.json
- VS Code knowledge commons Prompt/http_trace_review .vscode/mcp.json
- Zed knowledge commons Prompt/http_trace_review ~/.config/zed/settings.json
- Windsurf knowledge commons Prompt/http_trace_review ~/.codeium/windsurf/mcp_config.json
- Cline knowledge commons Prompt/http_trace_review ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI knowledge commons Prompt/http_trace_review ~/.gemini/settings.json
- Grok knowledge commons Prompt/http_trace_review .mcp.json (in your project root)
- ChatGPT knowledge commons Prompt/http_trace_review Settings → Connectors → Advanced → Developer mode
- Claude.ai knowledge commons Prompt/http_trace_review Settings → Connectors → Add custom connector
- LangChain knowledge commons Prompt/http_trace_review pip install langchain-mcp-adapters
Other prompts on this server
knowledge commons also offers 2 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 14 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.