Add FishOut to Cursor
https://mcp.fishout.ai/mcp, on every plan.Create the config file
Put it at ~/.cursor/mcp.json to make FishOut available in every project, or at .cursor/mcp.json in a repository to scope it to that one. The top-level key is mcpServers. A remote server is a url — do not add a type field, which Cursor does not expect for remote entries.
.cursor/mcp.json
{
"mcpServers": {
"fishout": {
"url": "https://mcp.fishout.ai/mcp"
}
}
}Sign in
Open Cursor Settings → MCP. FishOut shows as needing login; choose it and your browser opens on FishOut. Sign in, pick the organization and projects, and approve. Cursor then lists the tools the server advertises, and you can switch individual ones off from the same screen.
Or use an API key
For a machine where nobody can complete a browser sign-in, create a key under Settings → API & MCP and send it as a header. Cursor interpolates ${env:NAME}, which keeps the key out of a file you might commit; restart Cursor after setting it.
.cursor/mcp.json
{
"mcpServers": {
"fishout": {
"url": "https://mcp.fishout.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:FISHOUT_API_KEY}"
}
}
}
}Check it worked. Ask Cursor "list the FishOut tools you can use". If nothing appears, open the Output panel and choose MCP Logs from the dropdown — a bad header or a malformed file shows up there rather than in the chat.