You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the scenario modeler example through the built dscode CLI so the MCP App demo works from one terminal, and shut down managed MCP processes cleanly.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
`npm start` launches the current repo build of dscode from this example directory. dscode then starts the `scenario-modeler` MCP server through the existing stdio MCP config, so you only need one terminal.
20
15
21
16
Then ask the agent: "Show me the current SaaS scenario projections."
22
17
23
-
That phrasing is more natural, but still points the agent toward the `get-scenario-data` MCP tool because it asks for live scenario output rather than code analysis or setup help.
18
+
If the agent replies with plain text only, ask it to use the `get-scenario-data` MCP tool explicitly.
24
19
25
20
Agent calls `get-scenario-data` → dscode renders the MCP App → TUI highlights the localhost link → open it in your browser.
26
21
22
+
## Alternate startup modes
23
+
24
+
```bash
25
+
npm run start:server # start only the HTTP MCP server on localhost:3100
26
+
npm run start:stdio # start only the stdio MCP server
27
+
```
28
+
27
29
## How it works
28
30
29
31
-**server.ts** — Standard MCP server using `@modelcontextprotocol/sdk`. Registers:
0 commit comments