Connect Tana to Claude so you can use your team's meetings, tasks, decisions, and documents as context in a Claude conversation, then save new work back into Tana when you're done.

Tana connects to Claude through the Model Context Protocol (MCP), an open standard that lets Claude read from and write to external tools. Once connected, Claude can pull documents, meeting notes, and structured data out of Tana for context, and propose new content back into Tana. This guide covers the one-time setup, what Claude can access, and how to use the connection.

What you can do with Tana in Claude

Once Tana is connected, ask Claude to:

Pull context out of Tana

Get meeting context: read transcripts, screen-share screenshots, attendees, and attached artifacts from a meeting
Work with tasks: list open tasks, or plan work from an existing task
Search your workspace: full-text and semantic search across spaces for notes, docs, and decisions
Read a specific document: pull up a design doc, spec, or typed entry with all its fields
Check calendar events: see what's on today, or prep an upcoming meeting from its details

Save work back to Tana

Create documents: save a summary, spec, or recap as a doc in Tana
Create typed entries: file a Bug, log a Decision, or add any typed document with the right fields
Create and update tasks: add follow-ups, or break an existing task into sub-tasks
Update existing documents: append notes or edits to a doc already in your workspace

Every change Claude makes is a proposal you review and approve in Tana. See Working with proposals below. Nothing is written without your confirmation.

Connect Tana to Claude

You only need to do this once. The connection is per-account.

Tana isn't in Claude's built-in connector directory yet, so you add it as a custom connector using Tana's MCP server URL: https://home.tana.inc/mcp. In Tana, Settings → MCP has a one-click copy for the URL and ready-made setup snippets.

In Claude Code

Add Tana with a single command:

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

The first time you use it, Claude Code walks you through signing in to Tana.

In Claude Desktop or claude.ai

Claude connects to Tana through Anthropic's connectors flow:

In Claude, open Settings, then Connectors.
Choose Add custom connector.
Paste the Tana MCP server URL: https://home.tana.inc/mcp.
Click Connect. A Tana sign-in window opens. Sign in if you aren't already, and grant access to the workspace you want to connect.
The window closes and Tana shows as a connected tool in Claude.

Custom connectors are available on all Claude plans; free accounts can keep one at a time. For the latest steps on Claude's side, see Anthropic's guide to custom connectors.

You can now reference Tana in any Claude conversation.

What Claude can access

Claude works only with the content in the workspace you connected, and only when a prompt asks for it:

Search: full-text and semantic search across your spaces
Read: notes, typed entries and their fields, tables, backlinks
Meetings: transcripts, screen-share screenshots, event details, attendees, artifacts
Files: text-based attachments like markdown, CSV, and plain text, plus images; other files come back as metadata such as name, type, and size
Create: documents, tasks, and typed entries
Update: text, fields, task state, assignments, tables
Delete: remove documents, with your approval

The Tana connector reads and writes only your Tana content. It does not access your Claude memory, chat history, or files you've uploaded to Claude.

Tana captures the shared screen during a meeting, not participants' camera video, so the screen-share screenshots Claude can read never include people's faces.

Using Tana in Claude

Ask in plain language; Claude picks the right Tana tool from your prompt. Some prompts to try:

"Read the transcript from yesterday's standup in Tana."
"Find my notes about the Q3 roadmap in Tana."
"List all open bugs in Tana" or "Show me all Feature Requests assigned to me."
"Prep my 2 pm meeting: read the details and attached artifacts."
"Save this summary as a doc in Tana called 'API Migration Plan'."
"Add a task in Tana to review the pull request by Friday."

Example workflows

1. Turn meeting outcomes into a draft

"Read the transcript and outcomes from yesterday's design sync in Tana, then draft a one-page recap with agreed decisions and owners I can paste into Slack."

Claude finds the event, reads the transcript and any pinned artifacts, and produces a recap grounded in what was actually said. It's read-only, so nothing is written to Tana.

2. Research across your workspace and draft a spec

"Search Tana for everything related to our authentication system, the bugs, design docs, and decisions, then draft a technical spec for the new SSO feature, citing the source docs."

Claude searches across your spaces, reads each match, and produces a spec that links back to the source documents in Tana. Useful when context is scattered across many notes and meetings.

3. Capture work output back in Tana

"I just finished this Q2 metrics analysis. Create a doc in Tana titled 'Q2 Metrics Analysis' with the content above, and create three follow-up tasks for the action items."

Claude proposes the document and three tasks. They appear in Tana for review. You approve them and they land in your workspace.

Working with proposals

Every write Claude makes, whether creating a document, updating a field, or deleting an item, goes through Tana's proposal system. The change appears as a pending proposal in Tana that you review and approve before it takes effect. This is the same review loop Tana's own Chat uses, so nothing is added, changed, or removed in your workspace without your confirmation.

To view proposals created from external tools like Claude, click Browse in the sidebar, then view Chats.

Always check proposals before approving, especially updates to existing documents. See Proposals for how the review surface works.

Tips

Be specific about spaces: if similar document names exist in different spaces, mention the space so Claude finds the right one.
Reference meetings by date or title: Claude can look up events by date range or by name.
Ask for a specific kind of document: a Bug or a Decision lands with the right fields, in the right space.

Disconnect Tana

To remove the connection in Claude Code:

claude mcp remove tana

In Claude Desktop or claude.ai, open Settings, then Connectors, and disconnect Tana.

Disconnecting stops Claude from reading or writing to Tana. It does not delete any data already in your Tana workspace. You can also review or revoke access from your Tana account settings.

Troubleshooting

Claude says it can't reach Tana. The connection has likely expired or been revoked. Reconnect with the steps above.

Claude can't find a document. Paste the document's Tana link straight into the conversation and Claude opens exactly that item, no searching needed. Otherwise, name the space, or reference the item by its type or exact title. Semantic search helps when you don't remember the exact wording.

A proposal didn't appear in Tana. Proposals land in the workspace you connected. If you have access to more than one, confirm you're looking at the right one.

Something else? Reach out at support@tana.inc, or see MCP for the broader overview.