Developers

Your coding assistant can build here too.

Its token can draft and test. Going live stays with you, unless you give it Publish.

Connect Claude Code.

Make an API token in your workspace settings, then run this. Claude Code, or another AI app, can then build here.

claude mcp add gorunner \
  --transport http \
  https://api.gorunner.io/mcp/build \
  --header "Authorization: Bearer grt_…"

The endpoint is https://api.gorunner.io/mcp/build · Use GoRunner from ChatGPT, Claude and Cursor

You choose what it may do.

A token gets only the permissions you give it. Without Publish and unpublish, it can draft and test but not go live.

With a token

New API token

Never more than you can do yourself. Tokens never manage people or settings.

It may

Read workflows (ticked)
Create and edit workflows (ticked)
Delete workflows (not ticked)
Publish and unpublish (not ticked)
Run and test workflows (ticked)
Read connections (ticked)
Create and edit connections (not ticked)
Delete connections (not ticked)
Read runs (ticked)
Cancel and delete runs (not ticked)

Create token

An example. The dialog starts on Draft and run, which is these five: the token from the recorded session below.

Or by OAuth, from your client’s own settings

What it may do

Read onlySee workflows, runs and connections.
Draft and runAlso write drafts and start runs, in test or live. (chosen)
Draft, run and publishAlso publish, so changes go live.

An example. The screen starts on Draft and run where you may write, and never on publish, whatever the client asked for. Only Draft, run and publish can publish.

Presets are a ceiling: a grant never goes beyond your own role in the workspace. Run and test workflows also starts runs of workflows that are already live; it can’t change what they run.

Thirteen things it can do.

Each one calls GoRunner’s own API with the assistant’s token, so the token’s permissions apply.

gorunner_search_piecesFind apps for a jobany token
gorunner_get_piece_schemaRead an app’s settingsany token
gorunner_list_workflowsList workflowsneeds Read workflows
gorunner_get_workflowRead a workflowneeds Read workflows
gorunner_list_connectionsList connectionsneeds Read connections
gorunner_validate_workflowCheck a workflow before saving itneeds Read workflows
gorunner_upgrade_code_stepConvert a Code step to 2.0.0, without savingneeds Read workflows
gorunner_create_workflowCreate a draftneeds Create and edit workflows
gorunner_update_workflowChange a draftneeds Create and edit workflows
gorunner_run_workflowStart a run, in test or of the live versionneeds Run and test workflows
gorunner_get_runRead a run, step by stepneeds Read runs
gorunner_list_runsList runsneeds Read runs
gorunner_publish_workflowPublish a workflowneeds Publish and unpublish

13 tools at /mcp/build, commit 7b9974dd · up to 64 API calls per request and 96 KB per result · MCP docs

Your workflows, as its tools.

Publish a workflow that starts with the MCP Tool trigger, and your assistant can call it by name at /mcp/tools. Up to 40 tools; each call waits up to 25 s for the answer.

A recorded session.

Claude Code built and tested an order approval. Its publish call was refused: its token had no Publish and unpublish.

Evidence · Order approval · recorded

When an order arrives at a webhook, look up the customer at http://customers:8080/customers/{customerId}. If the total is over 500, ask finance@example.com to approve and wait. Then reply to the caller with the result. Build it, then test it with an order of 740 for customer c_881.

search_pieces query="catch webhook and respond"Webhook, Delay / Wait

search_pieces query="HTTP REST API request"HTTP Request, Approval, Webhook (+3 more)

search_pieces query="wait for approval by email"Delay / Wait, Email (SMTP), Approval (+4 more)

list_connections 1 connection: Outgoing mail (SMTP) (email)

get_piece_schema pieceId="webhook" triggerId="catch_webhook"webhook · Catch Webhook

get_piece_schema pieceId="http" actionId="send_request" narrow={…}http · Send HTTP request

get_piece_schema pieceId="email" actionId="send_and_wait"email · Send for Approval (wait for decision)

get_piece_schema pieceId="webhook" actionId="return_response"webhook · Return Response

validate_workflow definition={…}valid

create_workflow input="(cut off: not valid JSON)" (failed)InputValidationError: mcp__gorunner__gorunner_create_workflow was called with input that could not be parsed as JSON.

create_workflow name="Order approval on webhook" description="Receives an order via webhook, looks up the customer, requires finance approval when the total exceeds 500, and replies to the caller with the outcome." definition={…}created 865c7171 (draft)

publish_workflow workflowId="865c7171" (failed)FORBIDDEN: you don't have permission to perform this action — it requires the workflow:publish scope

run_workflow workflowId="865c7171" environment="test" idempotencyKey="test-c881-740-01" triggerData={…} waitSeconds=25run 292cfb04: paused — lookup_customer completed, check_total completed, request_approval paused

The approver approved it. Check the run.

get_run runId="292cfb04"run 292cfb04: completed — lookup_customer completed, check_total completed, request_approval completed, respond_result completed

Draft · never published

Order receivedWebhook
Look up customerHTTP Request · 5 msWorked
Total over 500?Branch · 0 msWorked
Under limit
Reply: no approval neededWebhook
Ask finance to approveEmail (SMTP) · 36 sWorked
The approver’s pageApproval needed: order over $500
Order for customer c_881 totals 740, which exceeds the 500 approval threshold. Please approve or reject.
ApproveThe approver pressed Approve. The run went on.
Reply to caller with decisionWebhook · 0 msWorked
Drafttest run · completed

Recorded: 22 Sep 2026 · Claude Code 2.1.215 · claude-opus-4-8[1m]
Against: local GoRunner test instance, commit 5fbf8f54
Its token could: Read workflows · Create and edit workflows · Run and test workflows · Read runs · Read connections. Not Publish and unpublish.
Shown: Tool calls and results as recorded; the assistant’s prose left out; waits shortened.

How a run flows.

The API records each run in Postgres, and Redis wakes a worker. The worker runs every step; a run that waits on a person is saved in Postgres until the answer.

Drawn from the source at commit 5fbf8f54, rechecked at v2026.10.7. The API runs no workflows itself. A worker that stops mid-run has its run picked up again.

The rest of the API.

REST APIOpenAPI 3.1: 159 operations across 130 paths, and a test that checks the spec against the router. No /v1 outside the embed API: changes are additive only. Retry a run request safely with an Idempotency-Key.
Tokens and permissionsgrt_ tokens, stored hashed, with an optional expiry and any of the ten permissions above. You can only grant permissions you hold; workspace admins make tokens.
Webhooks/api/webhooks/{token}, any method, with a token you can rotate. The caller waits up to 30 s for the workflow’s own reply, or adds ?async=true for a 202 at once. Sign-in by basic auth, a header or an HMAC signature.
Export and importExport any workflow as a .json file. Import one from n8n, Activepieces or GoRunner, up to 5 MB: every node is accounted for in a report before a workflow is created.

API reference MCP docs