Also known as: Model Context Protocol native, MCP-first
MCP-native describes a platform built with Model Context Protocol (MCP) as a first-class interface. MCP is the emerging open standard, introduced by Anthropic and adopted across Claude Desktop, Claude Code, Cursor, and other AI tools, that lets AI agents interact with external systems. An MCP-native platform exposes its data and actions through MCP, so any MCP-aware AI tool can operate on it.
Where you'll see mcp-native in day-to-day work inside Helm.
Helm ships an MCP server (`packages/mcp-server/`) that exposes every major entity (projects, tasks, contacts, invoices, time entries, documents, calendar events) to any MCP client. You can manage Helm from Claude Code in your terminal, from Claude Desktop on your desktop, from Cursor while coding, or from any other MCP-aware agent framework. The MCP server uses the same permission model as the rest of the platform. Workspace scoping, role-based access, and audit logs apply equally.
Concepts that show up in the same workflows and reports.
Common questions and honest answers.
No. Helm works fully through its web UI, Slack integration, and email. MCP is for teams that want to operate Helm from Claude Code, Cursor, or other AI-native development environments.
Any MCP-compliant client. Tested with Claude Code, Claude Desktop, Cursor, and Windsurf. MCP is an open protocol. New clients work as they ship.
MCP access is included on Pro and Business plans. Starter plans do not include MCP.
Helm is the AI work platform where these concepts stop being theory and start being your Monday morning.