Skip to main content
ApexGenius MCP puts your Salesforce org inside the AI tools you already use: Claude, ChatGPT, VS Code, and Cursor. This page explains what actually happens on a request, because if you work with real CRM data you should know.

​
The request path

  1. You ask something in your AI client (“show me stuck opportunities above the amount I specify”).
  2. The client calls an ApexGenius MCP tool over an authenticated connection.
  3. ApexGenius calls Salesforce using the credential assigned to the active user and project context.
  4. The result passes back through to your AI client, which writes the answer.
Two properties of that path matter more than anything else:

​
Your permissions are the ceiling

Salesforce profiles, permission sets, object permissions, and field-level security apply to the credential used for the request. ApexGenius does not bypass the access Salesforce grants to that credential. Current projects can use per-user Salesforce authorization where it is enabled. Some legacy projects can still use a shared project-level connection. Check the connection mode in the selected Salesforce project before assuming the request uses your personal Salesforce token.

​
What the gateway processes and stores

ApexGenius processes the request and tool result needed to complete each call. It also stores operational application data needed to provide and secure the route, including encrypted authorization references, project configuration, metadata staging you create, usage events, and content-minimized audit entries.
  • Usage events: may include the tool name, duration, and outcome.
  • Write audit log: supported record changes and deploys record who initiated the operation, the affected system and action, and the outcome. The gateway Activity view does not render raw query text, field values, or record IDs.
Your AI vendor processes the conversation under your agreement with that provider. The MCP route returns tool results to the AI client you authorized. The separate request-only ApexGenius workspace has a different data path and should be evaluated separately. Do not use ApexGenius for PHI or another regulated-data workflow unless the required agreements and controls are confirmed in writing.
Write confirmation depends on the client.Write tools are labeled so compatible AI clients can apply their confirmation controls. ApexGenius records supported provider writes, but it does not yet enforce a universal Auto, Ask, or Off approval mode at the gateway.

​
Authentication

The hosted gateway uses browser-based OAuth authorization tied to your ApexGenius account:
  • Claude and ChatGPT: add the hosted connector or app, sign in to ApexGenius, and approve.
  • Cursor, VS Code, Codex, and compatible clients: add the streamable HTTP server URL and complete the same browser sign-in.
Account access is gated. Sign in to the ApexGenius workspace and open Settings → Billing to confirm the current state and any account-specific terms. When an account is not entitled to an operation, the tool returns an access response instead of performing the request.

Set up the connection

Connect Claude, ChatGPT, Codex, VS Code, Cursor, or another compatible client.

Every MCP tool

The full reference: queries, records, metadata, staged files, and deployments.
Last modified on August 28, 2026