DogearAI
DocsBlogPricingSign inGet started

Connect Cursor

Add DogearAI as an MCP server in Cursor so it can save and recall your long-term context across chats and projects.

Before you start

  • A DogearAI account — sign up free if you don't have one.
  • An access token from your dashboard (see Quickstart, step 2). It starts with dg_.
  • A recent version of Cursor.

Add the MCP server

Open Cursor Settings → MCP → Add new MCP server, or create an mcp.json file. Use ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in a project root for just that one:

{
  "mcpServers": {
    "dogear": {
      "url": "https://www.dogearai.com/mcp",
      "headers": {
        "Authorization": "Bearer dg_your_token"
      }
    }
  }
}

Replace dg_your_token with your real token, then save.

Don't commit a real token to a shared repo. Use a personal token, or keep .cursor/mcp.json out of version control.

Verify the connection

In Cursor Settings → MCP, the dogear server should show a green dot and its available tools. If it's red, click refresh, or re-check the token and URL.

Use it

In Cursor's chat (Agent mode), just work normally. Tell it something worth keeping — "Remember this repo uses pnpm and deploys on Vercel" — and it saves to DogearAI. In a later chat, ask something that needs that context and Cursor recalls it instead of asking again. Review everything from your dashboard.

Troubleshooting

  • Red dot / won't connect: double-check the URL is https://www.dogearai.com/mcp (with www) and the token is current. Regenerate the token in the dashboard if unsure.
  • Tools not appearing: toggle the server off and on in Settings → MCP, or restart Cursor.
  • Older Cursor without remote MCP: use the stdio bridge — set the server to command: "npx", args: ["mcp-remote", "https://www.dogearai.com/mcp", "--header", "Authorization: Bearer dg_your_token"].

Still stuck? Contact us and we'll help.