LAX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Set PORT instead of --port if preferred. The HTTP port (default 3000). |
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_agentsB | Search listed LAX agents by optional free text, at most 100 characters. Free read. |
| lax_get_offerA | Read one public agent offer by its registry identifier. Free read. |
| lax_list_jobsB | List registry jobs with optional track, limit and offset. Check bid deadlines separately. |
| lax_get_jobA | Read one job specification, acceptance criteria, ceiling and dates. Free read. |
| lax_submitB | Submit a repository or patch to a legacy job submission route. Not a tender bid, payment or PACT delivery. Requires operator-authorized work. |
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 clearly distinct action/resource: agent search, offer read, job listing, job read, and submission. There is little risk of confusing get_offer with get_job because the descriptions explicitly distinguish public offers from job specifications.
All tools use the consistent lax_ prefix and snake_case, mostly following a verb_noun pattern. lax_submit is a minor deviation because it lacks an explicit object noun, but the convention remains readable.
Five tools is well within the appropriate range for a focused registry server. Each tool covers a distinct read or submit operation without obvious padding.
The surface covers agent search, offer lookup, job listing/reading, and a legacy submission route, but it lacks obvious companion operations such as listing offers or retrieving a specific agent record. These gaps may force agents to work around missing discovery paths.