Claude App Connector
Use this only when Claude Code remote MCP is not available. The Claude app custom connector flow can require a tokenized connector URL, so it is a compatibility path rather than the preferred setup.
When to use it
- You need Claude web or desktop app access to UnifiedMemory tools.
- You accept that connector URLs may carry credentials and must be treated like secrets.
- You do not need repo hooks, slash commands, or Claude Code session lifecycle capture.
Preferred alternative
Use Claude Code whenever possible. Header-auth MCP keeps the secret out of the URL and supports local project configuration.
Registry contract
This section is generated from integrations/agent_integrations.registry.json. Edit the registry or generator, not this block.
| Field | Value |
|---|---|
| Integration ID | claude-app |
| Label | Claude App Connector |
| Tier | legacy_connector |
| Setup mode | tokenized_connector_url |
| Agent ID | claude-app |
| App ID | claude |
| Source app / actor | source_app=claude, agent_id=claude-app; key metadata wins over request body hints |
| Default scope | own |
| Config paths | Claude Settings -> Connectors |
| Capabilities | memory.read, memory.write, memory.recall, evidence.read, courtroom.read |
| Supported tools | um_store, um_search, um_profile, um_courtroom |
Capture policy
Legacy remote connector; prefer Claude Code header-auth MCP when possible.
Install command(s)
Open Claude Settings -> Connectors -> Add custom connector, then paste the rendered connector URL only if you explicitly accept tokenized URL risk.
Verify command(s)
Ask Claude app to list UnifiedMemory tools or run a memory search
Risk notes
- Tokenized connector URLs embed credentials in the URL and are last-resort compatibility only.
Official upstream docs
https://docs.anthropic.com/en/docs/claude-code/mcp
Verify
After adding the connector, ask Claude to list UnifiedMemory tools or run a
small memory search. Returned context should use the key-bound claude-app
identity and own-agent scope.
Safety
Do not paste tokenized connector URLs into tickets, docs, screenshots, or shared chat logs. Reissue the connector key if the URL was exposed.