Inspect Salesforce actions
Find the Salesforce modules available in your workspace, inspect their required fields and identify the connection each action will use.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Plan a Salesforce reporting replica”
Stacksync MCP · CRM
Use Stacksync MCP to inspect Salesforce connections and available actions, plan syncs with a database or CRM, and investigate sync issues from your AI assistant. Salesforce object access and each operation still depend on your connected account.
01 / The connection
Use Stacksync MCP to inspect Salesforce connections and available actions, plan syncs with a database or CRM, and investigate sync issues from your AI assistant. Salesforce object access and each operation still depend on your connected account. Choose an AI client below to get started with the Stacksync MCP server.
The server belongs to Stacksync. The available Salesforce operations depend on your connection, permissions, and connector modules.
Explore the Salesforce connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Find the Salesforce modules available in your workspace, inspect their required fields and identify the connection each action will use.
Read the exposed object and field names, choose record matching and table direction, then prepare the sync configuration for review.
Inspect sync health and grouped record errors before choosing whether a retry, revert or ignore is appropriate.
03 / Setup
Connect the MCP server first. Then connect Salesforce using the requirements below.
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcp Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcp Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{
"mcpServers": {
"stacksync": {
"url": "https://mcp.stacksync.com/mcp"
}
}
} Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}' Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{
"mcpServers": {
"stacksync": {
"serverUrl": "https://mcp.stacksync.com/mcp"
}
}
} Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Salesforce connection and capabilities.
04 / Put it to work
Example prompts for Salesforce. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
Inspect my Salesforce and PostgreSQL connections and any existing sync between them. Discover the available Salesforce objects and PostgreSQL tables. Propose a one-way Salesforce-to-PostgreSQL sync for the account and opportunity data I select, including record IDs, initial-copy scope and destination permissions. Ask me to confirm the object mappings before saving or starting anything.
A proposed reporting sync with explicit objects, matching keys and initial-copy scope.
Find my Salesforce syncs and read their current issues. Group failures by cause and show the affected mappings and record IDs. Propose the smallest correction and explain when retry, revert or ignore would be appropriate. Do not resolve issues or change a mapping until I choose the action.
A diagnosis tied to actual sync issues and a reviewable recovery plan.
Inspect the Salesforce connector actions and my connection. If an account lookup action is available, show its required inputs and propose a lookup for the account identifier I provide. If it is unavailable, explain the missing capability. Prepare any follow-up record update as a separate proposal with the record ID and field changes; do not run it yet.
A verified action choice and an explicit proposal for one Salesforce account.
05 / Before you run
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗06 / Common questions
No. The assistant uses your Stacksync role, the Salesforce connection’s access and the available connector modules. Sync support also varies by object; inspect the live schema before promising access to a custom object.
Yes, the documented Stacksync Salesforce and PostgreSQL sync path supports this architecture. Choose direction and field mapping deliberately. Reading sync configuration is different from querying the copied records.
These prompts request inspection and a proposal before changes. The server’s separate Ask before every change setting can enforce confirmation for changes; it is off by default.
Reviewed · Product documentation and connector references
Keep building