Connecting Claude

Steplane has an MCP server, so Claude and other AI assistants can work with your processes. Claude acts as you: it sees and changes only what you can, and what it changes is recorded as yours, made through Claude.

The server's address is:

https://steplane.app/api/mcp

claude.ai and Claude DesktopCopy Anchor Link

1. In Claude, open Settings → Connectors and choose Add custom connector.
2. Name it Steplane and paste the address above.
3. Choose Connect. A Steplane page opens: sign in with your work email if you aren't already, then choose Allow.

On a Team or Enterprise plan, an owner of your Claude organization may have to add the connector first.

Claude CodeCopy Anchor Link

claude mcp add --transport http steplane https://steplane.app/api/mcp

Then run /mcp in Claude Code and choose Authenticate next to Steplane. Your browser opens the same sign-in and Allow page.

With an API key insteadCopy Anchor Link

For scripts, and AI tools that can't sign in with OAuth, create a personal API key under Settings → AI apps and API keys:

1. Give it a name that says what it's for, choose whether it can Read or Read and change, and when it expires.
2. Copy the key straight away: Steplane shows it once and stores only a fingerprint of it.
3. Send it in the X-Api-Key header. For Claude Code:

claude mcp add --transport http steplane https://steplane.app/api/mcp   --header "X-Api-Key: sl_your_key"

A key acts as you, with your permissions; a read key can't change anything. The history shows changes made with it as yours, through that key. Delete a key you no longer use; Settings → AI apps and API keys shows when each was last used.

The same key works with Steplane's REST API, for scripts and integrations: https://steplane.app/api/v1, described at https://steplane.app/api/v1/openapi.json.

Signing in and staying signed inCopy Anchor Link

• Steplane asks you to Allow each app the first time. The page names the app and where it sends you back to; only allow apps you trust.
• Claude stays connected: it renews its access by itself. To disconnect, remove the connector in Claude, or choose Disconnect… under Settings → AI apps and API keys in Steplane. Its access ends within 15 minutes.
• If you belong to several organizations, ask Claude to use a specific one, for example "in Nordlys Logistics".

What Claude can doCopy Anchor Link

Claude can read your processes and answer questions about them, for example:

• "What's our process for a damaged delivery?" Claude finds the process and shows it with its swimlane diagram: steps, who does each, systems, inputs and outputs, links to other processes, ISO clauses with their titles, KPIs and risks.
• "Which processes use the ERP?" or "Where does Finance take part?": processes that use a system, a role, or an input or output, such as an invoice. Useful before replacing a system.
• "Which reviews are due this month?": published processes whose regular review is due or overdue, with their owners.
• "Find gaps in our processes": missing owners or purposes, steps without a role, outputs nobody uses, links to retired processes.
• "What changed in Goods receipt since version 2?": the history of published versions and what changed between any two.
• "How do I ask for approval?" or "Where do I add a member?": Claude looks it up in these docs and answers with a link to the page.

Changing processes with ClaudeCopy Anchor Link

If you're an owner, admin or editor, Claude can also change processes, as you would in the editor:

• create a process, and change its name, purpose, owner, landscape group or review interval
• add, edit, move and remove steps: the role, systems, inputs and outputs, and branches for decisions
• link processes ("uses", "hands off to"); a process that doesn't exist yet becomes a placeholder
• set ISO clauses, KPIs, and risks and opportunities
• choose the standards your organization works towards, such as ISO 9001:2015, and say why a clause doesn't apply, if you're an owner or admin
• set up a draft landscape: Claude asks what your company does, suggests the typical processes, and adds the ones you keep as placeholders in your landscape groups ("We're a wholesaler working towards ISO 9001. Set up our landscape.")
• tell you how your processes cover a standard and what's missing, with what each clause asks for, and propose which process should cover a gap ("Which ISO 9001 clauses aren't covered yet?")
• publish the changes as a new version, with a change note, and record a review
• work in change projects: start one, add the processes it changes, retires or adds, and edit the to-be versions while the live processes stay as they are (Change projects), and analyse a project's impact: Claude runs the checks, reads the processes around the change and adds findings the rules can't see, for example "Analyse the ERP project and tell me what could break". Claude can also take a ready project live, or revert one, if your organization's AI policy lets it publish
• link a change project to a project in your connected Linear workspace, and send its findings there as issues (Linear)
• ask for approval of a change and tell you where it stands ("Who still needs to approve Goods receipt?"). Claude can't approve: that's a person's decision, made in Steplane
• keep the document register: add documents with their number, version, owner and link, and find the processes that use one ("Which processes use I-15-01?")
• make a role such as Quality manager own a process, and set who holds a role, for example "Peter is our new quality manager"
• shape the landscape: add, rename, describe, reorder, nest and remove landscape groups, for example "Split Core processes into Preparation and Execution"

For example: "Add a step to Goods receipt where Finance checks the invoice in the ERP, then publish it as 'Invoice check added'."

Good to know:

• Changes go to the process's working copy, like edits in the app, and anyone who has it open sees them straight away. Nothing changes for readers until it's published.
• While Claude works on a process, its page shows who is behind it, for example Anna Jensen via Claude is editing. It goes away when Claude publishes, or two minutes after its last change.
• The history records published versions as yours, made through Claude, for example "Anna Jensen via Claude (MCP)".
• Your organization may let AI assistants change drafts only (Settings → AI access). Then Claude saves its changes in the working copy and asks you to publish them in Steplane.
• If someone changed the process while Claude was working on it, Claude's change is refused instead of overwriting theirs; Claude reads the process again and retries.