Cursor Perigee perigee_describe_view
How to: Cursor Perigee perigee_describe_view
Add Perigee to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"perigee": {
"url": "https://perigee-mcp.perigeeinfo.workers.dev/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something perigee_describe_view does. Cursor lists the server's tools on connect and calls perigee_describe_view itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Perigee's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Perigee will not start until these are set, so perigee_describe_view never becomes available.
-
PERIGEE_SITE -
PERIGEE_MCP_CACHE
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.