Connect Claude to Salesforce.

A hosted MCP endpoint with OAuth login and a diagnostic prompt built for enterprise SaaS teams.

Connect Claude Use prompt
Connector layer

One connector. One org login. One diagnostic prompt.

Nexus hosts the connector surface. The same operator can turn Claude's first read into Salesforce delivery after the diagnostic.

CLIENT Claude
MCP Nexus
ORG Salesforce
https://mcp.nexus-agency.net/mcp Paste this

Add the connector in Claude.

Use the highlighted MCP URL as the custom connector endpoint. Claude registers through OAuth Dynamic Client Registration, then Nexus opens the Salesforce login flow for the org you choose.

MCP URL
https://mcp.nexus-agency.net/mcp
  1. 01

    Add custom connector

    In Claude, open Settings, then Connectors or Integrations, then add a custom connector with https://mcp.nexus-agency.net/mcp.

  2. 02

    Approve Nexus

    Claude discovers the OAuth metadata and opens the Nexus approval screen. Approve it to create the isolated MCP session.

  3. 03

    Connect Salesforce

    Ask Claude to start the interactive Salesforce login, then authorize the production or sandbox org you want inspected.

  4. 04

    Run the diagnostic

    Use the prompt below once the org connection is active. The result is a diagnostic starting point, not a delivery plan.

Prompt for Claude Nexus MCP 
Use the Nexus MCP connector at https://mcp.nexus-agency.net/mcp. If it is not connected yet, guide me through adding it as a Claude custom connector first.

Connect my Salesforce org with Nexus. Use the interactive login flow and alias it production.

Then run a Salesforce health diagnostic. Focus on data quality, automation risk, security, adoption signals, and the first fixes an enterprise SaaS team should queue. Return the report in markdown.

Diagnostic output

What the diagnostic returns.

This section is reserved for captured Claude output. Until that response is available, it documents the report structure only, with no fabricated org findings.

Captured Claude output slot Pending real response
Report shape

Salesforce health diagnostic

Real Claude output will replace this placeholder when captured. This page will not invent org findings.

  • 01Risk summary

    Org-level readout from Claude.

  • 02Friction areas

    Evidence-backed hotspots.

  • 03First fixes

    Work queue candidates.

  • 04Open questions

    Human review points.

Connector troubleshooting.

Operational answers for getting Claude unstuck. For retainer, pricing, and delivery scope, use the main agency page.

Cache reset

How do I reset Claude's MCP cache?

  1. Remove connector

    Open Claude Settings, then Connectors or Integrations, and remove Nexus.

  2. Start fresh chat

    Add https://mcp.nexus-agency.net/mcp again from a new Claude message.

  3. Approve OAuth

    Approve Nexus again so Claude creates a clean remote MCP session.

  4. Rerun prompt

    Run the Salesforce connection prompt before asking for the diagnostic.

If stale tools still appear, sign out and back in. For Claude Desktop, restart the app after removing the connector.

Do I need a Nexus account first?

No. Claude registers through OAuth Dynamic Client Registration. Nexus asks for Salesforce authorization only when you start the org connection.

What should I do if the audit says no org is connected?

Run the connection prompt again and confirm the Salesforce login completed in the browser. Then start a fresh Claude message before asking for the diagnostic.

Turn findings into work.

Use Nexus MCP to get the first read. Use Nexus Agency when the org needs engineering-backed Salesforce delivery from the same operator perspective.

Connect Claude Go to Nexus Agency

Same owner from first read through delivery. No rotating bench, no context handoff.

  • Operator perspective
  • Engineering-backed delivery
  • Async queue for enterprise SaaS teams