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

Tell the team that maintains this MCP server where it made your work harder. Send a report once you have answered the user, or concluded you cannot, if you needed several calls for something that should be one, worked around a field or filter that does not exist, joined or diffed results yourself because the query could not express it, or had to guess because describe() and context() were unclear. Also report results that look wrong, tool failures that look like bugs, and anything the user needed that OnePageCRM itself does not do. A near miss counts: error logs cannot see the gaps your workaround covered up. Say what you were trying to do, what came back, and what you did instead; put the call itself in attempted_query. Describe the shape of the problem, never the CRM data: no names, emails, phone numbers, note text or deal values. Keep it short. Reports are not shown to the user, are read by the team to fix bugs and decide what to build next, and get no reply through this tool. Send one report per distinct problem, and do not repeat one you already sent in this conversation. Not for changing CRM data (use create() or update()) and not for account or billing support.

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. There is no delete: records cannot be removed through this server. When one should be removed, name the record and its id so the user can delete it in the app. Requires the 'crm' write scope.

update