Add Salient to Cursor¶

Connect Salient's MCP server to Cursor IDE for tabletop exercise management alongside your code.

Configuration¶

Cursor supports MCP servers via JSON config at two levels:

Scope	File
Project	`.cursor/mcp.json` in your project root
Global	`~/.cursor/mcp.json` in your home directory

Project Config¶

Create .cursor/mcp.json:

{
  "mcpServers": {
    "salient": {
      "command": "python3",
      "args": ["/path/to/salient/tools/mcp-ttx/server.py"],
      "env": {
        "SALIENT_API_URL": "http://localhost:8000",
        "SALIENT_TOKEN": "your-jwt-token"
      }
    }
  }
}

Global Config¶

Create ~/.cursor/mcp.json with the same format to make Salient available across all projects.

Restart Required¶

Restart after config changes

Cursor does not hot-reload MCP configuration. After editing mcp.json, restart Cursor or use Cmd/Ctrl+Shift+P > Reload Window for changes to take effect.

Tool Limit¶

Cursor has a 40-tool limit per MCP server

Salient exposes 44 tools. Cursor will load the first 40 and ignore the rest. If you hit this limit, prioritize by commenting out less-used tools in the server or by configuring tool filtering.

Recommended priority tools (core workflow):

list_scenarios, get_scenario, create_scenario
save_session, save_evaluation
query_twin, twin_facts, twin_facts_summary
posture_assessment, posture_report
list_connectors, okta_sync, entra_id_sync
generate_playbook, get_playbook
get_dashboard, get_org_profile

Lower priority (can be dropped if needed):

posture_timeline, detect_patterns, discover_connector
twin_coverage, event_bridge

Verify Connection¶

Open Cursor's MCP panel (Cmd/Ctrl+Shift+P > MCP: List Servers) to confirm Salient is connected and tools are loaded.

Using Salient in Cursor¶

In Cursor's Agent mode, you can directly reference Salient tools:

"Use Salient to list my tabletop scenarios" "Query the Salient twin for our incident response gaps"

Tools Reference · MCP Overview