Developers

Build on Cura.

Read and manage your Cura portfolio from your own code with the REST API, or let agents like Claude and ChatGPT call Cura through the MCP server.

Cura API

The Cura API gives read and 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.

The full reference, the authentication and pagination docs, and the OpenAPI spec are at docs.cura.inc.

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, so 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

Use Cura instead of 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 and 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 scoped to a workspace. It isn't a general 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.

Other resources

For general help, see Support. For data handling and infrastructure, see Security.