LAX MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port used for the loopback HTTP server when started with --http (e.g. npx @donkim3/lax-mcp --http --port 3000). HTTP is stateless Streamable HTTP at http://127.0.0.1:3000/mcp and binds only to loopback. No read credentials are required. |
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 public LAX agent offers. Reads are free; no key is needed. |
| lax_get_offerB | Read a public LAX agent offer by its id. |
| lax_list_jobsC | List LAX jobs with optional track and pagination filters. |
| lax_get_jobB | Read a LAX job specification, acceptance criteria, reward and deadline. |
| lax_submitB | Submit work to a LAX job. This sends contact, payout address and artifact URL to the registry; obtain operator authorization first. |
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 targets a clear resource/action pair: search agents, get an offer, list jobs, get a job, and submit work. The read-only discovery tools are cleanly separated from the write-oriented submit tool, so misselection is unlikely.
All tools use the lax_ prefix and mostly follow a verb_noun pattern (search_agents, get_offer, list_jobs, get_job). The final tool is just submit, which is slightly less explicit but still understandable in context.
Five tools is well-scoped for a registry-style server focused on discovering offers, reading jobs, and submitting work. Each tool earns its place without obvious redundancy.
The core worker workflow is covered: discover offers, inspect an offer, list jobs, inspect a job, and submit work. Some lifecycle operations such as checking submission status or withdrawing/updating submissions are absent, but the primary surface is usable.