Salesforce's own documentation for connecting an AI client to an org through MCP (Model Context Protocol) runs across six separate pages: a setup overview, creating an External Client App, activating a server, connecting a client, testing the connection, and troubleshooting if something goes wrong. There's a seventh page written specifically for Claude, with its own callback URL and its own screenshots. None of these tie together into one sequence, and none of them cover the

"Agent harness" shows up in Salesforce's own Newsroom coverage, on a dedicated Salesforce product page, and across the wider AI-tooling conversation, from Anthropic's engineering blog to LangChain's own writing about agent architecture. Stripped down, it means everything around the model except the model itself: the tools, memory, and guardrails that turn a language model's output into something a real system can act on. None of those sources define it exactly the same way, a

Most admins don't actually read Salesforce's full release notes when a new release ships every four months. Instead, they wait for a subreddit thread to fill in what people are hitting, or a roundup blog like SalesforceBen to round up that release's items. Salesforce publishes the full notes in one batch, weeks before the release goes live, but reading that page start to finish still isn't how most admins catch up. Both community habits fill a real gap, but neither is written

Working through a Salesforce release usually starts and ends with the same list: which Release Updates enforce this cycle, who's affected, what breaks if you ignore them. That list matters, and Winter '27 has one worth checking before your org's upgrade weekend. But it's a compliance list, not a features list. It tells you what stops working if you do nothing. It doesn't tell you what you can now do that you couldn't do last release, which is the other half of what a release

Every time an admin or developer opens a fresh conversation with an AI coding assistant to help with Salesforce work, the same context has to get re-established: which objects are off-limits, what a deploy checklist actually requires, how the org names its custom fields, which report to run before touching a permission set. Skip re-explaining any of it, and the assistant doesn't know something's missing. It just does the task without the constraint, and nobody notices until t

Every AI tool your team uses (Claude, ChatGPT, a coding assistant, Slack's AI features) needs some way to reach your Salesforce data if it's going to be useful for actual work. Before MCP, that meant a custom integration for each pairing of AI tool and system: one connector for Claude to Salesforce, a different one for ChatGPT to your ERP, another for the coding assistant to your ticketing system. Multiply that across every tool and every system, and the integration work neve

A deactivated Salesforce account still owns records and live permission sets. This Salesforce employee offboarding checklist shows what to check first.

A Salesforce access review means three different questions answered together: what a permission set grants, who can see a field, and what's about to expire. Here's how to get all three without a spreadsheet.

As more automation and agents take actions inside Salesforce, the Salesforce event monitoring audit trail already exists — it just arrives as an unreadable CSV. Here's how to actually read it.

Every Salesforce Agentforce readiness checklist starts with the same two questions: what sensitive data is in your org, and who can reach it. Here's how to answer both without guessing.