The runstamp-mcp binary included in @runstamp/sdk gives an MCP-compatible
agent six bounded tools in two
progressive paths:
| Tool | Job |
|---|---|
runstamp_list_operations | Find operations by job, domain, verb, or availability. |
runstamp_describe_operation | Read an operation's schemas, errors, losses and binding requirements. |
runstamp_invoke_operation | Run a described operation through its public-GA local binding. |
runstamp_list_jobs | List the bundled local-preview Document Job definitions. |
runstamp_describe_job | Read one Job's inputs, outputs, steps, evidence, and limitations. |
runstamp_run_job | Run a described Job locally and return its readiness evidence. |
The operation path finds all stable operations without loading every top-level tool. The Job path exposes three bundled first-party definitions and reports local-preview limitations in every discovery response.
Configure your client
The server runs locally over stdio through npx. No global install is needed.
Use this configuration in Claude Desktop, Cursor, Gemini CLI, Windsurf, or Cline:
{
"mcpServers": {
"runstamp": {
"command": "npx",
"args": ["-y", "-p", "@runstamp/sdk@3.1.0", "runstamp-mcp"]
}
}
}| Client | Configuration file |
|---|---|
| Claude Desktop | claude_desktop_config.json |
| Cursor | .cursor/mcp.json |
| Gemini CLI | settings.json |
| Windsurf | MCP configuration file |
| Cline | MCP settings |
VS Code uses servers instead of mcpServers:
{
"servers": {
"runstamp": {
"command": "npx",
"args": ["-y", "-p", "@runstamp/sdk@3.1.0", "runstamp-mcp"]
}
}
}Agent workflow
- Call
runstamp_list_operationswith the smallest useful filter. - Call
runstamp_describe_operationbefore building input. - Confirm MCP availability is
public_ga, then invoke the operation. - Inspect the result envelope and loss ledger before using the artifact.
For a reusable Job, call runstamp_list_jobs, then runstamp_describe_job,
then runstamp_run_job. A successful local run can still report unchecked
or failed readiness if native-app, conversion-loss or customer-review
requirements are unresolved.
Security boundary
The MCP server is local-only. It needs no account, authentication, API key
or RUNSTAMP_API_KEY, and it does not silently send input to the Managed API.
Hosted execution is a separate surface for free-trial workspaces and active Platform and Enterprise
workspaces. Keep its environment-bound pj_live_ key out of MCP configuration;
see the Managed API quick start.