lzt-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LZT_DEV_MCP_LZT_FLOW_API_KEY | No | The X-API-Key for mutating lzt-flow routes (compile_flow, create_run, create_flow, import_flow) | |
| LZT_DEV_MCP_TESTNET_BASE_URL | No | Where the send_request(target='testnet') and get_testnet_status() connect to | |
| LZT_DEV_MCP_LZT_FLOW_BASE_URL | No | The REST API of lzt-flow for the Flow group | http://127.0.0.1:8000 |
| LZT_DEV_MCP_LZT_EVENTUS_BASE_URL | No | The REST API of lzt-eventus for the Events group | http://127.0.0.1:27543 |
| LZT_DEV_MCP_LZT_EVENTUS_ADMIN_API_KEY | No | The admin key for lzt-eventus routes: subscriptions, token accounts |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_methodsB | List pylzt API methods, optionally filtered by namespace/search. |
| get_method_schemaB | Get a method's declared request fields and response model name. |
| get_model_schemaB | Get a response model's JSON Schema by name. |
| send_requestC | Send a real pylzt request; defaults to testnet, prod requires a token. |
| describe_apiC | Search the method catalog by a free-text query. |
| list_flowsA | List lzt-flow flows for the current tenant. |
| get_flowB | Get a flow's full spec by id. |
| create_flowC | Create a new lzt-flow flow from a FlowSpec. |
| export_flowB | Export a flow as a versioned FlowSpec envelope. |
| import_flowC | Import a flow from an exported envelope (compile+dry-run gated). |
| compile_flowC | Compile a flow into an immutable FlowIR. |
| list_catalogA | List lzt-flow's node catalog (action/logic/trigger types). |
| list_dynamic_methodsC | List pylzt facade methods usable as dynamic flow nodes. |
| get_dynamic_methodC | Describe one dynamic facade method's params and return shape. |
| create_runB | Start a run of a compiled flow (idempotent on run_key). |
| list_runsB | List runs for the current tenant. |
| get_runC | Get a run's current status. |
| get_run_traceC | Get a run's per-node execution trace. |
| get_rate_limitsB | List pylzt's published per-RateClass request ceilings. |
| get_error_catalogA | List pylzt's typed error classes with their carried args. |
| get_testnet_statusA | Check whether the configured lzt-testnet instance is reachable. |
| list_subscriptionsA | List lzt-eventus subscriptions (admin-key gated). |
| create_subscriptionB | Create a new lzt-eventus subscription (webhook/websocket/sse/polling). |
| poll_pending_eventsC | Poll pending events for a polling-transport subscription. |
| confirm_readB | Confirm read progress for a polling-transport subscription up to a seq. |
| get_event_typesA | List lzt-eventus's subscribable event-type catalog. |
| register_token_accountC | Register a new lzt-eventus token account. |
| list_token_accountsA | List lzt-eventus token accounts (admin-key gated). |
| get_eventus_statusA | Check whether the configured lzt-eventus instance is reachable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Most tools cleanly target distinct resources (flows, runs, subscriptions, schemas), but a few pairs could confuse an agent: list_methods vs describe_api both surface API catalog information, and get_method_schema vs get_dynamic_method both describe method inputs/outputs. Overall, descriptions and naming help separate the main workflows.
All tools follow a consistent verb_noun pattern: list_*, get_*, create_*, import_*, export_*, send_*, poll_*, confirm_*, register_*. The naming is uniform across the pylzt, lzt-flow, and lzt-eventus subdomains, making the tool set predictable and easy to navigate.
At 29 tools, this is on the heavier side, but the server covers three distinct subsystems (pylzt, lzt-flow, lzt-eventus), each with a reasonable set of operations. The count feels justified for the stated purpose, though a few introspection helpers could potentially be consolidated.
The server provides strong lifecycle coverage: flows can be listed, created, imported, exported, compiled, and run; subscriptions can be created, listed, polled, and confirmed; API introspection covers methods, schemas, rate limits, and errors. Minor gaps like updating or deleting flows/subscriptions exist, but agents can likely work around them.