get_terminal_logs — BugEzy MCP Tool Read-only
get_terminal_logs
(get terminal logs) is one of 14 tools on the
BugEzy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_terminal_logs from your client
- Claude Code BugEzy get_terminal_logs run in your project directory
- Claude Desktop BugEzy get_terminal_logs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BugEzy get_terminal_logs ~/.cursor/mcp.json
- VS Code BugEzy get_terminal_logs .vscode/mcp.json
- Zed BugEzy get_terminal_logs ~/.config/zed/settings.json
- Windsurf BugEzy get_terminal_logs ~/.codeium/windsurf/mcp_config.json
- Cline BugEzy get_terminal_logs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BugEzy get_terminal_logs ~/.gemini/settings.json
- Grok BugEzy get_terminal_logs .mcp.json (in your project root)
- ChatGPT BugEzy get_terminal_logs Settings → Connectors → Advanced → Developer mode
- Claude.ai BugEzy get_terminal_logs Settings → Connectors → Add custom connector
- LangChain BugEzy get_terminal_logs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bugezy https://bugezy.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.