Skip to content

Start here

Use the Engage MCP connector

5 minute read

Reviewed October 4, 2026

Short answer

Short answer

The Engage MCP connector gives a compatible client access to your authenticated workspace. Use public help to learn the product, and tenant read tools to inspect your business knowledge. Where enabled for your administrator account, separate guarded tools can save knowledge and refresh retrieval. A proposed answer, saved file, refreshed index, and tested customer response are different results.

Before you start

  • An Engage account with access to the intended workspace
  • A compatible MCP client connected to https://api.ajai.pro/mcp
  • The required workspace role and enabled tools for any requested changes

Connect to the right workspace

Open workspace agent settings at https://app.ajai.pro/dashboard/settings/agents and use the connector endpoint https://api.ajai.pro/mcp in your compatible client. Sign in through the provided authorization flow. Setup and availability depend on your client and account.

Ask the connector to inspect the current configuration before requesting changes. Workspace selection and authorization come from the authenticated connection, not a company name typed in a prompt.

Keep product help and business facts separate

The public Help center teaches you to use Engage. The MCP get_engage_help tool provides connector-specific coaching and links to these web guides. Newer iPhone builds read the same public guide catalog as this website.

Your business knowledge is private workspace content: hours, services, policies, appointment instructions, and the questions your front desk repeats. The website editor, iPhone library, and MCP knowledge tools access the same business files. Help articles are not copies of those files.

Read, save, refresh, then verify

Start by asking the connector to read the relevant knowledge file. Explain the customer question you want it to answer and review the proposed wording. A suggestion alone does not change the file.

  1. 01For an authorized save, the connector uses the current checksum and an operation ID. If another surface edited the file, re-read it and resolve the conflict.
  2. 02After saving, explicitly request a knowledge-index refresh if that tool is enabled. Saving alone does not apply the new content to retrieval.
  3. 03Check the reported refresh result. A failed refresh can leave completed source updates in place; it does not guarantee rollback of the whole index.
  4. 04Test the affected question in each configured customer-facing channel. The connector cannot run those test conversations for you.

Know what each control changes

Business facts belong in knowledge. Tone, handoff behavior, and delivery preferences belong in the prompt profile and channel overrides. A channel override does not prove that a channel is connected.

Shared knowledge changes may affect multiple configured channels. Test website chat, voice, and other affected experiences separately; do not assume identical retrieval behavior or that an active call has updated.

MCP writes are available only in the controlled administrator rollout. Read-only access does not grant write access, and a visible tool can still reject an unauthorized action. The website and iPhone offer different management actions under their own workspace permissions.

Availability and limits

What to keep in mind

  • The connector cannot publish website changes, send customer messages, or run assistant test conversations.
  • MCP knowledge tools cannot move, import, or delete files. Use the available workspace tools for those operations.
  • A successful knowledge refresh is not evidence of a tested answer, a connected channel, or a changed live call.

Keep going

View all guides

Need a specific answer?

Review your Engage flow with AJAI.

Book a Review

Already using Engage? Contact support or review the Privacy Policy.