Developer Resources

Everything you need to integrate IntentDocs into your AI coding agent, CI pipeline, or custom tooling.

Quick Start

1Install the CLI

npx intentdocs init

2Add MCP config

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

3Start building

Your agent reads specs live and writes progress back via MCP.

API & Integration Endpoints

OpenAPI Specification

JSON

Full API reference in OpenAPI 3.1 format. 28 operations covering projects, story maps, sync, and MCP.

MCP Server

MCP

Model Context Protocol endpoint with streamable-http transport. 20 tools for spec-driven development.

MCP Manifest

JSON

Machine-readable manifest listing all MCP tools, their schemas, and authentication requirements.

MCP Discovery

JSON

Standard discovery file at /.well-known/mcp.json. Points agents to the MCP server, transport, and OAuth metadata.

OAuth Server Metadata

JSON

OAuth 2.1 authorization server metadata (RFC 8414). PKCE-only, 6 scopes, dynamic client registration.

OAuth Resource Metadata

JSON

Protected resource metadata for the MCP API endpoint. Links to the authorization server.

llms.txt

TXT

Product overview optimised for AI agents. Covers features, pricing, CLI reference, and page index.

Sitemap

XML

XML sitemap of all public pages for crawlers and agents.

Versioning & Deprecation

The IntentDocs API uses date-based versioning. Every API response includes an x-api-version header with the current version date.

Breaking changes are announced at least 90 days in advance via the Deprecation and Sunset response headers. Non-breaking additions (new fields, new endpoints) ship without version bumps.

Authentication

IntentDocs uses OAuth 2.1 with PKCE for agent authentication. MCP clients discover the auth server automatically via the server metadata endpoint.

Available scopes: read:projects, write:projects, read:maps, write:maps, read:specs, write:specs.