Use REDA AI with MCP

A connected AI assistant can ask your REDA AI agents to work with the Salesforce data and procedures your organisation has configured. Start with an agent your administrator has enabled for MCP. You still need your own Salesforce identity and access to the relevant records.

Connect your account

Getting there: open the AI assistant's Connectors area. Access: your administrator must enable the connection and assign both REDA AI User and REDA AI MCP User in Salesforce. Ask for your organisation's connector URL and OAuth client ID; do not ask for another user's password or token.

For Claude, a Team or Enterprise owner first adds the organisation's custom web connector. Each user then connects it and signs in to Salesforce individually. Individual accounts add the custom connector themselves. Use the supplied Consumer Key as the OAuth client ID, leave the secret blank, and use the manual client option if the interface offers automatic registration. Enable the connector in the conversation. See Claude's current connector instructions for navigation.

Ask for the business outcome

Name the agent and the work: “Ask the service desk assistant to summarise my open cases and suggest which need follow-up.” If the agent needs a record, provide the record link or identify it clearly. Review the answer against the records and context it used. Available actions depend on your configured agent; the connection does not grant a general right to every Salesforce operation.

Review proposed actions

1. Read the proposed record changes, recipients, dates and action sequence.
2. Correct anything inaccurate before approving. Decline a proposal you do not want performed.
3. When approving a REDA action, instruct the host to execute it through the REDA AI connector in Salesforce. If the host also has an email or calendar connector, do not ask it to carry out the same action there.
4. Check the returned result. If the connection times out, inspect the Salesforce record or ask your administrator to check the outcome before resubmitting; a missing reply is not proof that nothing happened.

Continue and check your work

Matching conversations can resume within the agent's conversation window. A blank window initially uses 30 minutes; your administrator can change it or disable automatic resume. Salesforce conversation messages include a Via MCP indicator for MCP interaction. Use REDA AI → AI Conversations to review the available history; the host also has its own chat history. Do not treat either view as proof that every external action has a separate receipt.

For a scheduled action, verify the time and intended record. Delayed processing uses the user who registered the Salesforce scheduled job, not automatic impersonation of the person who requested it. Ask your administrator to resolve a “processor unavailable” error before scheduling again.

When you need help

If the agent is missing, reconnect to refresh the catalogue and ask the administrator to check eligibility and access. If a record is unavailable, request the proper business access through your normal process. Share the time, agent name and error message with support, avoiding unnecessary sensitive content. Your conversation data may be processed by the AI host and configured providers as well as Salesforce; follow your organisation's data policy.