Salesforce metadata analysis

sf-intelligence gives AI agents a read-only way to analyze Salesforce metadata: schema, fields, Flows, Apex, permission models, integrations, OmniStudio, and generated documentation from one local org vault.

What metadata analysis means here

Most Salesforce search tools stop at file search or raw metadata retrieval. sf-intelligence builds a queryable knowledge base from the retrieved org metadata, then exposes that knowledge through a Salesforce MCP server. The result is plain-language metadata analysis that stays grounded in the org you actually indexed.

Questions this page targets

  • "What fields exist on Account, and which are custom?"
  • "Which Flows update this field?"
  • "What Apex classes reference this object?"
  • "Which permission sets grant access to this field?"
  • "Generate a data dictionary for this Salesforce org."
  • "Explain this org to a new admin or developer."

Metadata families covered

AreaExamples
SchemaObjects, fields, record types, picklists, layouts, tabs
AutomationFlows, workflow, approval processes, assignment and escalation rules
CodeApex classes, triggers, call graph, test coverage signals
SecurityProfiles, permission sets, field-level security, object access, sharing metadata
IntegrationsNamed credentials, remote sites, endpoints, outbound messages, platform events
DocumentationData dictionary, admin handbook, architecture overview, onboarding docs

Why AI agents need a metadata layer

A general model can explain Salesforce concepts, but it cannot know your org's custom fields, naming conventions, automations, package boundaries, and security model unless those facts are supplied. sf-intelligence supplies those facts as structured, read-only tools, so Claude, Cursor, Codex, or another MCP client can answer from the vault instead of guessing.

Related searches

For blast-radius work, see Salesforce dependency analysis. For client setup, see Claude Salesforce MCP setup. For the complete tool surface, browse all 176 Salesforce MCP tools.

Analyze your org metadata locally.

Install once, run a read-only refresh, then ask metadata questions in plain language.