test-task-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@test-task-server run a smoke-login test against staging-web and tell me if it passes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-test-task-server-ts
A small MCP server (stdio transport) for test-task scheduling, written in TypeScript.
Portfolio demo, not production. This is a small public project built to demonstrate MCP server development in TypeScript. It does not connect to any real test system, and it does not represent production TypeScript experience. Tasks live in memory only and are "executed" by a fake worker with deterministic, simulated outcomes.
What it does
Three tools, mirroring a simple test-task scheduling design:
Tool | Description |
| Queue a test task (task name + target + optional params). Returns a task id. |
| Poll a task by id for its status and result summary. |
| List all submitted tasks with their statuses. |
Task lifecycle: queued → running → passed / failed, driven by a fake
worker after short simulated delays. Outcomes are deterministic:
params.expectedOutcome("passed"|"failed") forces an outcome — handy for demos;otherwise the outcome is derived from a hash of the task name (~80% pass).
Related MCP server: Task Tracker MCP
What it demonstrates
MCP server development in TypeScript with
@modelcontextprotocol/sdk(stdio transport, zod-validated tool schemas)A small, testable design: pure tool handlers over an in-memory store, unit-tested with Vitest
Strict TypeScript (
strict: true)
Run it locally
Requires Node.js 20+.
npm ci
npm run build
npm startThe server speaks MCP over stdio, so it needs an MCP client to talk to. To try it interactively, the MCP Inspector works (optional):
npx @modelcontextprotocol/inspector node dist/index.jsExample tool calls (as an MCP client would send them):
// submit_test_task
{ "name": "smoke-login", "target": "staging-web" }
// submit_test_task — force a failure to see the failed path
{ "name": "checkout-flow", "target": "staging-web", "params": { "expectedOutcome": "failed" } }
// get_task_result
{ "taskId": "task-1" }
// list_test_tasks
{}Run the full verification suite (build, unit tests, and a real MCP SDK client talking to a separate server process over stdio):
npm testRun only the subprocess smoke test:
npm run test:smokeThe smoke test initializes an MCP session, discovers all three tools, submits synthetic passing and failing tasks, polls both to their terminal states, and checks listing, unknown task IDs, invalid inputs, and recovery after errors. Requests and polling have time limits, and the subprocess is closed even if an assertion fails. Unit lifecycle tests use a controlled clock to avoid depending on short wall-clock timing windows.
On 2026-11-15, npm ci, npm run build, npm test (12 tests), and
npm run test:smoke passed locally on Windows with Node.js 24.14.1. This validates
the SDK/stdio integration. Client configuration examples below are reference
snippets; this verification covers the SDK client rather than a Claude host.
Example client configuration
Config snippet only — connect it to a client yourself. Claude Code (.mcp.json):
{
"mcpServers": {
"test-task-server": {
"command": "node",
"args": ["/absolute/path/to/mcp-test-task-server-ts/dist/index.js"]
}
}
}Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"test-task-server": {
"command": "node",
"args": ["/absolute/path/to/mcp-test-task-server-ts/dist/index.js"]
}
}
}Replace /absolute/path/to/... with the real path on your machine, then restart
the client. On Windows, forward slashes are valid in the JSON path, for example
E:/projects/mcp-test-task-server-ts/dist/index.js. Run npm run build before
connecting. These are examples; the test commands do not change client settings.
Project layout
src/
index.ts MCP server wiring (stdio transport, tool registration)
tools.ts Tool handlers (pure functions over the store — unit tested)
store.ts In-memory task store + fake worker
store.test.ts Task lifecycle tests
tools.test.ts Tool handler tests
tests/
mcp.integration.test.ts MCP SDK client + subprocess smoke testLicense
MIT — see LICENSE.
Available Tools
3 toolsget_task_resultGet a task resultB
Return the status and result summary of a test task by id.
Inputs: taskId (required).
list_test_tasksList test tasksA
List all submitted test tasks with their current statuses.
Inputs: no named parameters.
submit_test_taskSubmit a test taskA
Queue a test task for execution. Returns a task id; poll get_task_result for the outcome. Optional params.expectedOutcome ('passed' | 'failed') forces a deterministic outcome, useful for demos.
Inputs: name (required), target (required), params.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: submit queues a task, get_task_result retrieves one task's outcome by id, and list_test_tasks enumerates all tasks. There is no meaningful overlap between submission, single-result polling, and listing.
All three tools follow a consistent verb_noun pattern (submit_test_task, get_task_result, list_test_tasks) with snake_case throughout. The naming is predictable and readable.
Three tools is on the thin side but matches the minimal async-task lifecycle the server advertises. Each tool earns its place with no filler.
The core submit/poll/list workflow is covered, which is sufficient for demo-grade test task tracking. However, there is no cancel or delete operation, leaving tasks with no lifecycle termination beyond completion.
Related MCP Connectors
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
MEOK MCP Test MCP — golden-file + schema-drift + tool-failure tests for any MCP server. Drop-in
Build, validate, and manage API simulations in WireMock Cloud from MCP-compatible AI agents.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceContract-driven service virtualization and synthetic test-data management server that enables simulating APIs from OpenAPI contracts through MCP tools.28 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceEnables managing tasks through a simple task tracker with REST API and MCP tools for listing, creating, updating, assigning, and deleting tasks.-
- AlicenseAqualityCmaintenanceEnables MCP clients to submit tasks to a local file-backed queue and later read or cancel them by ID, with results produced by a separately run worker.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables running YAML-defined test suites against MCP servers and agent workflows, with live or simulated execution, assertions, and regression reporting.72 npmMIT