Integration

Robocorp Control Room integration

Robocorp Control Room (now part of Sema4.ai) runs Python and Robot Framework automations. List and inspect processes, start, stop and follow process runs and their step runs, console messages and artifacts, manage work items and their queues, task packages, assistants, asset storage, vault secrets, workers, worker groups and process webhooks. Left out: the start route that takes the API key in the query string, and minting worker link tokens (the token is a credential). Authentication is a Control Room workspace API key sent as Authorization: RC-WSKEY <key>; each route needs the matching permission on the key, and the connection also holds the workspace id and the Control Room subdomain.

Connect Robocorp Control Room How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Robocorp Control Room.Built from the 62 Robocorp Control Room tools below, on the connection you add once.

What you can do with Robocorp Control Room

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Worker, 6 operations

add_worker_to_groupAdd worker to groupPOSTAdds an existing worker to a worker group, so processes targeting the group can run on it.
delete_workerDelete workerDELETEPermanently deletes (unlinks) a worker from the workspace. Irreversible.
get_workerGet workerGETReturns one worker: id, name and state.
list_workersList workersGETLists the workers (machines that run automations) of the workspace: id, name and state. One page: raise limit for more; has_more says if more exist (later pages are not reachable).
remove_worker_from_groupRemove worker from groupDELETERemoves a worker from a worker group; the worker itself is kept.
update_workerUpdate workerPOSTRenames a worker.

Link token, 5 operations

create_worker_group_link_tokenCreate worker group link tokenPOSTCreates a link token that lets new workers join the worker group until it expires. The token value is shown in Control Room only, not returned here.
delete_worker_group_link_tokenDelete worker group link tokenDELETEPermanently deletes a worker group link token; it can no longer link workers. Irreversible.
get_worker_group_link_tokenGet worker group link tokenGETReturns one link token of a worker group: id, name and expiry (the token value is shown in Control Room only).
list_worker_group_link_tokensList worker group link tokensGETLists the link tokens of a worker group: id, name and expiry. The token values themselves are shown in Control Room only. One page: raise limit for more; has_more says if more exist (later pages are not reachable).
update_worker_group_link_tokenUpdate worker group link tokenPOSTChanges a link token's name and expiry. Both are required: read the current values with get_worker_group_link_token and send back the one you keep.

Task package, 5 operations

create_task_packageCreate task packagePOSTCreates a task package: type zip (code uploaded later), public_git (configuration.repository) or github/gitlab (configuration with mode attached or detached).
delete_task_packageDelete task packageDELETEPermanently deletes a task package. Processes whose steps use it can no longer run them. Irreversible.
get_task_packageGet task packageGETReturns a task package: name, type, the tasks it contains, a download url and its git configuration when it is git-based.
list_task_packagesList task packagesGETLists the task packages (the uploaded or git-linked automation code) of the workspace: id, name, type, creation time. One page: raise limit for more; has_more says if more exist (later pages are not reachable).
update_task_packageUpdate task packagePOSTChanges the git configuration of a github or gitlab task package (attached to a branch, or detached on a reference). The package type cannot be changed.

Worker group, 5 operations

create_worker_groupCreate worker groupPOSTCreates a worker group with the given name.
delete_worker_groupDelete worker groupDELETEPermanently deletes a worker group. Irreversible.
get_worker_groupGet worker groupGETReturns one worker group (id and name).
list_worker_groupsList worker groupsGETLists the worker groups of the workspace (id and name). One page: raise limit for more; has_more says if more exist (later pages are not reachable).
update_worker_groupUpdate worker groupPOSTRenames a worker group.

Asset, 4 operations

create_assetCreate assetPOSTCreates an empty asset with the given name in asset storage. It holds no data until create_asset_upload adds its content.
delete_assetDelete assetDELETEPermanently deletes an asset and its payload from asset storage. Irreversible.
get_assetGet assetGETReturns an asset with its payload: type (empty, data or url), content_type, and either the data inline or a url to download it.
list_assetsList assetsGETLists the asset storage assets of the workspace (id and name of each). One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Process run, 4 operations

delete_process_runDelete process runDELETEPermanently deletes a process run and its history. Irreversible.
get_process_runGet process runGETReturns one process run: state (new, in_progress, completed, unresolved, stopping), creation, start and end times, duration, process and how it was started.
list_process_runsList process runsGETLists process runs of the workspace, optionally only one process (process_id) or one state: state, timing, duration, process and how it was started. One page: raise limit for more; has_more says if more exist (later pages are not reachable).
start_process_runStart process runPOSTStarts a run of the process, which executes its automation for real. Omit type to start with the default work item (or an empty one); with_work_item_ids, with_inputs and with_payloads choose the input instead.

Secret, 4 operations

create_secretCreate secretPOSTCreates a vault secret holding the given key/value items, readable by the workspace's automations.
delete_secretDelete secretDELETEPermanently deletes a vault secret. Automations that read it will fail. Irreversible.
list_secretsList secretsGETLists the vault secrets of the workspace by name and description. Secret values are never returned. One page: raise limit for more; has_more says if more exist (later pages are not reachable).
update_secretUpdate secretPOSTOverwrites a vault secret: the items sent replace ALL existing items of the secret, and the description is required too.

Webhook, 4 operations

create_webhookCreate webhookPOSTCreates a webhook that POSTs process run events (started, completed, unresolved) of one process to your endpoint. The signing secret is not passed through, so deliveries cannot be verified from what this tool returns.
delete_webhookDelete webhookDELETEPermanently deletes a process webhook; its endpoint stops receiving events. Irreversible.
get_webhookGet webhookGETReturns one process webhook: the process, the events sent and the endpoint url. The signing secret is not returned.
list_webhooksList webhooksGETLists the process webhooks of the workspace: the process, the events sent and the endpoint url. The signing secret is not returned. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Assistant, 3 operations

create_assistantCreate assistantPOSTCreates an assistant (an attended automation started by a person from Control Room) that runs the named task of a task package.
get_assistantGet assistantGETReturns one assistant: name, creation time and the task package and task it runs.
list_assistantsList assistantsGETLists the assistants of the workspace with the task package and task each one runs. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Process, 3 operations

create_processCreate processPOSTCreates a process: up to 10 steps, each running a task of a task package on a worker, plus optional schedules, an email trigger and notifications. A schedule or trigger makes it start runs on its own.
get_processGet processGETReturns one process: name, description, creation time and its steps with the worker each one runs on.
list_processesList processesGETLists the processes of the workspace (id, name, creation time). Use the id with start_process_run or get_process. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Work item, 3 operations

create_work_itemCreate work itemPOSTAdds a work item with the given payload to the input queue of a process. A process scheduled to start with input items may then run on it.
get_work_itemGet work itemGETReturns a work item: state, process, run, step, exception details, payload and files (each with a download url valid for one hour).
list_work_itemsList work itemsGETLists work items, optionally filtered by process, process run or state: state, process, run, step and exception details. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Artifact, 2 operations

get_step_run_artifactGet step run artifactGETReturns one step run artifact with its name, size and a url to download the file.
list_step_run_artifactsList step run artifactsGETLists the artifacts (log and output files) a step run produced, with name and size. Use get_step_run_artifact for a download url. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Assistant run, 2 operations

get_assistant_runGet assistant runGETReturns one assistant run: state, error code if it failed, start and end times, duration and the assistant it belongs to.
list_assistant_runsList assistant runsGETLists assistant runs in the workspace, or only those of one assistant when assistant_id is given: state, error code, start and end times, duration. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Step run, 2 operations

get_step_runGet step runGETReturns one step run of a process run: state, error code if it failed, timing, duration and its step.
list_step_runsList step runsGETLists the step runs of a process run: state, error code, timing, duration and the step each one executed. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Upload, 2 operations

create_asset_uploadCreate asset uploadPOSTSets the content of an asset. Under 5 MB pass the content in data and it is stored at once; for larger content omit data and upload the bytes to the returned upload_url. Replaces the asset's current payload.
get_asset_uploadGet asset uploadGETReturns the state of an asset upload created by create_asset_upload: status (pending, completed or failed), content_type, and reason when it failed.

Batch, 1 operation

batch_update_work_itemsBatch update work itemsPOSTRetries, deletes or marks as done the listed work items, all at once. delete and mark_as_done cannot be undone.

Console message, 1 operation

list_step_run_console_messagesList step run console messagesGETLists the console output messages of a step run with their timestamps, useful to see why a run failed. One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Event, 1 operation

list_step_run_eventsList step run eventsGETLists the events of a step run (event type and timestamp). One page: raise limit for more; has_more says if more exist (later pages are not reachable).

File, 1 operation

create_work_item_fileCreate work item filePOSTRegisters a file on a work item and returns an upload url and the form fields to send with it; the bytes are then uploaded to that url, outside this tool.

Output, 1 operation

list_process_run_outputsList process run outputsGETLists the output work items of a process run (their payload and files, each file with a download url valid for one hour). One page: raise limit for more; has_more says if more exist (later pages are not reachable).

Payload, 1 operation

update_work_item_payloadUpdate work item payloadPOSTReplaces the payload of a work item with the one sent.

Stop, 1 operation

stop_process_runStop process runPOSTStops a running process run. Both flags are required: whether to mark the remaining work items as done, and whether to terminate step runs still executing.

Workspace, 1 operation

get_workspaceGet workspaceGETReturns the workspace the connection is bound to: its id, name, organization (id and name) and Control Room url.

Use Robocorp Control Room from Claude Code, Cursor or Codex

Connect Robocorp Control Room in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Robocorp Control Room operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Robocorp Control Room

Create your workspace
Sign up free. Nothing to install.
Connect Robocorp Control Room once
Add your Robocorp Control Room connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.