Connect an MCP server
In this guide, you’ll connect a remote MCP server to your workspace, check the impact class Orqane gives each of its tools, assign the tools to an employee and test them in a sandbox. We use Linear as the example, but the steps are the same for any remote MCP server. It takes about 15 minutes.
Before you start
Section titled “Before you start”- The Builder role or above.
- The URL of a remote MCP server that supports the Streamable HTTP transport, for example
https://mcp.linear.app/mcp. - An account on the service behind the server, or an API key for it.
- An employee to give the tools to. This guide uses
Adafrom the Quickstart.
Connect and assign the server
Section titled “Connect and assign the server”Add the server
Go to Settings > Capabilities > MCP servers and click Add server. Fill in:
| Field | Value |
|---|---|
| Name | Linear |
| URL | https://mcp.linear.app/mcp |
| Authentication | OAuth |
| Credentials | Workspace credentials (every granted employee shares one account) |
Click Connect. Orqane opens Linear’s sign-in page. Sign in and authorize access.
Review the discovered tools
Orqane lists every tool, resource and prompt the server offers. Each tool gets a proposed impact class, based on its name, description and MCP annotations such as readOnlyHint and destructiveHint:
| Tool | Proposed impact class |
|---|---|
list_issues |
Read |
get_issue |
Read |
create_comment |
Write internal |
create_issue |
Write internal |
update_issue |
Write internal |
delete_issue |
Irreversible |
Check each one against what the tool really does. If a tool notifies people outside your company, open the menu next to it and choose Communicate. When in doubt, pick the stricter class.
Enable the tools you need
Turn on the toggle next to list_issues, get_issue, create_comment and create_issue. Leave delete_issue and update_issue off. Disabled tools are never shown to an employee, whatever its level.
Click Save. The server’s status changes to Healthy.
Grant the tools to an employee
Open Employees, select Ada and go to the Tools tab. Click Add tools, choose Linear and select the tools Ada needs: list_issues, get_issue and create_comment.
Ada’s autonomy level now applies to each tool. At L1 Approve, she reads issues on her own and asks before she comments.
Test in a sandbox
On the Tools tab, click Test next to Linear. Orqane opens a test chat in a sandbox. Write:
List the five most recent open issues in the Mobile team and add a commenton the oldest one asking for an update.In a test, Read and Draft actions run for real and every other action runs as a dry run: Ada shows the exact call she would make, with its inputs, without sending it. Check the inputs, then click Close test.
You’ve connected an MCP server, checked what each of its tools can do and given Ada exactly the tools she needs.
Keep the server healthy
Section titled “Keep the server healthy”- Settings > Capabilities > MCP servers shows each server’s status: Healthy, Degraded, Auth expired or Down.
- When a server adds a tool or changes a tool’s description, Orqane flags it and keeps the new version disabled until a Builder reviews it.
- If the status is Auth expired, click Reconnect. Runs that need the server pause at a checkpoint and resume after you reconnect.
- To revoke access, click Disconnect. Every employee loses the server’s tools immediately.