labs-catalog-mcp
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., "@labs-catalog-mcp list labs in collection 3"
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.
labs-catalog-mcp
A real MCP server, with a real captured session. LB-07 in the AI Labs portfolio's Live Builds collection: the portfolio's MCP Server Contract Workbench (GAP-01) simulates the wire protocol to teach it — this repo is the live counterpart a real client can connect to.
The server exposes the portfolio's own labs registry as tools:
tool | what it does |
| list labs, filter by collection (0–5) or badge (LIVE/SIMULATED) |
| one lab's problem, decision, status, route |
| find the lab for the enterprise decision you're facing |
Run it
npm install
npm start # stdio MCP server
npm run capture # real client session -> session-transcript.jsonl + console outputRelated MCP server: Lab Registry Server
Connect Claude Desktop
{
"mcpServers": {
"labs-catalog": { "command": "node", "args": ["/absolute/path/to/server.mjs"] }
}
}The captured session
session-transcript.jsonl / session.md hold an actual recorded session — initialize handshake, tools/list,
and three tool calls, both directions, timestamped. Recorded by tee-wire.mjs, a 30-line wire tap between
client and server; re-run npm run capture and it regenerates. No frame in this repo is hand-written.
Honesty & attribution
Built on @modelcontextprotocol/sdk (MIT) and zod.
Catalog data is a generated snapshot of the portfolio's packages/kit/src/registry.ts. Server, wire tap, and
capture harness are original. MIT licensed.
Available Tools
3 toolsget_labB
Full detail for one lab: the problem it addresses, the decision it enables, status, and route.
Inputs: id (required).
list_labsA
List the portfolio's labs, optionally filtered by collection (0-5) or live mode (LIVE/SIMULATED).
Inputs: live, collection.
search_decisionsA
Search the catalog by the enterprise decision you are facing (matches problem/decision/title text).
Inputs: query (required).
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 targets a distinct operation: retrieving full details of a single lab, listing labs with filters, and searching by decision text. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (get_lab, list_labs, search_decisions), making the set predictable and easy to navigate.
Three tools is an appropriate size for a focused catalog service, covering the primary use cases of detail retrieval, listing, and search without unnecessary bloat.
The tools provide full coverage for a read-only catalog: listing with filters, full detail retrieval, and full-text search. No obvious gaps exist for the stated purpose.
Maintenance
Related MCP Connectors
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Read-only AI/LLM cost tools with current MCP discovery and attributable Registry transport.
AgencyAI's public MCP for service discovery and AI-readiness assessment.
AI agent registry — search, discover, register, and connect agents via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceExposes SAP AI Core APIs as MCP tools, enabling AI assistants to manage AI Core lifecycle and administration through natural language.7MIT
- FlicenseAqualityBmaintenanceEnables MCP clients to discover and fetch skills, agents, commands, and hooks from the Gen-e2 Lab Registry, and check local inventory compliance against the registry.15-
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to local AI work center metadata including status, providers, usage, projects, and tasks via MCP.1-
- FlicenseNot gradedqualityCmaintenanceProvides a single remote MCP endpoint that gives AI clients policy-checked business tools, shared cross-client memory, durable jobs, and consolidated reporting across connected projects and operations.-