Supported Clients
Mouse works with the following editor and AI assistant combinations. Each has a dedicated setup guide linked below.
| Editor | AI Assistant | MCP Config Location | Setup Guide |
|---|---|---|---|
| VS Code | GitHub Copilot | .vscode/mcp.json | VS Code + GitHub Copilot |
| Claude Code | Claude (CLI + UI) | .mcp.json | Claude Code |
| Cursor | Built-in (Cursor AI) | .cursor/mcp.json | Cursor |
| Kiro | Built-in (Kiro AI) | .kiro/settings/mcp.json | Kiro |
| VS Code | Amazon Q Developer | .amazonq/mcp.json | Amazon Q Developer |
| VS Code | Roo Code | .roo/mcp.json | Roo Code |
| VS Code | Kilo Code | .kilocode/mcp.json | Kilo Code |
All supported clients have been fully end-to-end verified and tested.
Supported Models
Mouse is compatible with any model that supports tool use (function calling) via the MCP protocol. The following models have been verified:
| Provider | Models |
|---|---|
| Anthropic | All Claude models (4+) |
| OpenAI | All GPT models (4o+) |
| All Gemini models (2.5+) | |
| DeepSeek | v3.2+ |
| MiniMax | M2.1, M2.5 |
| Qwen | Qwen3 Coder Next |
| Rapter | mini |
Older Claude, GPT, and Gemini models do not support tool use and are incompatible with Mouse. Models not listed above are assumed to be incompatible until verified.
Coming Soon
We are planning to extend Mouse support to the following editors:
- Visual Studio
- Windsurf
- JetBrains IDEs
- OpenCode (VS Code extension)
Verifying Compatibility
After setting up Mouse in any supported client, you can verify the connection by asking your AI assistant:
"Use Mouse's
get_file_metadatatool to check the metadata of any file in this workspace."
If the assistant successfully calls the tool and returns file metadata, Mouse is working correctly. If it can call any one Mouse tool, it can call all of them.