OnePageCRM

Account-specific reference data: statuses, lead sources, call results, pipelines, users, tags, reason lost options, custom fields, and the account currency. Also the account's saved templates: predefined_actions (a name plus a 'days' offset for the due date) and predefined_items (deal line items with cost and price). Call before creating or updating records to get valid field values, before quoting any money value to get the currency to label it with, and whenever the user names a template ("my Follow-up template") so you can match it by name.

context

Create any entity. Use describe() first to discover writable fields, required fields, and examples. Use context() for valid reference values. Requires the 'crm' write scope.

create

Schema discovery — fields, types, constraints, and examples for reads and writes. Pass an entity name for its full schema, or an array of names for several at once — pass every entity to get the complete schema in a single call. Calling with no arguments returns only a one-line summary per entity, not fields, so name the entities you need.

describe

Execute an OQL (OnePageCRM Query Language) query. Pass a JSON query object to read CRM data. Use describe() to discover entities and fields.

query

Report a gap or problem with this MCP server to the team that maintains it. Applies when a question cannot be expressed as an OQL query, a needed field or filter does not exist, results look wrong, or describe() and context() did not make the schema clear. Not for changing CRM data (use create() or update()) and not for account or billing support. Reports are read asynchronously; no reply comes back through this tool.

feedback

Update any entity. Only provided fields are changed. Use describe() for writable fields. Array fields (emails, phones, urls, tags) are full replacements — to add/remove a single entry, query() the current array first, modify it, then send the full list.

update