Skip to main content
Ravenna’s MCP server puts your workspace inside whatever AI tool you already work in. Instead of switching to the Admin, you ask your assistant to triage tickets, look up users, or build a workflow, and it does it. The real value shows up when you combine it with the other MCP servers your client is connected to: pull a start date from your HRIS and open an onboarding ticket with it in one message, without copying anything.
The MCP server is in beta. Send feedback to support@ravenna.ai
1

Connect

Every client points at the same endpoint, https://core.ravenna.ai/mcp, and signs you in with OAuth using your existing Ravenna account. Do not set an Authorization header. Your client handles the token.
One command, then a browser sign-in. The callback port matters.
Terminal
Approve the connection in the browser, then start a new session. Run /mcp to check server status.
2

Verify it worked

Ask your assistant:

What Ravenna tools do you have available?

List my Ravenna channels

If you get real channel names back, you are connected. If the tools do not appear at all, restart the client completely, check the JSON for trailing commas, and confirm the URL is exactly https://core.ravenna.ai/mcp.
3

Name the workspace

Your account can span several workspaces, so every workspace-scoped call needs to know which one. Say it in the prompt and your assistant resolves it:

In the IT Support workspace, list open tickets assigned to me

Two rules worth knowing before you debug something that is not broken:
  • OAuth reaches every workspace you belong to. This is why OAuth is the right choice for almost everyone.
  • API key connections are pinned to the workspace that issued the key. Calls to any other workspace are rejected even if you are a member. If you need to work across workspaces in one session, use OAuth.
A “workspace membership not found” error means your account is not a member of the workspace you named, not that the workspace is missing.
4

Understand what it can and cannot do

The server enforces your existing Ravenna roles on every call. Your assistant can do exactly what you can do in the Admin, nothing more:
  • Most workspace tools allow Admin and Member roles
  • Some configuration tools are Admin only
  • A few, like creating users, need organization admin
  • Guests cannot call workspace tools at all
A forbidden error is a role problem. Check your role at Settings > Members.
Learn more about permissions and workspace targeting

​
What to actually use it for

Copilot is better inside the Admin, because it already has page context. MCP wins when Ravenna is one of several systems in the same task. Cross-system ticket creation

Look up Jamie Lee in HiBob, then create an onboarding ticket in the IT Support channel with their department, start date, and manager

Incident follow-up in bulk

Pull the resolution notes from the DNS outage post-mortem in Incident.io, post a summary on all open tickets tagged dns-outage, and move them to Resolved

Planning your own day

What tickets are assigned to me across all my workspaces? Prioritize by due date and flag anything overdue.

Reviewing a channel for stale work

Show me open tickets in the IT Support channel waiting more than 48 hours. Which are unassigned?

Learn more about the full tool catalog and troubleshooting

​
Next

Copilot recipes

The same jobs, done inside the Admin with page context.

Foundry

Give your agents custom tools against your own APIs.
Last modified on September 17, 2026