Cana logocana.build
Product · MCP Hub & Gateway

Connect the tools your agents need.

Connect an MCP server to a Cana chat, a Bot or a Cana App, so the agent can use the tools it exposes. Add your own external, local or hosted MCP server in settings, then use its tools with an agent.

mcp gateway · 10 servers · 214 tools
GitHubJiraSalesforcePostgresServiceNowSlackSAPSnowflakeDatadogInternal APICana MCPauth · scope · audit

Add your own server

Add an external, local or hosted MCP server in Settings → MCP Servers.

Use it in a chat

Give a Cana chat, Bot or App access to the server's tools.

Connected app tools

Connect Gmail, Slack, GitHub, Notion and many more from Integrations.

Controlled access

The connected account and the agent's permission decide what can happen.

Cana MCP

One connection, the right place

A server you connect in settings is available to your chats. A server you add to a Cana App is available to that app. You decide where each connection belongs.

  • Personal MCP servers in Settings
  • MCP servers on a Cana App
  • Test before use
  • Turn a connector off without deleting it
mcp gateway · 10 servers · 214 tools
GitHubJiraSalesforcePostgresServiceNowSlackSAPSnowflakeDatadogInternal APICana MCPauth · scope · audit

Cana MCP

Use the tools you already have

Some things do not need an MCP server. Connect a supported app from Integrations, and the chat can use the tools that connected account makes available.

  • Connect cards in chat for supported apps
  • Gmail, Slack, GitHub, Notion and many more
  • The account you connected decides access
  • Connected-app actions ask for approval by default
01

Connect cards in chat for supported apps

02

Gmail, Slack, GitHub, Notion and many more

03

The account you connected decides access

04

Connected-app actions ask for approval by default

How it works

Cana MCP, step by step.

  1. 01

    Connect

    Add an MCP server in settings or connect a supported app.

  2. 02

    Test

    Check that the server is reachable and see the tools it exposes.

  3. 03

    Assign

    Make it available to the chat, Bot or Cana App that needs it.

  4. 04

    Use

    Ask the agent to do the work with the tools you allowed.

Specifications

Under the hood.

MCP servers

Remote servers connected in settings or to a Cana App

Connected apps

Gmail, Slack, GitHub, Notion and many more

Check

Test a connector before assigning it to an agent

Control

Enable, disable, remove or replace a connection

Use cases

What teams build with it.

01

Use your GitHub tools

Connect GitHub so an agent can find issues and make updates in the account you chose.

02

Bring an internal server

Add your team's external, local or hosted MCP server, then use it from a chat.

03

Add tools to an embedded assistant

Give a Cana App its own MCP server so the assistant can help visitors with your systems.

FAQ

Good questions.

Do I have to build an MCP server?

No. You can connect supported apps from Integrations, or add an external, local or hosted MCP server your team already has.

Can I check a server before an agent uses it?

For web-based servers, Cana checks reachability and available tools before saving. Local Standard I/O servers are validated when an agent starts.

How do I get started with Cana MCP?

Start a Cana chat, then open Cana MCP from the Platform area when it fits the work you need to do.

How do I control what an agent can do?

Choose the permission level that fits the task: Ask, Accept Edits, Research and Plan, or Bypass All.

Can I connect tools to this work?

Cana can use connected apps and remote MCP servers when you have connected and allowed those tools.

Explore Cana MCP. Join the waitlist.

Join the waitlist for early access to Super Intelligent Agents and updates as Cana opens up.