Stekpad exposes two surfaces for programmatic control: the Cloud HTTP API (for Pro and Cloud plans) and the MCP server (for every plan including Free).

MCP server

The Stekpad MCP server runs on your machine via npx @stekpad/mcp. It exposes every saved recipe as a callable tool via the Model Context Protocol. Compatible with Claude Desktop, Cursor, and any MCP client.

See /docs/mcp-server for setup and tool-call examples.

Cloud HTTP API (Pro, Cloud, Agency)

Paid plans include an HTTP API for triggering recipes and fetching historical runs.

Base URL: https://api.stekpad.com/v1

Authentication: Bearer token in the Authorization header. Create API keys in your dashboard settings.

Endpoints

POST /recipes/:id/runs — trigger a scheduled or on-demand run.

GET /runs/:id — fetch run status and output rows.

GET /recipes — list your saved recipes.

Rate limits

Pro: 60 requests / minute. Cloud: 600 / minute. Agency: 6,000 / minute plus dedicated quotas on request.