# Your collections in Claude

> Search your collections, follow a card to other books and read its passage from Claude Code, Claude Desktop or Codex, through Model Hub.

Topic Map puts six tools on Model Hub: five that read, and one that opens the map (it changes nothing). Anything that uses Model Hub's tools can call them: Claude Code, Claude Desktop or Codex connected to Model Hub's MCP server, and Model Hub's own panel when it gains tool use.

| Tool | What it gives |
|---|---|
| `topic-map.collections` | your collections, with their lens, source, size and when each was last indexed |
| `topic-map.search` | the cards for a question, best first, each with its book, its passage and an anchor quoted from it |
| `topic-map.neighbors` | the cards nearest one card in other books: how they treat the same point, and where they disagree |
| `topic-map.get` | one card, or one passage with all its cards |
| `topic-map.read` | a passage's full text |
| `topic-map.open_map` | opens a collection's [map](map.md) in Obsidian and gives back its link as soon as the map opens (a map still being laid out says so); it changes nothing in your vault |

Tools never collapse repeated terms: each card comes back on its own, with its **group** when it has one (its name, and how many books and versions it has; a single card also lists the other cards in its group), so a client can show a term once if it wants. See [Repeated terms](repeated-terms.md).

`topic-map.search` and `topic-map.neighbors` rank as the **Keyword matching** setting says, unless the client asks for `mode: hybrid` (words and meaning) or `mode: vector` (meaning only).

## Connect a client

Switch on Model Hub's MCP server and copy its command, as Model Hub's guide says (Settings → Model Hub → Tools). Ask your client which tools it has: the `topic-map.*` tools are in the list while Topic Map is enabled.

## What it costs

Reading costs nothing. Each search embeds its question with the model Topic Map uses for search (Settings → Topic Map → Models: **Card vectors for search and topics**), a fraction of a cent, which Model Hub's Usage tab shows under Topic Map. Your client's own model is billed by your client, not by Model Hub.

## What leaves your computer

A tool's result goes to the model your client uses: the cards' fields, the anchors quoted from your books, and, for `topic-map.read`, a whole passage. Only what the client asks for is sent. Model Hub's tool-call log keeps a hash of each call's arguments, never the arguments. In Settings → Model Hub → Tools you can set any `topic-map.*` tool to **Ask** or **Deny**.

## When a call is refused

The client sees a refusal that starts with its reason: `collection-missing` (no collection by that name), `not-indexed` (index it first), `unknown-facet` or `unknown-field` (the valid ones are listed), `card-missing` or `unit-missing` (an id that isn't in the index), `invalid-request` (an argument out of range, such as `k` over 50, or a `focus` that is not a card on the map).