The Salesforce MCP

Role-scoped by design

Every MCP key carries a role, and every one of the 56 tools requires exactly one permission. Roles are bundles of permissions, so a higher role includes everything a lower one can do, and tier gating layers on top: effective access is the minimum of your role and your plan.

• Read-only — 15 tools: setup status, list sandboxes and their status, browse and describe metadata, org summary, search, sync logs, deploy tags, policy and dependency checks, verify a deploy, and the guidance playbooks.
• Contributor — +34, 49 of the 56: live record reads and org intelligence (governed SOQL, record get, bulk query jobs, org compare, drift, deploy preview, usage and data-quality reports, saved analyses); branches, proposed fields, validation rules and metadata, pull requests and saved reports; merge, validate, rollback and test coverage; sync; playbook scripts.
• Admin and Owner — +7, all 56: connect a Salesforce org or the GitHub App, bind a mirror repository, and write records in bulk from uploaded CSV files (insert, update or upsert; there is no delete tool). Their other permissions (members, roles, MCP keys, billing, notifications) gate the workspace, not the tools.

A key's scope can narrow any of this, never widen it. Live record reads are logged per call (who, which tool, which object, and the outcome) and bulk record writes per batch, in both cases without record contents.

What your AI asks before it runs

Every tool tells the client whether it only reads or whether it changes something. 34 of the 56 tools are marked read-only: they create and change nothing in Salesforce, in GitHub or in your FlowSprite workspace. The other 22 are marked as changing something, so a client such as Claude asks you before each call. That covers committing metadata to a branch, opening or merging a pull request, starting a sync, a validation, a rollback or a bulk job, and connecting an org or a repository.

Three things to try once you are connected:

• "What is still left to set up in my FlowSprite workspace?"
• "Which custom fields on Account are less than 5% populated in my sandbox?"
• "Add a picklist field Renewal Risk to Opportunity and open a pull request for it."

Help and privacy

Questions about connecting an AI client, or a tool that does not behave the way this page says: hello@flowsprite.com. Security reports go to security@flowsprite.com. What FlowSprite stores and why is in the privacy policy and the terms of use.

Keys you control

Generate a personal MCP key from the FlowSprite portal or admin dashboard. Scope it to specific sandboxes or leave it org-wide. Keys revoke instantly, rotate without downtime, and can carry an expiry. Every key is role-scoped and tier-gated, and every metadata change arrives as a pull request you review before anything deploys.