Schema | Synthetic Orders MCP Server

Synthetic Orders MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MAX_BATCH`	No	Hard cap on count. Must be ≥ 1.	100
`ORDER_API_URL`	No	Where batches are POSTed.	http://127.0.0.1:8000
`REQUEST_TIMEOUT_S`	No	Per-request HTTP timeout.	10

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
check_targetA	Report whether the configured order API is reachable, and what it holds.
preview_orderA	Generate one order and return it without sending it. `seeded` samples the catalog and should be accepted; `simple` invents every field and should be rejected. Pass `seed` to reproduce an exact payload.
send_ordersA	Generate `count` orders and POST each one to the configured order API. Use `seeded` for traffic that should be accepted and `simple` to drill the API's rejection path. The result reports the seed, so the same batch can be replayed by passing it back in.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`catalog`	The sellable catalog rows the seeded generator draws from.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mitchallen/mcp-synthetic-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server