Skip to main content
idapt
HomeAI ModelsExploreResourcesPricing
Sign inUse for Free
  • Home
  • Pricing
  • AI Models
  • Skills
  • Image models
  • Voice models
  • Video models
  • Rankings
  • Multi-Model Chat
  • Agents
  • Computers
  • Drive
  • Automations
  • AI Gateway
  • All features →
  • Blog
  • About
  • Comparisons
  • Benchmarks
  • Model Match
  • Demos
  • Help center
  • FAQ
  • Privacy
  • Support
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Migrate
  • Downloads
  • Desktop
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)Discord
Help Center
🔌

Connect any coding agent

Found this helpful? Share it:

Any coding agent or MCP client can drive your idapt workspace and everything in it: files, agents, computers, 200+ models, and a durable shared memory. There are two paths in: the idapt CLI, or MCP 🔌

Option A: the CLI

Anywhere you have a shell (your machine, a cloud computer, CI, a script), install the CLI and call idapt <resource> <verb>directly.

  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.

Tell your agent it can run idapt commands and discover them on its own with idapt help <resource>and idapt instructions <resource>. See the command reference.

Option B: MCP

Use these connection details with any MCP-compatible tool:

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

  2. Point the client at the idapt MCP endpoint:

    • Endpoint: https://idapt.app/api/mcp

    • Transport: Streamable HTTP (JSON-RPC 2.0)

    • Header: Authorization: Bearer YOUR_IDAPT_API_KEY

  3. Confirm it works with { "action": "workspace list" }.

idapt exposes a single MCP tool, idapt. You reach every capability by passing it { "action": "<resource> <verb>", "args": { ... } }, the same grammar the CLI speaks. See what an MCP client can do for the call shape and Connect your tool for per-client config.

Use idapt Knowledge

Use the workspace Knowledge Base as your durable, cross-session memory. Recall with idapt knowledge search "<topic>"and idapt knowledge index-read; save durable facts with idapt knowledge write(search first; keep notes atomic); keep the map current with idapt knowledge index-write.

Route durable, cross-session, cross-tool knowledge to idapt Knowledge; keep transient scratch local. Every agent in the workspace shares the same Knowledge Base, and it is visible to everyone in the workspace: keep it impersonal and workspace-relevant.

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

🔌

idapt MCP Server

Connect Claude Code, Cursor, Codex, and any other MCP client to your idapt workspace.

⚙️

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

Notifications over MCP

Send notifications from Claude, Cursor, or any MCP-compatible tool.

Was this helpful?