5660de49de
Some checks failed
CI / test (map[image:macos-latest name:macos], 1, 4) (push) Has been cancelled
CI / test (map[image:macos-latest name:macos], 2, 4) (push) Has been cancelled
CI / test (map[image:macos-latest name:macos], 3, 4) (push) Has been cancelled
CI / test (map[image:macos-latest name:macos], 4, 4) (push) Has been cancelled
CI / test (map[image:windows-latest name:windows], 1, 4) (push) Has been cancelled
CI / test (map[image:windows-latest name:windows], 2, 4) (push) Has been cancelled
CI / test (map[image:windows-latest name:windows], 3, 4) (push) Has been cancelled
CI / test (map[image:windows-latest name:windows], 4, 4) (push) Has been cancelled
CI / merge-reports (push) Has been cancelled
- Added a new integration script to manage custom features related to smart context. - Implemented handlers for smart context operations (get, update, clear, stats) in ipc. - Created a SmartContextStore class to manage context snippets and summaries. - Developed hooks for React to interact with smart context (useSmartContext, useUpdateSmartContext, useClearSmartContext, useSmartContextStats). - Included backup and restore functionality in the integration script. - Validated integration by checking for custom modifications and file existence.
51 lines
1.2 KiB
Markdown
51 lines
1.2 KiB
Markdown
### Fake stdio MCP server
|
|
|
|
This directory contains a minimal stdio MCP server for local testing.
|
|
|
|
- **Tools**:
|
|
- **calculator_add**: adds two numbers. Inputs: `a` (number), `b` (number).
|
|
- **print_envs**: returns all environment variables visible to the server as pretty JSON.
|
|
|
|
### Requirements
|
|
|
|
- **Node 20+** (same as the repo engines)
|
|
- Uses the repo dependency `@modelcontextprotocol/sdk` and `zod`
|
|
|
|
### Launch
|
|
|
|
- **Via Node**:
|
|
|
|
```bash
|
|
node testing/fake-stdio-mcp-server.mjs
|
|
```
|
|
|
|
- **Via script** (adds a stable entrypoint path):
|
|
|
|
```bash
|
|
testing/run-fake-stdio-mcp-server.sh
|
|
```
|
|
|
|
### Passing environment variables
|
|
|
|
Environment variables provided when launching (either from your shell or by the app) will be visible to the `print_envs` tool.
|
|
|
|
```bash
|
|
export FOO=bar
|
|
export SECRET_TOKEN=example
|
|
testing/run-fake-stdio-mcp-server.sh
|
|
```
|
|
|
|
### Integrating with Dyad (stdio MCP)
|
|
|
|
When adding a stdio MCP server in the app, use:
|
|
|
|
- **Command**: `testing/run-fake-stdio-mcp-server.sh` (absolute path recommended)
|
|
- **Transport**: `stdio`
|
|
- **Args**: leave empty (not required)
|
|
- **Env**: optional key/values (e.g., `FOO=bar`)
|
|
|
|
Once connected, you should see the two tools listed:
|
|
|
|
- `calculator_add`
|
|
- `print_envs`
|