Developers

Connect your AI agent

index365 is built for AI agents. This page is the shortest path from a fresh API key to an agent that can run audits and apply fixes. Read it once to understand where index365 installs, then pick the interface that fits your agent: the MCP server, the CLI, or the agent skills that wrap either.

Which runtime are you using?

Your phone does not need index365 installed. The environment running your coding agent does. index365 (CLI, MCP, skills) installs into wherever the agent actually runs: your laptop, your Claude Code, Codex, Cursor, or Windsurf session, or a CI pipeline.

So the question is not “which device am I on,” it is “where does my agent run.” If you are controlling a desktop agent from your phone, the setup lives on that desktop (or in the cloud environment the agent runs in), not on the phone. A phone controlling a desktop agent uses the desktop's setup.

Once you know where your agent runs, you install index365 there once and every audit, finding, and fix flows through that same environment.

Pick your path

There are three ways to connect, and they share one prerequisite: an API key. The canonical order is get an API key (see Authentication), connect via MCP or CLI, then optionally add skills on top.

Not sure which to pick: if your agent supports MCP, start there. If you live in a terminal or are wiring index365 into CI, use the CLI. Skills sit on top of either and give your agent the audit-and-fix workflow out of the box.

Set up with your agent

The fastest way to connect is to let your agent do it. This page is written so a coding agent can read it and finish the setup itself.

TipWorking with a coding agent? Paste this page's URL (https://index365.co/docs/developers/connect-agent) into Claude Code, Codex, or Cursor and ask it to set up index365. The page contains everything it needs.

When you are ready, head to Authentication for the key step. Once you have a key, the MCP and CLI pages above each walk through connecting in a couple of commands.