Add Salient to Cline¶
Connect Salient's MCP server to Cline, the autonomous coding agent for VS Code.
Configuration¶
Cline stores MCP config in a platform-specific location:
Add the Salient server:
{
"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"
}
}
}
}
Auto-Approve Tools¶
Cline normally asks for approval before each tool invocation. To auto-approve Salient tools, add an "alwaysAllow" list:
{
"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"
},
"alwaysAllow": [
"list_scenarios",
"get_scenario",
"query_twin",
"twin_facts",
"twin_facts_summary",
"get_dashboard",
"get_org_profile",
"posture_assessment",
"list_connectors"
]
}
}
}
Read-only tools are safe to auto-approve
The list above includes only read operations. Keep write operations like create_scenario, save_session, and save_evaluation behind manual approval for safety.
No Tool Limit¶
Unlike Cursor (which caps at 40 tools), Cline has no limit on the number of tools per MCP server. All 44 Salient tools are available without filtering.
MCP Marketplace¶
Cline includes an MCP Marketplace in the extension sidebar. Salient is not yet listed, but you can configure it manually using the JSON above.
Using Salient in Cline¶
Start a Cline session and reference Salient tools naturally:
"Use Salient to list my tabletop scenarios" "Query the Salient digital twin for our incident response maturity"
Cline will discover the available tools and prompt for approval (unless auto-approved).