Claude Duet and your knowledge base

What Claude Duet can use

Duet runs on a Claude account, so memory, skills, and connectors set up in Claude are available from the first message. It can use connected apps such as Gmail, Google Calendar, Google Drive, and Slack. For websites without a connector, it can use its own cloud browser. See Anthropic’s Duet guide.

How Duet handles memory and chats

Duet uses and adds to Claude memory. Separate topic channels share the same memory. It can also search Duet chats and Claude chats outside projects for earlier context, subject to the Search and reference chats setting. Deleting a chat removes it from that search. See Anthropic’s memory and chat search guide and Duet guide.

What Duet can and cannot see

Duet cannot see every Claude project or all files on a computer. It can read work in Claude but cannot change it. Connected apps are controlled by the user, who starts each connection and can disconnect it later. See Anthropic’s Duet guide.

Custom remote MCP connectors

Anthropic documents custom connectors using remote MCP for Claude, Cowork, and Claude Desktop. They are available across Free, Pro, Max, Ultra, Team, and Enterprise plans, while Free users can have one custom connector. A connector can use an existing remote MCP server or a server built by the user. See Anthropic’s remote MCP guide.

Remote and local MCP are different

Remote MCP servers communicate with Claude over the internet and must be reachable from Anthropic’s cloud infrastructure. Local MCP servers configured in Claude Desktop use the local network, but that separate mechanism is unavailable in Cowork and claude.ai. See Anthropic’s remote MCP guide.

Which plans include Duet

Duet is a research preview available by waitlist to US users on Pro, Max, and Ultra plans. It is not yet available on Team or Enterprise plans. Remote MCP custom connectors have a broader plan range, but that does not establish that Duet supports them. See Anthropic’s Duet guide and remote MCP guide.

Where KnowMan fits

KnowMan keeps saved articles, readable content, citations, and memories such as claims, decisions, and playbooks. Its MCP server runs locally with npx -y @knowman/mcp and is also available as a hosted server at https://api.knowman.io/mcp with OAuth sign-in or an API key. For local setups, see the KnowMan MCP guide and Claude knowledge base guide.

Add the hosted KnowMan server to Claude

KnowMan’s hosted remote MCP server is available at https://api.knowman.io/mcp. The documented setup for clients with MCP OAuth is to add that server URL, then sign in on the KnowMan consent page and approve. The consent page requests knowman.read, which covers search, read, and ask, and knowman.write, which covers saving links. Access tokens last one hour and refresh automatically.

You can use an API key instead of OAuth: create one in KnowMan settings and send it as an Authorization: Bearer <key> header. To disconnect an app, delete its "OAuth: <app name>" entry in your KnowMan API-keys list; changing your KnowMan password disconnects every app.

KnowMan also runs locally with npx -y @knowman/mcp; the open-source client is knowman-mcp. Since Duet uses connectors already set up in your Claude account, adding the hosted server there is the documented path for Claude setups. Then ask the assistant to search or save, for example "search my KnowMan for ..." or "save this URL".