Developer Tools
scenariosplice.com
Assists with authoring and validating ScenarioSplice scenario JSON, and discovering published training scenarios.
ENDPOINT 1
https://scenariosplice.com/mcp
MCP server metadata
- Name
- ScenarioSplice
- Version
- 1.0.0
ScenarioSplice lets people build branching training scenarios in the browser. Use get_spec to learn the scenario JSON format, draft a scenario for the user, check it with validate_story, then give the user the JSON and tell them to import it at https://scenariosplice.com/#library.
Known tools 3
get_specGet the ScenarioSplice scenario JSON format: schema, authoring rules, a complete example, and import instructions.
Inferred read-onlyvalidate_storyValidate a drafted scenario JSON object against the ScenarioSplice format: broken links, orphan nodes, missing endings.
Inferred read-onlylist_publishedList recently published training scenarios on ScenarioSplice with playable links.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.scenariosplice]
url = "https://scenariosplice.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"scenariosplice": {
"type": "http",
"url": "https://scenariosplice.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: scenariosplice
Remote MCP URL: https://scenariosplice.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"scenariosplice": {
"url": "https://scenariosplice.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"scenariosplice": {
"type": "http",
"url": "https://scenariosplice.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "scenariosplice",
"transport": "streamable-http",
"url": "https://scenariosplice.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.