What is MCP in Ostrata?

MCP (Model Context Protocol) is the protocol that allows Claude, Cursor, and other compatible clients to connect to Ostrata to read and write your CRM data via controlled tools. Endpoint: https://ostrata.io/api/mcp. Documentation at /docs/api.

Do I need to code to use MCP?

Minimal client configuration (Claude Desktop or Cursor) is needed to connect the endpoint. After that, you use natural language or the exposed tools — without rebuilding a custom API.

Does Pilot replace MCP?

No. Pilot is the CRM chat inside Ostrata. MCP serves external agents and IDEs. Both share the same data.

Does Ostrata replace my billing tool?

No. Ostrata is a flexible-schema CRM (Pilot, SIREN, MCP, EU). Not billing, not PDP, not e-commerce in this positioning.

Can I combine MCP and the REST API?

Yes. MCP for agents/IDE; REST and webhooks for classic integrations.

Is SIREN enrichment available via MCP?

SIREN/INSEE enrichment is native in Ostrata (Operations / views). MCP agents act on your schema objects; for enrichment details, see /siren-crm-enrichment.

What is the price and trial duration?

From €17.10 / seat / month annual. 30-day trial for 1 seat; card charged at end of trial.

Where to find the MCP documentation?

At https://ostrata.io/docs/api (MCP section) and endpoint https://ostrata.io/api/mcp.

Connect Claude and Cursor to your CRM with MCP

Connect Claude Desktop, Cursor, or any MCP client to Ostrata to read and write contacts, companies, and deals live. Flexible-schema CRM, Pilot AI, and EU hosting — without leaving your IDE or assistant.

Try Ostrata Discover MCP

Table of contents

AI agents without live CRM access

Teams using Claude or Cursor to analyze a pipeline or prepare follow-ups hit the same wall: the assistant can't see client records, deals, or up-to-date companies.

You have to export a CSV, paste an excerpt into the chat, then re-enter the result into the CRM. For an SMB that wants useful agents in daily workflows, this back-and-forth breaks the flow. Data becomes stale the moment it leaves the CRM, and no one wants to give an LLM a full database dump.

You need a clean protocol: the agent queries the CRM via controlled tools, reads what it needs, and writes only what you authorize. Ostrata exposes an MCP (Model Context Protocol) server to connect Claude, Cursor, and compatible clients directly to your workspace — without billing module, without PDP, without e-commerce.

Ostrata MCP: read and write the CRM

Ostrata provides an MCP endpoint at https://ostrata.io/api/mcp. Once connected from Claude Desktop or Cursor, you can query and update your CRM objects (contacts, companies, deals, custom objects) from the same environment where you already work.

No copy-paste. No manual export. The agent uses the MCP tools exposed by Ostrata; you keep control over the schema and workspace permissions.

API and MCP documentation

Flexible schema for SMB objects

Unlike rigid CRMs, Ostrata lets you define the objects and fields that match your sales process: industrial prospects, projects, machines, partners — not just imposed 'Contact' and 'Account' tables.

MCP agents work on your schema. You're not forced to map standard tables that don't match your business. Ostrata is not a billing tool or PDP: the focus remains CRM, data, and automation useful to SMBs.

Pilot and external agents on the same data

In Ostrata, Pilot drives the CRM in plain language from Operations. In parallel, Claude or Cursor access the same data via MCP. A sales rep can ask 'follow up on stalled deals' in Pilot, while a builder automates a sync or analysis from Cursor.

One source of truth. Two ways to act: conversational (Pilot) and agentic (MCP).

SIREN and EU hosting

For French SMBs, SIREN/INSEE enrichment remains available on company records. Your workspace data is hosted in the European Union, with operations from Paris under French law — a clear argument for teams sensitive to B2B data sovereignty.

SIREN enrichment in your CRM

Native GDPR compliance, multi-tenant isolation, and operations from France: your B2B data doesn't transit through American clouds.

REST and webhooks as complement

MCP covers the agent / IDE use case. For classic integrations (ERP, scripts, n8n), Ostrata keeps the REST API and webhooks. You choose the right channel: MCP for Claude and Cursor, REST for existing pipelines.