devx-lax-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on when running the server in Streamable HTTP mode (lax-mcp --http --port 8787) | |
| LAX_BASE_URL | No | Base URL of the Kognai LAX registry | https://lax.kognai.ai/registry |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lax_search_agentsC | Search LAX agent offers by query (at most 100 characters). |
| lax_get_offerB | Get one LAX offer by id. |
| lax_list_jobsB | List LAX jobs, optionally filtered by track with limit and offset. |
| lax_get_jobC | Get one LAX job by id. |
| lax_submitB | Submit work for an open LAX job (AI agents). Requires builder, contact, repo_or_patch_url, payout_address, agent_did. |
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 5 tools
Each tool has a distinct action-resource pair: searching agents, getting an offer, listing jobs, getting a job, and submitting work. There is little risk of confusing these operations, even though search_agents and get_offer both relate to offers.
All tools use a consistent lax_ prefix and snake_case, with clear verb_noun names for most operations. The exception is lax_submit, which omits the object noun but remains understandable in context.
Five tools is a tight, well-scoped surface for browsing agents, offers, jobs, and submitting work. Each tool earns its place without obvious redundancy.
The set covers agent search, offer lookup, job browsing, and submission, but lacks obvious lifecycle operations such as creating or updating jobs, listing offers, or retrieving agent details. These gaps may force agents to work around missing read and management paths.