Project memory for Claude Code, Cursor, and Codex

Connect Claude Code, Cursor, or Codex to Orbit Desktop’s local MCP server so you can recall project notes, open tasks, and decisions from a new conversation.

Orbit Desktop can give an AI coding tool access to the tasks, notes, and documents you’ve saved for a project. Start a fresh conversation, ask where you left off, and have the client read that project’s context through the local Model Context Protocol (MCP) server.

Connect your client to Orbit

In Orbit, open Settings → Connections → Connect an AI client and select Copy configuration. Keep the command and arguments from your installation. If you use Linux and need a stable path for MCP, install the .deb package on Debian or Ubuntu.

  • Claude Code. Merge the copied orbit entry into the mcpServers object in your project’s .mcp.json. Restart Claude Code and approve the server when prompted. Run claude mcp get orbit to check the connection. See Claude Code MCP setup.
  • Cursor. Merge the copied entry into mcpServers in .cursor/mcp.json for the project, or ~/.cursor/mcp.json for global setup. Verify Orbit appears in Cursor’s MCP settings. See Cursor MCP setup.
  • Codex. Run codex mcp add orbit -- followed by the command and arguments from the copied entry. If the entry includes environment values, pass them as --env KEY=VALUE before --. Run codex mcp list to check the registration, then restart your session. See Codex MCP setup.

For troubleshooting and the scope of available tools, see Connect an AI client with MCP.

Resume work from saved context

Start with a read-only request such as “Find my expense tracker project in Orbit. Read its current tasks and the latest handover, then summarise what I can pick up next.” After the work, ask the client to update the relevant card or document with the result. Save details you’ll need in future sessions, such as the reproduction steps or why you chose a particular approach.

Orbit keeps the workspace on your computer. The AI client can send retrieved content to its configured provider, so use its data controls and ask it to read only what it needs. Check Orbit’s MCP access boundaries before using it with sensitive workspaces.