15 minTime to key
NoNo-human path
3Human gates
5/10Onboarding score
Admin approvalEmail verificationMandatory 2FA
Fastest path to a key
- Talk to salesFill Developer Edition signup form at developer.salesforce.com/signup (name, email, company, country, username)
- Click activation link in email and set password
- Talk to salesComplete MFA registration at first UI login (Salesforce Authenticator/TOTP)
- Talk to salesAgent installs Salesforce CLI (npm i -g @salesforce/cli) and runs 'sf org login web' (browser OAuth) -> 'sf org display' yields access token + instance URL
- Talk to salesCall <instance>/services/data/vXX.X/sobjects with Bearer token (or use DX MCP: npx @salesforce/mcp --orgs DEFAULT_TARGET_ORG)
- Working API key
Biggest gap
Hosted MCP is off by default, requires a hand-built External Client App, and is billed via Flex Credits that need a sales contact.
Worth copying
Per-product llms-*.txt files with an explicit instruction block telling LLM agents which official docs to prefer.
Sources (9) · checked 2026-10-11
- https://developer.salesforce.com/llms.txt
- https://developer.salesforce.com/docs/llms.txt
- https://developer.salesforce.com/docs/llms-hosted-mcp-servers.txt
- https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/hosted-mcp-servers-overview.md
- https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/claude.md
- https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/activate-mcp-servers.md
- https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mcp_server_eca.htm
- https://developer.salesforce.com/signup
- https://mcpservers.org/servers/salesforcecli/mcp
30Readiness score / 100
L1 Agent-readableBeats 35% of 1,846 companies
Access10/20
Context9/20
Interfaces8/32
Onboarding3/19
Trust0/9
llms.txt · docs
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +10 Agents get the real page, not a bot wall. Serve the homepage to AI user-agents (Claude-User, ChatGPT-User) without a challenge or 403.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
- FAILAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- FAILSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- PASSFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 14 changes, up to +70 points
Each change is ready to paste, filled in for salesforce.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/salesforce.com)