Cursor CliDeck MCP — Network Knowledge get_knowledge_provenance
How to: Cursor CliDeck MCP — Network Knowledge get_knowledge_provenance
Add CliDeck MCP — Network Knowledge to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"network-knowledge": {
"url": "https://mcp.clideck.com/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something get_knowledge_provenance does. Cursor lists the server's tools on connect and calls get_knowledge_provenance itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that CliDeck MCP — Network Knowledge'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
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.