get_bug_events — BugTape demo MCP Tool Read-only
get_bug_events
(get bug events) 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_bug_events from your client
- Claude Code BugTape demo get_bug_events run in your project directory
- Claude Desktop BugTape demo get_bug_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BugTape demo get_bug_events ~/.cursor/mcp.json
- VS Code BugTape demo get_bug_events .vscode/mcp.json
- Zed BugTape demo get_bug_events ~/.config/zed/settings.json
- Windsurf BugTape demo get_bug_events ~/.codeium/windsurf/mcp_config.json
- Cline BugTape demo get_bug_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BugTape demo get_bug_events ~/.gemini/settings.json
- Grok BugTape demo get_bug_events .mcp.json (in your project root)
- ChatGPT BugTape demo get_bug_events Settings → Connectors → Advanced → Developer mode
- Claude.ai BugTape demo get_bug_events Settings → Connectors → Add custom connector
- LangChain BugTape demo get_bug_events 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.