Cursor OmniForce omniforce_list_reports
How to: Cursor OmniForce omniforce_list_reports
Add OmniForce to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"omniforce-mcp": {
"url": "https://mcp-oss.omniforce.run/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something omniforce_list_reports does. Cursor lists the server's tools on connect and calls omniforce_list_reports itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that OmniForce'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
OmniForce will not start until these are set, so omniforce_list_reports never becomes available.
-
OMNIFORCE_API_KEY -
OMNIFORCE_API_BASE_URL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 12 October 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.