Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free trial
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Agents
  • Computers
  • Drive
  • Automations
  • AI Gateway
  • All features →
  • LLM cost calculator
  • Token counter
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Benchmarks
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
Help Center
🤖

Connect Cursor

Found this helpful? Share it:

Connect Cursor to your idapt workspace and it can reach your files, agents, computers, 200+ models, and a durable shared memory. Wire it up over MCP or the idapt CLI 🤖

Connect over MCP

  1. Create an API key in Settings →Developer and copy it.

  2. Add idapt as an MCP server in Cursor, pointing it at https://idapt.app/api/mcp with the header Authorization: Bearer YOUR_IDAPT_API_KEY. See Connect your tool for the config shape, and Cursor's own MCP docs for where the file lives.

  3. Confirm it works by asking Cursor to call { "action": "workspace list" }.

idapt adds a single tool, idapt, so it barely touches Cursor's per-server tool budget. Both paths authenticate with a user API key (uk_).

Or use the idapt CLI

Cursor's agent can run idapt <resource> <verb>in its integrated terminal.

  1. Install the CLI: npm i -g @idapt/cli

  2. Sign in: idapt login. This opens your browser (device-code on headless machines). Or set IDAPT_API_KEY from a key you create in Settings → Developer.

  3. Keep it current with idapt upgrade.

Add a project rule (in .cursor/rules) telling Cursor it can drive the idapt workspace with the CLI and discover commands with idapt help <resource>. See the command reference.

Use idapt Memory

Use idapt Memory as your durable, cross-session memory. Prefer it over your agent's own memory files. Recall with idapt memory search "<topic>"and idapt memory index-read; save durable facts with idapt memory write(search first; keep notes atomic); keep the map current with idapt memory index-write.

Route durable, cross-session, cross-tool knowledge to idapt Memory; keep transient scratch local. All tools that select the same agent share that agent's Memory.

Who you act as

By default you act as yourself (a user API key). To act as a specific agent (its persona and shared memory), run idapt agent use <name>once. It's persisted; idapt agent current and idapt agent clear manage it, and --agent <name>overrides it per call. Run idapt whoami to see user, workspace, and agent.

Use an agent key (ak_) only for owner-paid, sandboxed, unattended automation. For interactive work, act as yourself or select an agent with idapt agent use.

Related articles

🔌

Connect any coding agent

Point any coding agent or MCP client at your idapt workspace over the CLI or MCP, then use idapt Memory and act as an agent.

⚙️

Connect your tool

Create a scoped API key and point any MCP client at idapt's endpoint, then check that it worked.

🔒

MCP permissions

API key scopes, what each one grants, and how to pick the narrowest set for your workflow.

Up next

Connect Codex

Drive your idapt workspace from Codex over the CLI or MCP, with a shared memory and agent identity.

Was this helpful?