metadata
Salesforce metadata analysis
Search and explain schema, fields, Flows, Apex, permissions, integrations, and OmniStudio from a local org vault.
Use cases
The operational problems Salesforce teams actually search for - each one an intent-matched page that answers the question and shows the sf-intelligence tools that solve it. Offline, read-only, grounded in your real metadata.
dependencies
Salesforce dependency analysis
Trace what depends on a field, object, Flow, Apex class, permission set, or package before you change it.
impact
Impact analysis
What breaks if you delete a field, object, Flow, or Apex class? Dependency tracing with confidence tiers.
where-used
Where is a field used?
Find every place a Salesforce field is referenced - Flows, Apex, layouts, reports, validation rules - from the dependency graph plus a source grep.
safe-delete
What breaks if you delete a field?
Simulate a delete before you make it. See every dependent component, with honest coverage caveats on what static analysis can miss.
explain
Explain a Salesforce flow
Ask what a specific Flow actually does in plain English - its trigger, decisions, and the components it touches.
access
Sharing & visibility
Why can't a user see a record? Who can edit a field? Trace Profiles, Permission Sets, and the sharing cascade.
agents
Claude Salesforce MCP
Register a read-only Salesforce MCP server in Claude Code, Claude Desktop, Cursor, Codex, or any MCP client.
safety
Is AI safe on my org?
Offline, read-only, fail-closed - why a local metadata vault is the low-risk way to point an AI agent at Salesforce. No writes, no data egress.
Compare
How sf-intelligence stacks up against the official Salesforce MCP server and the paid cloud platforms.