`disable-model-invocation: true` does not merely make a skill prefer `/name` — the model cannot invoke it at all, and its description is absent from the skill listing. So "create a PR for #2163", which is how that work actually starts, could never reach `pr-flow`. The original rationale ("procedures with side effects we'd invoke by name anyway") conflates invoking a skill, which only loads instructions, with performing the procedure it describes. Flipped `pr-flow`, `pre-push-gate`, `board-ops` and `test-servers` to model-invocable. `user-invocable` is an independent axis, so this is purely additive — every `/name` still works. `issue-create`, `issue-triage` and `release` stay deliberate. `board-ops` is in the set because `pr-flow` and `issue-create` delegate their card steps to it: a pointer from a model-invocable skill to a manual-only one is a dead end for the model. Costs weighed: the listing share goes 1,199 → 2,256 of 4,000, and a spurious load costs ~250 characters where a missed one costs a wrong base branch or an unsigned commit. The rules stay resident in AGENTS.md either way — this improves the odds of getting the procedure too, it does not become the guarantee. Eval cases committed for all four, measured at RUNS=3: pre-push-gate, board-ops and test-servers 5/5; pr-flow 4/5, with "take it through to a pull request" at 100% and the Copilot-review case borderline. Three initial cases were replaced rather than tuned green: their answers are resident in AGENTS.md, so the model answering without the skill is correct behaviour, not a miss — the rule this file already records about what makes a valid trigger case. AGENTS.md's maintenance rule now says to default to `false` and explains why, so the advice this change walks back does not get re-applied. Signed-off-by: cliffhall <cliff@futurescale.com>
98 lines
3.9 KiB
Markdown
98 lines
3.9 KiB
Markdown
---
|
|
name: test-servers
|
|
description: Run a composable MCP test server by hand — pick the showcase config that reproduces a given feature or bug, build test-servers, and connect with the right protocol era. Covers the stale-build hazard.
|
|
disable-model-invocation: false
|
|
---
|
|
|
|
# Running a test server
|
|
|
|
`test-servers/` provides **composable MCP servers** so tests and manual checks
|
|
exercise a real server over a real transport instead of mocks. A server is
|
|
assembled from **presets** (fixture factories in
|
|
`test-servers/src/preset-registry.ts`) and configured declaratively with a JSON
|
|
file under `test-servers/configs/`.
|
|
|
|
The full catalogue of showcase configs — one per feature, each with what to click
|
|
and what the broken build did — is
|
|
[`docs/test-servers.md`](../../../docs/test-servers.md). This skill is how to
|
|
run one.
|
|
|
|
## Build first
|
|
|
|
The servers are spawned as real subprocesses, so the build output must exist:
|
|
|
|
```sh
|
|
cd clients/web && npm run test-servers:build # tsc -p test-servers → test-servers/build/
|
|
```
|
|
|
|
Scripts reach this through `scripts/ensure-test-servers.mjs`, which builds
|
|
**unconditionally** (once per process per repo root).
|
|
|
|
⚠️ **Unconditional emit is not a clean.** A **deleted** source file leaves its
|
|
stale `.js` behind, existence checks pass against it, and anything still
|
|
importing that module silently runs the old code — reported not as staleness but
|
|
as a product failure in whatever was being tested. So after deleting or renaming
|
|
a source file:
|
|
|
|
```sh
|
|
rm -rf test-servers/build
|
|
```
|
|
|
|
The `.tsbuildinfo` is pinned inside `build/` so that clean actually invalidates
|
|
the cache.
|
|
|
|
## Run one
|
|
|
|
Two processes: the test server, then the Inspector.
|
|
|
|
```sh
|
|
# 1. The server, from the repo root, with the config you picked:
|
|
node test-servers/build/server-composable.js --config test-servers/configs/<name>.json
|
|
```
|
|
|
|
```sh
|
|
# 2. The Inspector, in another terminal (needs a built launcher — `npm run build`):
|
|
node clients/launcher/build/index.js --web
|
|
```
|
|
|
|
Then add the server in the Inspector using the URL the first process announced.
|
|
|
|
Two mechanics that bite:
|
|
|
|
- **The server announces its URL on _stderr_**, not stdout (`console.error` in
|
|
`server-composable.ts`). Watching stdout alone looks like a server that never
|
|
started.
|
|
- **The bound port is not necessarily the config's.** `createTestServerHttp`
|
|
resolves through `findAvailablePort()`, which walks upward when the configured
|
|
port is taken — so read the announced URL rather than assuming.
|
|
|
|
## Pick the right protocol era
|
|
|
|
Each config in [`docs/test-servers.md`](../../../docs/test-servers.md) says
|
|
which era to connect with. The default is **legacy**; configs setting
|
|
`transport.modern` need **Protocol Era = Modern**. Connecting with the wrong era
|
|
usually looks like a missing capability rather than an error.
|
|
|
|
## Common starting points
|
|
|
|
| Want to see | Config |
|
|
| --- | --- |
|
|
| An MCP App in the Apps tab | `mcp-app-http.json` (legacy) |
|
|
| An App-rendered elicitation | `app-elicitation-http.json` (legacy) |
|
|
| `Mcp-*` headers + the modern error taxonomy | `modern-network-http.json` |
|
|
| A tool result's `structuredContent` section | `structured-output-http.json` (legacy) |
|
|
| RFC 6570 resource-template expansion | `rfc6570-templates-http.json` |
|
|
| OAuth token revocation on clear | `oauth-revocation-http.json` (legacy) |
|
|
| Cancelling a call mid-flight | `cancellation-modern-http.json` (modern) |
|
|
|
|
## Adding a config or preset
|
|
|
|
- Presets live in `test-servers/src/preset-registry.ts`; configs in
|
|
`test-servers/configs/*.json`.
|
|
- A new showcase config gets a row in `docs/test-servers.md` saying what to do
|
|
and what the broken build did — the "what it looked like broken" half is what
|
|
makes the fixture reproducible later.
|
|
- ⚠️ **An `outputSchema` override must ride a tool that returns structured
|
|
content.** A conforming client validates the result against the advertised
|
|
schema, so an override on a preset returning none makes every call fail with
|
|
"declares an output schema but returned no structured content".
|