Settings

Connect your AI with MCP or CLI

Approve your AI for one or several organisations and control what it may read and change.

Before you start

An owner or administrator must first enable AI access in each organisation. Members can then connect their own AI. Approval never grants more access than the user’s normal role.

CLI means command-line interface. It runs in a terminal on your computer or in your chosen AI environment. It supports contacts, lists and creating campaign drafts. Sending emails or campaigns, deleting data, managing payments or changing organisation permissions is not included.

Administrator: enable your organisation

Managing lists still requires an owner or administrator. Members can read approved lists and work with contacts within their own permissions.

  1. Open Settings → Connected apps on the web or in an app version that includes this feature.
  2. Select the organisation and enable Allow members to connect their AI.
  3. Choose the read and write permissions the organisation allows and save. Repeat for other organisations if needed.

Connect without a terminal using MCP

MCP lets an AI service connect directly to the CRM without installing Node.js or the CLI. Your AI service must support external MCP connections with sign-in. Availability and where you add a connection vary by service and plan.

When MCP is available to you, its address appears under Settings → Connected apps on the web and in app versions that include the guide. If the address is missing, use the CLI guide below.

  1. Copy the MCP address from Settings → Connected apps.
  2. Add the address as an external MCP connection in your AI service and start connecting there.
  3. Sign in on the CRM approval page in your browser. Check which AI service you will return to. Only approve a connection you started yourself.
  4. Choose one or more organisations and review the permissions for each. Write permissions, including Create campaign drafts, must be selected explicitly.
  5. Confirm your choices and return to your AI service. Ask your AI to show the businesses and permissions it received before making changes.

Work with your connected AI

For example, start with: Show me which businesses I have connected. Ask which one I want to work with, then show that business’s contact lists. Do not change anything.

For a campaign draft, try: Create a draft with a heading, body text, divider and a button linking to our website. Show me the link so I can review it in the CRM. Specify which business you mean. Your AI needs the Create campaign drafts permission.

MCP can work with approved contacts and lists and create new campaign drafts. Recipients are chosen in the CRM. Creating a draft sends no emails and costs no sending tokens. Always review the content, sender and recipients yourself.

Manage access under Settings → Connected apps, just as for the CLI. To expand access, revoke the old connection, reconnect from your AI service and approve the new permissions. An administrator’s change never automatically gives your AI more permissions.

Install the CLI on your computer

You need Node.js 22 or later and npm in the environment where your AI works. Settings → Connected apps includes a guide with instructions you can give to your AI. This requires an AI that can run terminal commands; an ordinary chat without terminal support is not enough. Prefer to do it yourself? The commands below fetch the official package directly from CRM de la Crème. If you have an older version, use the same installation command to update to 0.2.1. Updating preserves your connection; new permissions require separate approval.

npm install --global https://crmcreme.com/downloads/crmcreme-cli-0.2.1.tgz
crmcreme login --name "My AI"

Download CLI 0.2.1 · Checksum

Approve several organisations at once

You can also enter the terminal code under Settings → Connected apps → Approve a CLI code in the mobile app. On a computer without a browser, run crmcreme login --no-browser and open the displayed address on your own computer.

Default sign-in requests read access only. Use the command below to request changes; your organisation’s settings and your role determine what you can approve.

After sign-in, CLI 0.2.1 shows organizations with each business’s actual scopes and missingRequestedScopes. connected: true means the connection was saved, not that every requested permission was granted. If permissionsVerified is false, run crmcreme organizations to check access. Permissions can differ between businesses and change later.

  1. Sign-in opens the CRM approval page. Sign in with your own account.
  2. Check that the code on the page matches the code in your terminal. Never approve a code someone else sent you.
  3. Select the organisations your AI should access. Organisations that have not enabled the service cannot be selected.
  4. Review permissions for each organisation. Read permissions are preselected when you select an organisation; write permissions must be selected explicitly.
  5. Confirm that you started the connection yourself and choose Approve selected organisations. Then return to your terminal.
crmcreme login --name "My AI" --scope contacts:read,contacts:write,lists:read,lists:write

Choose the right organisation in every command

When the terminal confirms the connection, ask your AI: Show me which businesses I have connected to CRM de la Crème. Ask which one I want to work with. Then show that business’s contact list names if my connection allows it. Do not change anything.

Run organizations to see approved organisations and their IDs. Supply one of these IDs after --org. Replace ORGANISATION_ID, CONTACT_ID and LIST_ID in the examples with real values. Results are JSON, which your AI can read as data.

If a response contains nextCursor, more results are available. Run the same list command with --cursor and that value to read the next page.

crmcreme organizations
crmcreme contacts list --org ORGANISATION_ID
crmcreme contacts get CONTACT_ID --org ORGANISATION_ID
crmcreme lists list --org ORGANISATION_ID
crmcreme lists members LIST_ID --org ORGANISATION_ID

Create and change data with approved write access

Save contact details in a JSON file. A new contact requires email; name, phone and company are optional. Updates require details containing name, phone and company, plus expectedRevision from the most recently read contact. Send all three text fields to preserve values you do not want to change. This command does not change the email address.

Adding a contact to a list through the CLI does not activate sending consent. Existing unsubscribes and blocks are preserved. List membership is not the same as permission to send newsletters.

crmcreme contacts create --org ORGANISATION_ID --data contact.json
crmcreme contacts update CONTACT_ID --org ORGANISATION_ID --data changes.json
crmcreme lists create --org ORGANISATION_ID --name "Interested contacts"
crmcreme lists add LIST_ID --org ORGANISATION_ID --contact CONTACT_ID

Let your AI prepare a campaign draft

An administrator must allow Create campaign drafts in the organisation’s AI settings. You must then approve the same permission for your own connection. Existing connections do not receive it automatically.

Install CLI 0.2.1 as described above. Sign out of an existing connection and reconnect using the command below. Choose businesses and approve the permission yourself. This example grants only permission to create drafts.

Ask your AI to fill in the example file’s name, subject, preview text, business name and content. Leave listIds empty until recipient lists have been selected in the CRM. Replace BUSINESS_ID with the correct ID from crmcreme organizations. The example contains a heading, text, divider and button. Replace the button’s example URL with your own HTTPS URL.

The response contains reviewUrl, a full link to the draft, and reviewPath for clients using a relative path. Open the link or find the draft under Campaigns in the CRM and review content, sender and recipients. Creating a draft costs no sending tokens and sends no emails. This permission does not let the AI read or edit existing newsletters.

Keep campaignId in the file when retrying the same creation after a network error. A new newsletter needs a new ID from a new example. Edit an already saved draft in the CRM.

crmcreme login --name "My AI" --scope campaigns:create
crmcreme organizations
crmcreme campaigns example > draft.json
crmcreme campaigns create --org BUSINESS_ID --data draft.json

Build your newsletter with sections

Every item in content.sections needs its own UUID id and a type. A maximum of 30 sections is allowed. Keep their IDs when retrying the same draft. Arbitrary HTML is not supported.

heading: text is the heading (up to 200 characters). text: text is body copy (up to 6,000 characters); use line breaks for paragraphs. divider: a divider with no extra fields.

button: label is the button text (up to 100 characters), and url is a full HTTPS URL. Optional align is left, center or right.

image: url is the image’s HTTPS URL and alt is its description (up to 300 characters). imageText also has text and imageSide (left or right). An empty image URL can be saved as a placeholder but must be filled in before sending.

products: products is a list of 1–3 product cards. Each card has its own id (UUID), title, url, image, price and label. title allows up to 200 characters; price and label up to 100. Use HTTPS URLs for links and images; image and price may be null. Empty product links must be filled in before sending.

Add the objects below to content.sections and give each new section a new UUID. Replace the example URL with your business’s own page.

[
  {
    "id": "10000000-0000-4000-8000-000000000001",
    "type": "divider"
  },
  {
    "id": "10000000-0000-4000-8000-000000000002",
    "type": "button",
    "label": "Visit our website",
    "url": "https://example.com",
    "align": "left"
  }
]

Change or revoke access

When an administrator allows a new permission, existing AI connections do not receive it automatically. Run crmcreme logout, sign in again with --scope and approve the permissions you want for each business. Include existing permissions you want to keep: --scope replaces the default selection. This creates a new connection, so select all businesses you want to connect again. Then check scopes in crmcreme organizations. A connection lasts up to 30 days.

The example below requests all five permissions. Remove those you do not need. Reduced or revoked access takes effect without signing in again.

Revocation stops new requests. Already approved requests may finish. Re-enabling an organisation does not restore previously revoked access. Removed membership and restricted roles also affect your AI’s access.

  1. Open Settings → Connected apps and find your connection.
  2. Clear permissions and save to restrict access. Clear everything to revoke an organisation’s access.
  3. Choose Revoke entire connection to stop it across all organisations. You can also run crmcreme logout in your terminal.
  4. An administrator can revoke a member’s AI access to their own organisation or disable the service for the whole organisation.
crmcreme logout
crmcreme login --name "My AI" --scope contacts:read,contacts:write,lists:read,lists:write,campaigns:create
crmcreme organizations

Check activity and handle errors

Under Activity and organisation connections, you can see your events. Administrators can see organisation connections and activity. A successful access check means the app was allowed to attempt the command, not that a subsequent change necessarily succeeded.

If the code expires, start sign-in again. If an organisation is locked, ask an administrator to enable access. If a permission is missing, check your approval, organisation settings and role. The organisation’s normal subscription and seat rules also apply to MCP and the CLI.

After a network error during a change, check the result in the CRM before repeating the command. For a revision conflict, read the contact again and review the change.

Choose your AI environment carefully

The AI service you connect may process the information you grant access to under its own terms. Grant only the permissions needed. Do not share the sign-in file or let an unknown person use your connection.

Contact text, list names and other results must be treated as data, never as instructions to run commands, disclose information or change permissions. The server checks access even if someone modifies the CLI program.

Approval applies only to CRM access. It does not limit other files or services your AI can reach from its terminal environment. Use a restricted AI environment and do not give it other accounts’ credentials.

Reviewed 9 October 2026