Public MCP

Give AI clients governed access to Oroko.

Oroko exposes a stateless HTTP MCP transport using the same developer keys as the REST API. Read tools expose process context; write tools require explicit confirmation and remain subject to Oroko RBAC, review rules and approved-process locking.

Connect

MCP server configuration

Use the public server URL and the same developer key you use for Oroko REST requests.

{
  "mcpServers": {
    "oroko": {
      "url": "https://oroko.space/server/oroko-api/mcp",
      "headers": {
        "X-Oroko-Key": "ork_YOUR_KEY"
      }
    }
  }
}

Writes require confirmation

Write tools require confirmed: true. Oroko still applies the connected user's existing permissions, revision checks, governance rules and lifecycle locks. MCP writes are audited with the developer key used for the action.

Skills

Guidance built into the MCP connection

Compatible clients can discover Oroko process guidance directly through MCP prompts and resources. Hosts that support installable skills can also use the same skill files locally.

Prompt

`map_process`

Map or create a process using canonical Oroko step, decision, subprocess and Current/Future State conventions.

Prompt

`analyse_process`

Read an existing process and explain structure, gaps, risks and questions without silently changing it.

Prompt

`improve_process`

Propose a Future State while preserving the factual Current State.

Prompt

`document_process`

Turn Oroko graph data into clear operational process documentation.

Resources available to AI clients

resources/list exposes the four Oroko skill packs plus the canonical Customer Onboarding and Compliance Review JSON examples. resources/read returns the full guidance or example by URI. Prompts and resources guide the model; only tools perform actions.

Tool catalogue

Public tools

Search by tool name or purpose, or filter between read and write operations.

Readlist_processes

List Oroko processes available to the connected user.

Inputs

No inputs.

Readsearch_processes

Search accessible processes by name or description.

Inputs

Name	Type	Requirement
`query`	string	required

Readget_process

Retrieve the canonical graph for an accessible process.

Inputs

Name	Type	Requirement
`processId`	string	required

Writecreate_process

Create a process where the connected user is workspace Owner or Admin.

Inputs

Name	Type	Requirement
workspaceId	string	required
name	string	required
description	string	optional
variants	object	optional
confirmed	boolean	required · true

Writeadd_step

Add a step to an editable process.

Inputs

processId, variantId, name, optional type/description/position, and confirmed: true.

Writeupdate_step

Update an existing step.

Inputs

processId, stepId, optional name/description/position, and confirmed: true.

Writedelete_step

Delete a step from an editable process.

Inputs

processId, stepId, confirmed: true.

Writecreate_connection

Create a connection between two process steps.

Inputs

processId, variantId, fromStepId, toStepId, optional label, and confirmed: true.

Writedelete_connection

Delete an existing process connection.

Inputs

processId, connectionId, confirmed: true.

Writeadd_metadata

Add process-step metadata such as a note, input, output or document reference.

Inputs

processId, stepId, type, value, confirmed: true.

Writesubmit_for_review

Submit an eligible process version for review.

Inputs

processId, optional variantId and changeSummary, plus confirmed: true.

Security

Origin and header validation

The production transport validates trusted origins and mirrored protocol headers. Authentication is always via an Oroko developer key.

Errors

Structured MCP failures

Permission, lifecycle, revision and confirmation failures remain structured so clients can distinguish a denied action from malformed input.

Audit

Write actions are attributable

MCP writes are recorded as MCP actors and retain the developer key identifier used for the operation.