Integrations and MCP

All integrations are configured in Settings. Click "Connect" to start the OAuth flow and authorize the service. On the desktop app, the authorization page opens in your default browser so passkeys and password managers work; Tana finishes the connection once the provider reports it as active. On the web, authorization opens in a popup. Once connected, the integration is available to AI in chat and through skills.

You can disconnect or reconnect integrations at any time from the same settings page.

Connect Google Calendar or Microsoft Outlook to see your events in Today. On the desktop app, connecting or reconnecting a calendar opens the provider's sign-in page in your default browser, so passkeys and password managers work.

The first time you connect a provider, Tana enables that account's primary calendar automatically so Today has events to show right away. After that, enable the specific calendars you want to sync. Each calendar can be enabled, disabled, or force-synced individually. Events sync automatically when changes happen on either side, and you can trigger a manual sync at any time. If you disconnect and later reconnect the same provider, Tana remembers the calendars you previously had enabled and turns them back on for you.

If a connected calendar stops syncing for any reason, Tana surfaces a Calendar needs reconnect indicator next to your account in the sidebar and on the calendar settings page. Reconnecting the affected provider clears the warning. The reconnect dialog tells you that reconnecting clears your current calendar selections so you know to re-pick them afterwards.

If an account is connected without write permission, Calendar settings shows it with an amber Read-only row and an Enable edits action that runs the consent flow to grant write access. The per-calendar write toggles stay dimmed until it is granted.

Synced events show their original title, time, attendees, and external meeting link. You can add talking points, start a chat, and extract outcomes from synced events the same way as Tana-created meetings.

For more on working with synced events, see Meetings.

Connect your GitHub account to work with repositories, issues, and pull requests from AI chat.

What the AI can do with GitHub:

• Repositories: List your repositories and browse directory contents
• Issues: Search, read, create, update issues. Add comments.
• Pull requests: List, create, review, merge PRs. Add comments.
• Code: Read file contents from repositories

When a skill is attached to a type for GitHub issue creation, you can file an issue from the item's Send to menu; the AI asks which repository when the item does not make it obvious, then links to the GitHub issue once it is created. Filing an issue from a meeting reads the transcript, pulls in screen-share screenshots, and asks a clarifying question if the surface is ambiguous, then attaches an automatic Screenshots section to the issue body.

Two levels of Slack integration:

Organization-level (admin): Install the Tana Slack app to enable the /tana slash command in your Slack workspace.

Personal: Connect your Slack account to let AI chat send messages and access channels.

What the AI can do with Slack:

• List channels and users
• Send direct messages
• Send channel messages

Mentioning @tana in a thread: Mention @tana in any Slack thread to bring Tana into the conversation. It posts a thinking placeholder and edits it in place with the answer, and keeps a running chat per thread so follow-ups have context. It reads the earlier messages in the thread and any files shared there, and ingests image, PDF, text, and JSON attachments on the mention, so you can drop in a screenshot or document and ask about it. Tana only uses what each participant in the thread is allowed to see.

If your Slack email does not match a Tana account, @tana and /tana reply with an open in Tana link that pairs the two identities, so future mentions resolve to you.

Connect Linear to create and manage issues from meetings and chat.

What the AI can do with Linear:

• List teams
• Search existing issues
• Create new issues
• Update issues

Like GitHub, Linear has a system skill for creating issues from typed items. Attach it to a type and run it from any item's Send to menu.

Connect Jira to create and update issues from meetings and Chat. Useful for pushing bugs and feature requests out of meeting outcomes and into the project tracker.

What the AI can do with Jira:

• List Jira projects the connected account has access to
• Search issues by free text, optionally scoped to a project key
• Create issues with summary, description, type, priority, labels, assignee, and parent (for subtasks or epics)
• Update an existing issue's summary, description, priority, labels, assignee, or workflow status

Filing a Jira issue from a meeting reads the transcript and embeds screen-share screenshots into the issue description as visual context, the same way it works for GitHub.

Connect HubSpot to read and update CRM data from Chat. Useful for pulling context into a meeting prep, logging a note after a call, or moving a deal forward without leaving Tana.

What the AI can do with HubSpot:

• Contacts: Search by name, email, company, or domain. Look up full details and the deals associated with a contact. Update lifecycle stage, lead status, and any contact property (job title, phone, custom properties).
• Companies: Search by name or domain. Update lifecycle stage and any company property (industry, employee count, custom properties).
• Deals: List recent deals sorted by last modified. Create a new deal and associate it with a contact or company.
• Notes: Create a note and attach it to a contact, company, or deal, for example to log meeting takeaways straight into the CRM record.

Property names follow your HubSpot configuration (HubSpot internal property names like lifecyclestage or hs_lead_status, with the values configured in your account).

New to HubSpot in Tana? Follow the setup guide for the connect flow, example prompts, and troubleshooting.

Beyond the built-in integrations above, Tana can connect to your own remote MCP servers, so any tools they expose become available to AI chat. This is how you bring a service Tana does not integrate with directly, your own internal server or a third party's, into the AI.

To add a server, go to Settings, Custom MCP servers:

1. Enter the server URL and authorize it over OAuth. On the desktop app, the authorization opens in your default browser so passkeys and password managers work.
2. If a server does not let Tana register itself automatically, the connect step says so, and you can add it with a Client ID and Secret instead.

Each connected server is private to you; other members of your organization do not see it.

Connecting a server adds a linked skill for it. The server's tools enter a chat only when that skill is in scope, so a connected server does not add tools to every conversation. Manage the connection from the skill's panel:

• Tool catalog: every tool the server exposes, with the server URL and when it was last synced. Use Refresh tool catalog to re-read the list after the server changes.
• Allow or deny each tool: a per-tool control. A denied tool is never offered to the AI or called on your behalf, and it stays denied across a catalog refresh.

Remove a server from the same settings page to disconnect it and drop its tools.

This is the inverse of Tana's own MCP server, which lets external AI tools connect into Tana.

Tana can hand off the current document or chat context to an external coding tool as a self-contained prompt. The hand-off is driven by the built-in Open in coding tool skill (see Skills) and triggers on phrasings like "create a PR", "open a pull request", or "send this to Cursor". When more than one tool is enabled, the AI asks you to pick. When the repo or project is not named in the source material, the AI asks where the change should land instead of guessing.

Available coding tools:

• Claude Code: Anthropic's CLI coding agent, desktop app only. Configure one or more named projects (name and local folder path) in Settings, Coding Tools. The AI launches Claude Code in the chosen project folder, and the session URL appears as a clickable link in the chat. The web app shows a "Requires desktop app" note.
• Codex: OpenAI's coding agent
• Cursor: AI-first code editor
• GitHub Copilot: GitHub's AI pair programmer (opens in VS Code)
• Lovable: AI full-stack app builder
• v0: Vercel's AI UI builder

Enable or disable individual tools in Settings, Coding Tools. Each tool has a toggle to control whether the AI can use it. When a tool is used in chat, an "Open in [tool name]" button appears in the conversation. If the prompt is too long to fit in that tool's launch link, a note appears above the button with a Copy full prompt action that puts the complete prompt on your clipboard; the shortened link still works as a secondary action.

Tana provides a Model Context Protocol (MCP) server that lets external AI tools connect to Tana. From a client like Claude Code or Claude Desktop, an agent can read documents, search content, create and update items, and use the same capabilities available in Tana's built-in chat.

The server lives at https://home.tana.inc/mcp, and authentication is handled automatically over OAuth. Settings, MCP has a one-click copy for the URL and ready-made configuration snippets.

MCP works in both directions. This page covers Tana as a server, external AI tools reaching into Tana. For the reverse, connecting Tana to your own MCP servers so their tools become available in chat, see Custom MCP servers in Integrations.

Add Tana to Claude Code with a single command:

claude mcp add tana --transport http https://home.tana.inc/mcp

The command and URL are available for one-click copy in Settings, MCP.

Claude Desktop connects to Tana through Anthropic's connectors flow. From the Settings, MCP page in Tana, follow the link to Anthropic's "Use connectors to extend Claude's capabilities" guide and add Tana with the MCP Server URL shown on the page.