get_repro_context — BugTape demo MCP Tool Read-only
get_repro_context
(get repro context) is one of 14 tools on the
BugTape demo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_repro_context from your client
- Claude Code BugTape demo get_repro_context run in your project directory
- Claude Desktop BugTape demo get_repro_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BugTape demo get_repro_context ~/.cursor/mcp.json
- VS Code BugTape demo get_repro_context .vscode/mcp.json
- Zed BugTape demo get_repro_context ~/.config/zed/settings.json
- Windsurf BugTape demo get_repro_context ~/.codeium/windsurf/mcp_config.json
- Cline BugTape demo get_repro_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BugTape demo get_repro_context ~/.gemini/settings.json
- Grok BugTape demo get_repro_context .mcp.json (in your project root)
- ChatGPT BugTape demo get_repro_context Settings → Connectors → Advanced → Developer mode
- Claude.ai BugTape demo get_repro_context Settings → Connectors → Add custom connector
- LangChain BugTape demo get_repro_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.