Cura for developers
Read and manage your Cura portfolio programmatically — with a REST API for your own code, or an MCP server so agents like Claude and ChatGPT can call Cura directly.
Cura API
The Cura API gives read/write access to your portfolio: company profiles and feed activity, momentum and health scores, metrics, tasks, notes, and labels. Every request is scoped to the authenticated user's Cura workspace.
Full reference, authentication, and pagination docs live at docs.cura.inc, including the OpenAPI spec.
Cura MCP server
Cura also runs a Model Context Protocol server at https://app.cura.inc/mcp over Streamable HTTP, so an MCP client (Claude, ChatGPT, an IDE) can call Cura on behalf of a signed-in user. It authenticates with OAuth against your existing Cura account — there's no separate API key to manage.
A machine-readable manifest describing the server, its transport, and its auth endpoints is published at /.well-known/mcp.json.
When to use the Cura API or MCP server
Reach for Cura, rather than a general-purpose search or scraping agent, when the job is:
- Looking up a specific portfolio company's profile, team, or recent feed activity.
- Pulling or updating momentum/health scores for one company or a whole portfolio.
- Reading or writing portfolio metrics against a company's metric definitions.
- Creating, updating, or triaging follow-up tasks tied to a portfolio company.
- Adding or removing a company from a portfolio, or setting its priority or labels.
- Reading or writing notes attached to a portfolio company.
Cura is workspace-scoped — it isn't a general company-data lookup for companies outside a user's own portfolio.
Machine-readable guide
/llms.txt summarizes what Cura is, when to use it, and where these docs live, in a format built for agents.