Skip to main content

How to Connect an AI Assistant (MCP)

With the aprity MCP server, an AI assistant that supports the Model Context Protocol — ChatGPT, Claude, Cursor, GitHub Copilot… — can answer questions about your Salesforce org from your aprity documentation. You sign in with your own Salesforce login; there is no token to paste.

Prerequisites​

  • Intelligence plan (2,000 tool calls per month) or Trial (25 tool calls for the whole trial). The MCP server is not included on Documentation.

  • At least one published documentation version.

  • Your Salesforce administrator has prepared the Connected App used by aprity:

    • the aprity MCP callback URL is in its callback URLs (the aprity setup wizard lists it with the other callback URLs);
    • your profile or permission set is among the pre-authorized users.

    See Connected App Setup.

Step 1 — Get your MCP URL​

The URL is specific to your organization. Copy it rather than typing it.

  1. In the aprity portal, open the account menu (your avatar, top right) and click Connectors. This page is reserved for aprity administrators of your organization; if you do not see it, ask one of them for the URL.
  2. On the AI assistants · MCP card, click Copy URL.
  3. For clients configured through a JSON file, expand Client configuration and click Copy configuration.

The URL is not a secret: it carries no credential.

Step 2 — Add aprity to your AI assistant​

Add a remote MCP server in your client and paste the URL (or the configuration). The exact place differs per client:

Step 3 — Sign in​

  1. The first time the client connects (or the first time it calls aprity), it opens a browser window on your Salesforce login page.
  2. Sign in with your Salesforce credentials, on the org documented by aprity.
  3. Accept the authorization prompt.

The aprity tools then appear in your client. They answer from the latest published version of your documentation.

Disconnect​

Remove the aprity server from your AI client. Your Salesforce administrator can also cut access for everyone by disabling the Connected App.

On the Connectors page, Legacy access tokens lists tokens created before sign-in with Salesforce was available. Once every client uses the URL above, click Revoke on each of them.

Troubleshooting​

  • The client says access is refused after sign-in: check that your plan includes the MCP server and that you signed in to the right Salesforce org.
  • Salesforce refuses the sign-in: your profile is probably not pre-authorized on the Connected App. Ask your administrator.
  • Answers are out of date: the assistant reads the latest published version. Run a new analysis after significant changes.

See also MCP authentication failed and the Remote MCP Server guide.