Skip to help content
All help guides

AI and MCP

Connect an AI assistant to set up your CRM

Use a scoped MCP connection to inspect settings, propose additions, and apply them after administrator approval.

What this connection can do

MCP lets a compatible assistant call defined CRM tools. The current setup connection can read this company’s lead statuses, lead sources, and appointment types, propose additions to those lists, check a proposal, and apply an approved proposal.

It cannot access contacts, payments, passwords, billing, or team permissions. It cannot delete or overwrite existing setup entries. It is a setup helper, not unrestricted account automation.

Create a scoped key

Only an active company administrator can create and manage AI connections. Open Settings → AI setup. A connection lasts 30 days and remains tied to its company and administrator.

  1. Give the connection a recognizable name for the assistant you are using.
  2. Select Create connection.
  3. Save the shown key in the assistant’s secure connection settings; it is shown only once.
  4. Hide the key after saving it.
  5. Use a separate connection for another assistant so access can be revoked independently.

Connect a compatible remote MCP client

In an assistant that supports remote MCP with bearer-token authentication, add https://app.kineticview.io/api/mcp as the server address. Put the scoped key in the secure bearer-token field, then connect. The CRM domain and endpoint must be deployed and reachable before this works.

OAuth-only assistants are not supported by this connection yet. A remote server URL alone is not an OAuth integration. If a client reports an origin error, contact the platform administrator to review its allowed origin rather than changing the key.

Alternative: a local stdio MCP client

A client that supports local stdio can launch the supplied Node.js adapter instead. The adapter is scripts/mcp-server.mjs in the Kinetic View project and requires the project dependencies.

Configure the client to launch Node with the adapter’s absolute path. Set KINETIC_VIEW_URL to the deployed CRM HTTPS origin and KINETIC_VIEW_AI_TOKEN to the one-time scoped key using secure environment storage. The default origin is https://app.kineticview.io; that origin must actually be deployed and reachable.

Do not paste the key into an ordinary chat or use a database password as the key. Both transports use the same limited tools and administrator approval workflow.

Use the review and approval workflow

The four tools are inspect_company_setup, propose_company_setup, get_setup_proposal, and apply_approved_setup. A proposal returns a review URL and does not itself change settings.

  1. Ask the assistant to inspect current setup and explain its suggestions.
  2. Describe your business and request a small set of missing stages, sources, or appointment types.
  3. Have it create a proposal, then open the review URL in the CRM.
  4. Review every proposed name and color under Setup proposals.
  5. Approve these additions only if they match your process.
  6. Ask the assistant to check approval and apply the approved proposal.
  7. Confirm the proposal is marked Applied and verify the settings lists.

Example request

“Inspect my current setup. We are a home remodeling company. Propose any missing lead stages for new inquiry, appointment set, quote follow-up, sold, and closed lost; sources for referral and website; and appointment types for estimate and follow-up. Explain additions first and wait for me to approve the proposal in the CRM before applying it.”

The current tool accepts at most 30 items per supported list. Duplicate names are skipped case-insensitively instead of overwriting existing settings. Review the existing stages before proposing new terminology.

Revoke access and troubleshoot

Use Revoke beside the connection if its key is exposed, the assistant is no longer needed, or the administrator changes. A revoked or expired connection cannot apply proposals. Approval also requires an active administrator in the same company.

Unauthorized errors usually mean an expired/revoked key or inactive administrator. A proposal conflict can mean it is unapproved, expired, or no longer authorized. Review it in the CRM rather than asking the assistant to bypass approval. Connection failures require checking the configured HTTPS origin and deployment availability.