AI tools: let Claude Code use your library

AI coding tools start every session knowing nothing about what you have read. Connect one to tagit and it can search your library, read the pages you saved, and save new things as it works. This guide covers setting it up, what you can ask for, and what the tool can and cannot reach.

It works through MCP, the open standard AI tools use to talk to other apps. Claude Code is the one this guide walks through. Other MCP clients that accept a URL and a key work the same way.

Connect Claude Code

1. Open Settings from the avatar menu at the bottom of the sidebar.
2. Under Connect AI tools, click Create key.
3. Name the key after where it will live, such as "Work laptop". If you belong to more than one workspace, choose whether the key covers all of them or only one.
4. Click Create key. tagit shows the key and a ready-made command.
5. Click Copy command and paste it into a terminal. It looks like this:

claude mcp add --transport http tagit https://www.tagit.io/api/mcp --header "Authorization: Bearer tagit_sk_..."

6. Start a new Claude Code session and type /mcp. tagit should be listed as connected.

The key is shown once. tagit keeps only a fingerprint of it, so if you lose the key you create a new one.

Run from a project folder, the command connects tagit for that project only. Add --scope user to the command to have it in every project.

What you can ask for

There is nothing to learn. Ask in plain words and mention tagit, at least the first few times, so the tool knows where to look.

Find something you saved.

• "Search tagit for what I saved about CSS colour spaces."
• "Did anyone on the team save something about refresh tokens?"

Search works by meaning as well as by keyword and tag, so you do not need the title. Each result comes with its summary, tags, who saved it and when.

Read a saved page.

• "Read the OKLCH article from tagit and tell me which approach it recommends."

tagit keeps a readable copy of every save, so the tool reads the page as it was when you saved it, even if the original has changed or gone.

See what is new.

• "What did I save to tagit this week?"
• "What has the team been saving lately?"

Save a page.

• "Save this doc to tagit, tag it supabase, and add a note saying it fixed the policy bug."

The page gets a summary and an archived copy like any other save. Saving a link that is already in the library adds the tags and the note to the existing save. Pages behind a login or a bot wall are saved, but tagit may not be able to capture their text.

Save something the tool wrote.

• "Write up what we decided about the API keys and save it to tagit as a note."
• "Save a note to tagit describing how the billing webhook works, tagged billing."

This creates a note, the same kind you write yourself under Notes. It can be up to 20,000 characters, Markdown formatting shows as written, and search finds it like any save. See Notes.

Save what a session used

The pages that solved a problem are usually gone when the session closes. A capture keeps them.

At the end of a piece of work, type:

/mcp__tagit__capture_session

Claude looks back over the conversation and saves the pages the work actually relied on, eight at most, each with a few tags. Then it writes one note that says what was learned or decided and lists those pages with a line on why each mattered. Pages it only glanced at are left out.

You do not have to remember the command. After work that leaned on web pages, Claude offers once to save the useful ones. Say yes and it does the same thing. It never captures without being asked.

A capture is nine saves, and by default Claude Code asks you to approve each one. To approve tagit's two save tools once, add this to .claude/settings.local.json in a project, or to ~/.claude/settings.json for every project:

{ "permissions": { "allow": ["mcp__tagit__save_page", "mcp__tagit__save_note"] } }

Captures go to the workspace the key covers. With a key for a team workspace, that means your teammates see them, which is the point, but worth knowing before you say yes.

With a team

Connect a key to a team workspace and the tool searches the whole team's library, not only your saves. A page one person saved is there for everyone's AI tools, and results say who saved it.

The same goes for notes the tool saves. A decision written down in one session can be found from a teammate's session the next day.

One thing stays personal: the note attached to a saved page ("add a note saying why") is private to you, as it is everywhere in tagit. If the reason should reach the team, ask for a standalone note instead. See Team workspaces.

What a key can reach

A key acts as you. It reaches the libraries of the workspaces you belong to, or only the one workspace you chose when creating it.

• It can search, read and add. It cannot edit or delete anything.
• It does not reach shared collections, only workspace libraries.
• Saves it makes are private, like saves from the extension. Nothing it does makes a page public.
• It sees your own notes on saves, never a teammate's.

Treat a key like a password. Anyone who has it can read the full text of everything in those workspaces. Do not paste it into chats or commit it to a repository.

Revoke a key

Settings, Connect AI tools lists your keys with the workspace each one covers and when it was last used. Click Revoke next to a key and it stops working at once. Revoking does not remove anything the key saved.

Use one key per machine or tool. Then you can revoke the one on a lost laptop without reconnecting everything else.

If something does not work

• tagit is not listed under /mcp. The command connects one project folder unless you add --scope user. Sessions that were already open also need restarting.
• "Missing or invalid API key". The key was mistyped or revoked. Create a new one and run the command again. If a tagit entry already exists, remove it first with claude mcp remove tagit.
• The tool does not use tagit. Say so in the request: "search tagit for...".
• "No workspace matches". The key is limited to one workspace and the request named another. The message lists the workspaces the key can use.
• "Rate limit reached". The key made more than 60 requests in a minute, or more than 10 saves. Wait for the next minute.
• "tagit does not save this URL". The page is on localhost or an internal host, or the address carries a token or key. An AI tool is never allowed to save those. Save it yourself with the extension if you need it.
• A saved page has no text. tagit could not fetch it from its servers. Save it with the browser extension instead, which captures the page as you see it.

Limits

Connecting AI tools is part of Premium and Team. On the free plan, creating a key opens the upgrade options.

The Claude chat apps (claude.ai and the desktop chat) cannot connect yet. They need a sign-in flow that tagit does not have so far.

A key can make 60 requests a minute, and at most 10 of those can be saves. Past that the tool is told to wait, which it will. A person working with an AI tool should never notice; the limit is there to stop a tool stuck in a loop, or a key in the wrong hands.

When a tool reads a very long page it gets the first 50,000 characters. Notes on a save are limited to 5,000 characters.