Create, search, update, and manage data in OnePageCRM from Cursor, over the Model Context Protocol.
Add the plugin from the Cursor Marketplace and authorize when prompted. Authentication is OAuth 2.1, so there is no API key to paste.
The connection acts as the signed-in user and respects that user's existing OnePageCRM permissions. You choose read-only or read-write on the consent screen.
| Tool | Purpose |
|---|---|
query |
Read data via OQL, with filters, ordering, lookups and aggregates |
create |
Create a contact, deal, action, note, call or meeting |
update |
Update an existing record |
describe |
Entity schemas: field types, query traits, writable and required flags |
context |
Account reference data: statuses, pipelines, users, tags, custom fields |
feedback |
Report a gap or problem with the server |
Queryable entities: contacts, companies, deals, actions, notes,
calls, meetings.
Reads go through OQL, a JSON query language over the CRM. Won revenue this quarter by owner:
{
"from": "deals",
"select": ["owner_id", "count()", { "sum": ["amount"] }],
"where": { "status": "won", "close_date": "THIS_QUARTER()" },
"group_by": ["owner_id"]
}The schema is an allowlist, so an unknown field or an unsupported operator fails with a message naming the problem rather than returning a partial result.