https://core.ravenna.ai/mcp.
Only workspace admins can create these keys. If you are not an admin, ask your workspace admin to generate one for you. Learn how to create and manage API keys.
Multi-workspace access
API keys are scoped to a single workspace, and each MCP server entry only accepts one key. If you work across multiple workspaces, you need a separate MCP server entry for each one, with a unique name to tell them apart.Create an API key in each workspace
Switch to each workspace in the Ravenna web app and create a dedicated API key. Give each key a name that identifies the workspace (for example, “MCP - IT Support”, “MCP - HR”).
Add a named entry for each workspace
In your client’s configuration, add one MCP server entry per workspace.
Specify the workspace when prompting
Your AI assistant will see all sets of tools for each Ravenna workspace you connect. When making a request, mention which workspace you mean so the assistant uses the correct connection. For example, “List open tickets in the IT Support workspace” or “Use ravenna-it to list my open tickets”.Make sure you review the tool call carefully before confirming, to ensure it is using the correct workspace connection.
Configure your AI client
ChatGPT
ChatGPT’s MCP integration requires OAuth authentication, which is not yet supported by the Ravenna MCP server. Support for ChatGPT is coming soon.
Claude Desktop
Each Ravenna workspace has its own API key. Repeat the server block for as many workspaces as you need, just give each a unique name and its own environment variable.Locate your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add an entry to
mcpServers for each Ravenna workspace you want to access. Name each one ravenna-{{ workspace }} and use its corresponding API key:Replace each
your-...-api-key with the API key for that workspace, found in your Ravenna dashboard under Settings → API Keys.Node.js must be installed on your machine for
npx mcp-remote to work. You can download it from npmjs.com/package/mcp-remote.Claude Code
Claude Code manages MCP servers through the CLI. A single terminal command registers the Ravenna server with your API key. No config files to edit.Add the MCP server
Run the command below in your terminal, replacing
YOUR_API_KEY with your actual key.Start a new session
Open a new Claude Code session. The Ravenna tools will be available automatically.
Learn more about MCP servers in Claude Code
Codex
Each Ravenna workspace has its own API key. Add a new MCP integration for as many workspaces as you need, just give each a unique name.Learn more about MCP servers in Codex

- Name:
ravenna-{{ workspace }} - Select
Streamable HTTP - URL:
https://core.ravenna.ai/mcp - Headers key:
Authorization - Headers value: your workspace API key
Cursor
Cursor uses a JSON configuration file for MCP servers. You add the Ravenna server to.cursor/mcp.json, then connect it through Cursor’s settings UI.
Open the configuration file
Create or edit
.cursor/mcp.json in your project root. For global access across all projects, use ~/.cursor/mcp.json in your home directory instead.Add the Ravenna MCP server
Paste the configuration below, replacing
YOUR_API_KEY with your actual key.Connect in Cursor settings
Go to Cursor Settings > Tools & MCP. You should see Ravenna listed. Click Connect if it is not already connected.
Learn more about MCP servers in Cursor
VS Code
VS Code supports MCP servers natively through configuration files. You add the Ravenna server configuration to anmcp.json file, and the tools become available through Copilot Chat in agent mode.
Create the configuration file
Create a file called
.vscode/mcp.json in your project root. For global access across all projects, press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux), select Preferences: Open User Settings (JSON), and add the mcp block shown below.Add the Ravenna MCP server
Add the configuration below, replacing
YOUR_API_KEY with your actual key.Learn more about MCP servers in VS Code
Windsurf
Windsurf uses a JSON configuration file for MCP servers. You add the Ravenna server to the Windsurf config file, then restart the app.Add the Ravenna MCP server
Paste the configuration below, replacing
YOUR_API_KEY with your actual key.Learn more about MCP servers in Windsurf
Other clients
Any MCP-compatible client that supports remote HTTP servers can connect to Ravenna. Use the following connection details and refer to your client’s documentation for where to add remote MCP server configurations.- URL:
https://core.ravenna.ai/mcp - Transport: HTTP (labeled
http,streamable-http, orssedepending on your client) - Authorization header:
Bearer YOUR_API_KEY
The
/mcp endpoint supports both modern and legacy MCP transports. Your client connects to the same URL regardless of which transport it uses, and the server detects the protocol automatically.Test your connection
Check tool availability
Ask your AI assistant: “What Ravenna tools do you have available?” It should list the available MCP tools.
Run a simple query
Try a basic read operation like “List my Ravenna channels” or “Get the current user.”
Troubleshooting
Tools not appearing
Tools not appearing
- Verify your configuration file is in the correct location for your client.
- Check that the JSON is valid (no trailing commas, correct nesting).
- Restart your AI client completely after making configuration changes.
- Confirm the server URL is exactly
https://core.ravenna.ai/mcp.
Authentication errors
Authentication errors
- Check that your API key is correct and has not been revoked.
- Verify the
Authorizationheader uses theBearerprefix with a space before the token. - Ensure there are no extra spaces or newline characters in your key value.
No data returned
No data returned
- Confirm your API key is scoped to the workspace you expect.
- Verify that your user account has the necessary permissions to access the requested data.
- Try a simple operation like “get current user” to isolate whether the issue is with authentication or with a specific tool.
Connection drops or timeouts
Connection drops or timeouts
- Some clients maintain a persistent connection to the server. If your network is interrupted, restart the client to reconnect.
- If the connection drops after a period of inactivity, this is expected. Start a new conversation or restart the client.
- Check that your network allows long-lived HTTPS connections and does not have aggressive idle timeouts.
Learn more about available MCP tools