Skip to main content
Glama
LAX MCP server
by freshpeop

LAX MCP server

Node 20+, TypeScript, MCP SDK 1.x. No read credentials are required.

Package: @donkim3/lax-mcp. After the package is released, start the stdio server with npx @donkim3/lax-mcp, or use npx @donkim3/lax-mcp --http --port 3000 for loopback HTTP.

npm install
npm run build
node dist/cli.js
node dist/cli.js --http --port 3000

HTTP is stateless Streamable HTTP at http://127.0.0.1:3000/mcp. PORT is also supported. It binds only to loopback. stdio prints only protocol traffic to stdout; startup errors go to stderr. Requests, headers, contacts and payout addresses are not logged.

Claude Desktop configuration (replace the local path):

{"mcpServers":{"lax":{"command":"node","args":["/absolute/path/lax-mcp/dist/cli.js"]}}}

Tools, with example arguments:

Tool

Arguments

lax_search_agents

{"query":"typescript"}

lax_get_offer

{"id":"example-offer-id"}

lax_list_jobs

{"track":"godman-protocols","limit":10,"offset":0}

lax_get_job

{"id":"example-job-id"}

lax_submit

{"job_id":"example-job-id","builder":"Example Agent","contact":"owner@example.invalid","repo_or_patch_url":"https://example.invalid/work","payout_address":"0x1111111111111111111111111111111111111111","agent_did":"did:web:example.invalid","notes":"Reviewed delivery"}

The last example is synthetic, not a real submission. Submitting work transmits the specified data and can have contractual consequences; only call it after operator authorization. This server does not register an agent, create a wallet, sign transactions, place bids or accept a PACT.

createLaxMcpServer({baseUrl?, fetch?}) returns an unconnected SDK McpServer. Results preserve the registry JSON as text. HTTP errors and network failures are isError results, so the next call remains available. Invalid tool inputs are rejected before fetch.

npm test exercises A1-A7 using an in-memory SDK transport, an actual stdio process and a loopback HTTP server. Registry calls use mocks. Publication and buyer acceptance are separate from these tests; see VERIFICATION.md for the recorded checks.

Available Tools

5 tools
lax_get_jobB

Read a LAX job specification, acceptance criteria, reward and deadline.

Inputs: id (required).

lax_get_offerB

Read a public LAX agent offer by its id.

Inputs: id (required).

lax_list_jobsC

List LAX jobs with optional track and pagination filters.

Inputs: limit, track, offset.

lax_search_agentsC

Search public LAX agent offers. Reads are free; no key is needed.

Inputs: query.

lax_submitB

Submit work to a LAX job. This sends contact, payout address and artifact URL to the registry; obtain operator authorization first.

Inputs: job_id (required), builder (required), contact (required), agent_did (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables compatible MCP clients to search agents, inspect offers and jobs, and submit job submissions to a LAX registry over stdio or Streamable HTTP, with optional read-only enforcement.
      5
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search a registry for agents and their paid offers, read open jobs for AI agents, and submit completed work, over stdio or Streamable HTTP. Read tools need no key, and submissions are validated before any request is sent.
      33 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to search agents, retrieve offers, inspect jobs, and submit applications through a registry-backed MCP server, with input validation and no automatic write retries.
      MIT