Assistants
Use Boundlane from the assistant you already use.
Boundlane is a remote MCP server. Connect it once, sign in as yourself, and choose what the assistant may do. It acts as you, inside the rules your workspace set.
https://boundlane.com/mcpWhat it can do
- See automations, runs, pending approvals and open exceptions in the workspace you connect.
- Start and continue a Studio build session from a description of the process.
- Call actions an automation exposes to assistants, each one decided by that automation’s policy before it runs.
What it cannot do
- Decide an approval. You decide it on Boundlane; the assistant hands you the link.
- Do more than you can, or more than you granted when you connected it.
- Perform anything your workspace forbids, in any rollout stage.
- Promote a version, change a rollout stage, or touch credentials, members or billing.
Where each host takes the address
Claude
Add a custom connector in Claude’s connector settings and paste the address. Claude Code takes the same address with claude mcp add --transport http.
ChatGPT
Add Boundlane as an app with this address from ChatGPT’s apps settings. Business and Enterprise workspaces may need an administrator to allow it.
Cursor, VS Code and other IDEs
Add a remote MCP server with this address to the editor’s MCP configuration. The editor opens the sign-in when it first connects.
Copilot Studio, Gemini Enterprise, Perplexity, Le Chat
An administrator adds a custom MCP connector for the organisation with this address and OAuth sign-in. Members then connect from the assistant.
Agents you built elsewhere
An automation can expose some of its actions to agents built on other platforms, through the Control Gateway. The outside agent proposes each call; the automation’s policy decides it, with the same rollout stages, approvals and forbidden actions as the automation’s own runs. Every call is recorded as a run you can inspect.
You can see and disconnect every connected assistant under Settings → People & access.