Add FishOut to VS Code
https://mcp.fishout.ai/mcp, on every plan.Create .vscode/mcp.json
The top-level key is servers, not mcpServers — this is the difference that trips people coming from Cursor. Remote servers need "type": "http" stated explicitly. Or run MCP: Add Server from the command palette, which writes the same thing.
.vscode/mcp.json
{
"servers": {
"fishout": {
"type": "http",
"url": "https://mcp.fishout.ai/mcp"
}
}
}Start it, trust it and sign in
VS Code shows a Start action above the server entry. The first run asks you to trust the server, then opens your browser on FishOut: sign in, pick the organization and projects, and approve. The trust step is mandatory and cannot be skipped from the config.
Or use an API key
Where nobody can complete a browser sign-in, create a key under Settings → API & MCP and use an inputs entry with "password": true, so VS Code prompts once and keeps the key in secret storage rather than in the file.
.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "fishout-key",
"description": "FishOut API key",
"password": true
}
],
"servers": {
"fishout": {
"type": "http",
"url": "https://mcp.fishout.ai/mcp",
"headers": {
"Authorization": "Bearer ${input:fishout-key}"
}
}
}
}Use it from agent mode
Open Copilot Chat and switch to agent mode. The tools picker lists the FishOut tools; leave them all on, or select a subset. MCP tools are not available in ask or edit mode.
Check it worked. Run MCP: List Servers from the command palette and confirm FishOut is running. From there you can show its output log, which is where an auth failure appears.