Remote MCP Server (AI clients)

The Remote MCP Server lets you connect MCP-compatible AI clients -- ChatGPT, Claude Desktop, Claude.ai, Claude Code, Cursor, and other MCP-compatible clients -- directly to your aprity-scanned Salesforce org. Once connected, the AI client can answer questions about your org, look up object behaviour, and draft user stories grounded in your latest scan.

The server is an OAuth 2.1 endpoint at https://mcp.aprity.ai/v1/mcp. You point your AI client at that URL; the client walks you through an OAuth 2.1 + PKCE sign-in that authenticates you with Salesforce SSO. After you approve, the client holds a short-lived token and can call the aprity knowledge tools on your behalf.

What you can do once connected

The AI client gets access to three tools backed by your most recent successful scan:

Tool	What the AI client can ask aprity to do
Answer a question	Open-ended questions in plain language: "What does the OpportunityService class do?", "Why is the Account trigger failing on update?", "Summarize how we integrate with our e-signature provider." The orchestrator queries the deterministic knowledge tools and returns synthesized prose with citations to the source metadata.
Describe object behaviour	Deterministic lookup: "What happens when a Case is updated?" Returns the list of triggers, flows, validation rules and ownership outcome. No LLM cost, sub-second response.
Draft a user story	Generate a structured Salesforce user story (Given / When / Then) from a free-text intent. Multi-turn refinement is supported.

The tools are the same deterministic knowledge tools that power the Help Agent and Story Agent (object dossiers, fields, execution order, access/permissions, ownership, dependencies, impact analysis, integrations). The AI client never sees raw Salesforce data live -- it sees the facts aprity captured during the last scan. Run a fresh scan when your org has changed.

Plan availability

The Remote MCP Server is available on Intelligence and Trial plans. It is not included on Documentation.

Plan	Monthly tool-call quota
Documentation	Not included
Trial	500 tool calls per month
Intelligence	5,000 tool calls per month

A tool call is one request the AI client makes to aprity. Asking a single question typically consumes one call ; multi-turn refinement of a user story consumes one call per turn. Quotas reset on the first day of each calendar month and unused quota does not roll over.

See Plan Comparison for the full feature matrix.

Connect an AI client

You connect an AI client by adding aprity as a remote MCP server and pointing it at the aprity endpoint. The client then runs the OAuth sign-in for you.

1. In your AI client's MCP / connector settings, add a new remote MCP server with the URL:

   https://mcp.aprity.ai/v1/mcp

2. The client opens a browser window for the OAuth 2.1 + PKCE flow.

3. Sign in with Salesforce SSO -- the same credentials you use for your aprity-scanned org. aprity resolves your tenant from your Salesforce org.

4. Approve the connection. The client receives a short-lived token automatically; there is nothing to copy or paste by hand.

5. Once connected, the aprity tools appear in your AI client and draw on your latest successful scan.

note

The exact place to add a remote MCP server differs per client. Some clients (e.g. ChatGPT, Claude.ai) accept the URL directly; others (e.g. Claude Code, Cursor) add it through their MCP configuration. In all cases the OAuth sign-in is the same.

Pick the per-client setup guide that matches your tool:

• ChatGPT Desktop
• Claude.ai (web)
• Claude Desktop
• Claude Code (CLI)
• Cursor

Disconnect a client

Disconnect aprity from within the AI client (remove the connector / MCP server entry), or revoke the connection at the OAuth provider. Once disconnected, the client's token can no longer call aprity and the next request returns 401.

Disconnect a client when:

• The device or AI client that held the connection is decommissioned.
• The connection is no longer needed.
• The Salesforce user who authorized the connection leaves the company.

Limitations

• The AI client only sees the metadata captured during your last successful scan. Recent org changes are visible after the next scan completes.
• Each connection is tied to the Salesforce user who authorized it via SSO. Authorize from each client you want connected.
• Tool-call quotas are per tenant, shared across all AI clients connected for that tenant. If your team has multiple clients connected, they draw from the same monthly pool.
• AI clients must support remote MCP over HTTP with OAuth. Clients that cannot run the OAuth sign-in won't work -- see the per-client guides.

Privacy and security

• Authentication uses OAuth 2.1 + PKCE with Salesforce SSO. The token your client receives is short-lived and scoped to your tenant -- it cannot read data from any other aprity customer's org.
• aprity resolves your tenant from your Salesforce org during sign-in; you authenticate with the same Salesforce identity you use for the scanned org.
• Every tool call is logged with your tenant context for audit. Token values are never logged. Tool inputs are PII-scrubbed before persistence.

See the Security Model for the full aprity authentication and data-handling posture.

Headless and CI use cases

The Remote MCP Server is designed for interactive AI clients on developer workstations that can run the OAuth sign-in. For headless or CI scenarios where a browser-based OAuth flow is impractical, aprity ships a stdio-transport shim (aprity-mcp) for internal aprity engineering and CI smoke tests. It is not the recommended customer-facing path and is not documented in the help center -- contact your aprity contact if you have a use case that the Remote MCP Server cannot cover.

Troubleshooting

Symptom	Where to start
AI client returns 401 Unauthorized	MCP authentication failed
The OAuth sign-in fails or loops	Confirm your plan includes the Remote MCP Server and that you sign in with the correct Salesforce identity for your aprity-scanned org. See MCP authentication failed.
Answers feel out of date	Run a new scan -- the AI client only sees the last successful scan
Tools do not appear after connecting	Re-run the OAuth sign-in from the client, and verify your plan includes the Remote MCP Server.

For anything else, contact support@aprity.ai.