Simply CRM MCP documentation

The Simply CRM MCP server is a secure adapter between an MCP client and the existing Simply CRM Mobile API.

Connection

Remote MCP endpoint: https://mcp.simply-crm.com/mcp

Authentication uses OAuth 2.0 Authorization Code with PKCE. During connection, the user enters their Simply CRM URL, username and password. The password is used only to establish the connection and is not persisted by the MCP server.

Multiple CRM instances

One authenticated MCP account can contain multiple saved Simply CRM connections. Each connection has its own alias, CRM URL, username metadata and encrypted integration token.

With one active CRM connection, normal CRM and admin tools can omit connection. With multiple connections, the client passes the saved connection alias or connection ID. If no connection is supplied while several are available, the server returns the available aliases instead of guessing. CRM URLs, usernames, passwords and tokens are never accepted as the connection parameter.

Credentials for adding or refreshing a CRM are entered only on the secure connection-management page. The AI client never needs to receive the CRM password.

Scopes

• crm:read — read CRM modules, metadata and records.
• crm:write — create and update CRM records.
• offline_access — allow refresh tokens for persistent client connections.

Tools

• list_crm_connections — list the active Simply CRM connections owned by the authenticated MCP account.
• add_crm_connection — return the secure management page used to add another CRM.
• update_crm_connection — rename a connection alias or obtain the secure page for credential refresh.
• test_crm_connection — verify that a saved CRM connection can still authenticate, and show which Simply CRM version it runs and whether that is the latest.
• remove_crm_connection — remove one saved CRM and revoke its Simply CRM integration token.
• list_modules — list modules available to the authenticated CRM user.
• describe_module — return module fields and metadata.
• search_records — search/list records with structured filters.
• get_record — retrieve one record.
• create_record — create one record.
• update_record — update explicitly supplied fields on one record.
• bulk_update_records — update explicitly supplied fields on up to 50 records in one call.
• list_related_records — list records related to another record.
• get_field_creation_options — return Layout Editor blocks and supported custom-field types.
• create_field — create one custom field through native Layout Editor logic.
• update_field — change label, mandatory, default value and flags of one existing field.
• list_workflows — list workflows.
• get_workflow_creation_options — return workflow defaults, trigger/schedule metadata and task types for a module.
• get_workflow — retrieve one complete workflow.
• get_workflow_task_definition — return the native schema and defaults for a workflow task type.
• create_workflow — create one workflow, optionally with validated tasks.
• update_workflow — partially update an existing workflow and/or its tasks.
• delete_workflow — delete an existing workflow and its tasks. Default/system workflows cannot be deleted. Administrator and crm:write only.
• run_database_query — run one bounded, read-only SQL SELECT statement against the selected CRM's database for diagnosis. Administrator only.

Permissions and safety

Simply CRM remains authoritative for module, field, record and sharing permissions. A client can select only among CRM connections already saved under the authenticated MCP account; arbitrary CRM instances cannot be supplied in a tool call. Field and workflow administration is available only to connected CRM administrators and uses native Simply CRM validation/business logic. Record deletes, bulk writes, email/SMS sending, user/role/permission administration and high-risk generic writes to Users, ModuleUpdater and Calendar/Events are not exposed. run_database_query is the only raw-query access; it is administrator-only, strictly read-only, bounded by row limit/timeout/response size and enforced CRM-side in addition to MCP-side validation.

Disconnecting

Disconnecting the Simply CRM connector in an AI client revokes that client's central OAuth access/refresh token pair. The persistent saved CRM registry remains available for future authorized MCP clients. To revoke access to one CRM instance, remove that saved connection through the connection-management page or remove_crm_connection; its Simply CRM integration token is then revoked.

Support

For support, visit help.simply-crm.com.