# Pulse Documentation

> Pulse is an AI project intelligence platform. These docs cover features, integrations, and developer references. Each article below links to a clean Markdown version for machine reading.

## MCP Server
Connect your IDE or AI agent — Claude Code, Cursor, VS Code, Windsurf, and more — to your Pulse workspace over the Model Context Protocol.

- [Connect the Pulse MCP Server](https://pulseios.com/docs/mcp/connect-pulse-mcp/llms.md): The Pulse MCP server exposes ~110 workspace tools over the Model Context Protocol at https://api.pulseios.com/mcp. Auth: personal API key (pulse_sk_…) created under Profile → API Keys, sent as a static Authorization: Bearer header. This is the only auth method (no OAuth/browser sign-in). Works in any MCP client: Claude Code (claude mcp add --transport http pulse https://api.pulseios.com/mcp --header "Authorization: Bearer pulse_sk_…"), Cursor / VS Code (Copilot) / Windsurf / Cline / Zed / JetBrains via JSON config (url + Authorization header), and stdio-only clients (Claude Desktop, OpenAI Codex, Gemini CLI) via the mcp-remote bridge. Every call is scope- and RBAC-gated: the key acts as you and can never exceed your role; revoke takes effect on the next request. Tool domains: tasks, tags, projects, sprints, milestones, members & workload, goals & OKRs, workspace & analytics, capacity, ownership, RAID (+ AI intelligence), cross-project dependencies, strategy artifacts, pulse analysis, documents & ADRs, file reading, scheduled workflows, and integrations (GitHub, Jira, Linear, Asana, Trello, Monday.com, HubSpot). Also serves pulse:// resources, reusable prompts, and a Claude Code skill (pulse-mcp).