Cursor nordic data Prompt/due_diligence
How to: Cursor nordic data due_diligence
Add nordic data to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"nordic-data": {
"url": "https://nordic-data-mcp-production.up.railway.app/mcp/auth"
}
}
}-
02
Save the file and restart Cursor.
-
03
due_diligence is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Cursor will not call it for you.
-
04
If it does not appear, check that nordic data is connected and that you are looking at its prompts rather than its tools.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
nordic data will not start until these are set, so it never reaches Cursor.
-
NORDIC_API_KEY -
NORDIC_DEFAULT_COUNTRY -
NORDIC_VERBOSE_ERRORS
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.