Connecting your agent

Your coding agent talks to IntentDocs over MCP, the standard way for coding agents to use outside tools. Once it's connected, the agent reads stories and criteria live, saves its plans and tests, and reports results to the story it built. Edit the spec in the web app and the agent sees the change on its next call.

The server

Use the www. address. The bare domain redirects to it, and an Authorization header is dropped on that redirect.

The quickest way: OAuth

A client that supports MCP OAuth needs only the URL. Add this to its MCP config, and it opens your browser to sign in the first time it connects:

{
  "mcpServers": {
    "intentdocs": {
      "url": "https://www.intentdocs.com/api/mcp"
    }
  }
}

With a token

If your client can't sign in through the browser, use a token.

1. Open your project's Overview and choose Connect an agent on the Connections card. That opens Connect your agent. You can also manage tokens under Settings → Access Tokens.
2. Pick your tool: Claude Code, Cursor, Claude.ai, Other / Manual, or Chat builder (Lovable, Bolt, v0…).
3. Create a token and copy it. It is shown once.
4. Add the server the way the page shows. For Claude Code, run the claude mcp add command it gives you, or put its config in .mcp.json in your project root. Claude Code's config uses "type": "http". See Claude Code setup. For Cursor, the config below goes in .cursor/mcp.json.

{
  "mcpServers": {
    "intentdocs": {
      "type": "streamable-http",
      "url": "https://www.intentdocs.com/api/mcp",
      "headers": {
        "Authorization": "Bearer intent_cli_your_token"
      }
    }
  }
}

5. Restart your agent. The page shows Waiting for first request until the agent calls, then Connected.

For Claude.ai, the page walks you through adding an MCP server: enter the server URL, set authentication to None, and add a custom header named Authorization with the value Bearer intent_cli_your_token.

A chat builder such as Lovable, Bolt or v0 has no MCP setup. The page gives you a prompt to paste instead, with the next story filled in.

Full steps for each client are in Claude Code setup and Cursor and remote setup.

Which workspace it reads

A token is bound to one workspace, your personal workspace or a team workspace, for its whole life. Switching workspace in the browser doesn't move it. Your agent names the workspace it is reading from in its first answer.

In a team workspace, an admin may need to approve a new agent before it can read the workspace's projects. Until then it reads your personal projects only. See Workspaces and teams.

Check it works

Ask your agent to list your IntentDocs projects. It should call list_projects and say which workspace it's reading. Then try:

Use the intentdocs MCP to show me the next story to build in <project name>.

Note: an agent loads the tool list when it connects and keeps it until it reconnects. If it says a tool doesn't exist, reconnect the IntentDocs connector, allow any new tools it asks about, and start a new session.

Next

Install the CLI to connect your repository, or go straight to the web app.