Connect Claude Desktop
Add DogearAI to the Claude desktop app so it can save and recall your long-term context across conversations. There are two ways — pick one.
Before you start
- A DogearAI account — sign up free if you don't have one.
- The Claude desktop app installed.
Option A — Custom connector (recommended)
Newer Claude apps connect over OAuth, so you don't handle a token by hand. In Claude, open Settings → Connectors → Add custom connector and enter:
Name: Dogear
Remote MCP server URL: https://www.dogearai.com/mcpClick add — Claude will send you to DogearAI to sign in and approve, then the connection is live. Enable it in a chat and Claude can use the memory tools.
Custom connectors require a paid Claude plan. On the free plan, use Option B.
Option B — Config file with a token
Works on any version. First generate an access token in your dashboard (MCP Setup → Generate); it starts with dg_.
Then open Settings → Developer → Edit Config (this opens claude_desktop_config.json) and add:
{
"mcpServers": {
"dogear": {
"command": "npx",
"args": [
"mcp-remote",
"https://www.dogearai.com/mcp",
"--header",
"Authorization: Bearer dg_your_token"
]
}
}
}Replace dg_your_token with your real token, save, and fully restart Claude (quit and reopen).
The mcp-remote bridge needs Node.js installed. It lets a stdio-only client reach the remote endpoint.
Verify
In a chat, the DogearAI tools should be available (look for the connector/tools indicator). Tell Claude something worth keeping — "Remember I'm based in Guangzhou and ship with Vercel" — and it saves to DogearAI. Ask later and it recalls. Review everything from your dashboard.
Troubleshooting
- Connector won't authorize: make sure the URL is
https://www.dogearai.com/mcp(withwww) — the bare domain redirects and breaks OAuth. - Config edited but nothing shows: fully quit and reopen Claude — it only reads the config at startup.
- 401 / unauthorized (Option B): the token is wrong or revoked. Generate a new one in the dashboard.
Still stuck? Contact us and we'll help.