Webmcp

Generated MCP contract

node mcp/lib/index.js

Fifty-five typed tools from one execution contract

The generated executable is not a list in a document. The official MCP SDK accepts the whole surface, including write annotations, OAuth scopes, idempotency headers and typed outputs.

Discovery ran against the local generated executable with a non-production placeholder credential; no tool call reached DoneOS production.

  1. 01

    The generated surface is executable

    Connected with the official MCP SDK and called `tools/list` on the generated DoneOS stdio server.

    The generated stdio server completed MCP discovery with 55 valid tools: 36 write actions and 19 reads.

    node mcp/lib/index.js
    $ node mcp/lib/index.js
    Terminal showing the generated DoneOS MCP server returning 55 valid tools
  2. 02

    The contract carries execution semantics

    Inspected the generated `create_work_item` tool returned by discovery.

    The inspected work command carries the parts that usually disappear in naive code generation: a retry key, a narrow scope and a structured result.

    node mcp/lib/index.js
    $ node mcp/lib/index.js
    Terminal showing DoneOS work creation semantics including idempotency and typed output

What this feature does

  • 55 SDK-validated tools
  • 36 explicit writes
  • Idempotency and output semantics preserved

Worth knowing

  • This is the broad generated adapter, not the separately reviewed hosted production surface.