The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Building Custom Objects and Permission Sets with the Salesforce Development Plugin for Claude Code (opens in a new tab)

You will learn how to set up the Salesforce Development Plugin in Claude Code, prepare an org with the metadata-experts and salesforce-api-context MCP Servers, and generate a Custom Object, Permission Sets and a Lightning page as metadata.

Why read this

You will also see why the older Salesforce DX MCP Server is being retired and why deployments should stay with humans.

  1. Create the DX project
  2. Build the Custom Object and fields
  3. Build the Permission Sets
  4. Build the Lightning page
  5. Package the metadata for a human to deploy
The main stages of building metadata with the plugin in the worked example

The article explains how the Salesforce Development Plugin for Claude Code differs from other tools with similar names. It groups Skills, the Salesforce CLI and hosted metadata servers into one toolset, while the Salesforce DX MCP Server reaches end-of-life on November 2, 2026, and Salesforce in Claude is aimed at end users rather than builders. The author lists the prerequisites: Node.js, Python, the Salesforce CLI and Claude Code, with a Claude plan that includes Claude Code. The org must have the MCP Servers page under Integrations and API Catalog used to enable the metadata-experts and salesforce-api-context MCP Servers.

The walkthrough then installs the plugin with the claude plugin install command and runs the setup command to check the org connection. The author builds a worked example, The General Store, using prompts that create a DX project, an Equipment Loan Custom Object with picklists, a lookup and a long text field, two Permission Sets, and a Lightning Record Page. He reviews the generated XML to confirm the read, create and edit permissions match the requirements.

The piece closes with advice on safety. It recommends building in a sandbox, Developer Edition org or Scratch Org, keeping deployments in human hands, and giving the agent specific field names and permissions because the model is trained on generic data.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Recommended

Exposing HXL widgets to Slackbot through a custom MCP server (opens in a new tab)

You will learn what a custom MCP server needs before Slackbot can render HXL widgets, how to connect Slack through the Salesforce Org Connection, and how to set tool permissions and descriptions so the right tool is chosen.

Why read this

You will also see how to troubleshoot a missing card.

  1. Check the MCP server definition
  2. Map users by Federation ID
  3. Request and approve the org connection
  4. Add the MCP server in Slack admin
  5. Turn on the server and set tool permissions
Steps to make an HXL widget appear in Slackbot, in the order the article gives them

The article explains how to make an existing HXL widget appear in Slackbot. If a widget already renders in Claude or ChatGPT, it can render in Slackbot without changes to the widget, the Apex action or the Custom Lightning Types. The remaining work is configuration: deciding how Slack connects to the Salesforce MCP server, who can use it, and which tools Slackbot may run. The author uses the Pronto sample app to show a storefront card and a follow-up menu card.

Before connecting, the server must be active, every resource needs a description, each tool’s uiResource must match a resourceName, and each tool’s readOnly and destructive flags must be set. Slackbot treats unclassified tools as write tools, which adds confirmation prompts. The connection itself is made through the Salesforce Org Connection: users are mapped by Federation ID, the org is requested and approved from Slack and Setup, and the MCP server is added in Slack admin and confirmed by a Date added value.

Each user then turns on the server in Slackbot and approves tools, choosing Allow once, Always allow or Deny per tool. Two limits apply: up to five active servers per user, and a 60-second timeout per call, with stateless calls that rerun the Apex action, so calls should stay small. Overlapping tools on other servers or Slackbot’s own Salesforce search can cause a plain table instead of the card, so descriptions should be specific.

The troubleshooting section maps common symptoms, such as plain text, missing tools, or blank values, to causes and fixes. Testing with a debugging tool like MCP Inspector helps separate server definition problems from Slack problems.

Read the original at Salesforce Developers Blog (opens in a new tab)

Also told by InfallibleTechie (opens in a new tab)

Worth reading?

Salesforce Catalog gives AI assistants a live index of your org's metadata (opens in a new tab)

You will learn what Salesforce Catalog indexes, how it grounds AI answers and code generation in your org's real object and field names, and how an admin enables it and connects an AI assistant or the Data 360 MCP server.

Without Catalog

  • Agent guesses field names
  • Deploy fails on unused field
  • Engineer or Setup review needed

With Catalog

  • Agent searches the live index
  • Returns closest real matches
  • Answers only what user may see
Catalog lets an agent check the org's real names before it answers or writes code

Salesforce Catalog is an index of how an org is built, covering Objects, Fields, Flows, Apex, Permission Sets, users, and Data 360 components such as data streams, calculated insights and segments. It updates as teams deploy changes, so no separate documentation has to be written or maintained. An AI assistant or agent consults the Catalog before answering, and every question runs as the signed-in user, so answers are limited to what that user may see.

The article gives examples from a service operations manager tracing a CSAT figure back to its source, a data owner checking what depends on a field before changing it, and a developer who avoids using an unused field name. Catalog matches questions by meaning as well as by name, returns a short ranked list of candidates, and lets the agent read details only for those, which the article says keeps responses fast in large orgs and reduces failed deploys.

An admin enables Catalog in Data Cloud Setup and turns on the MCP Server, then connects an AI assistant such as Claude, ChatGPT or Cursor, or Agentforce Vibes, which comes preconfigured. Teams building their own agents can use the Data 360 MCP Server, and Agent Context Engine uses Catalog to supply context. The article notes that Catalog is available in every edition that supports Data 360 and points to a setup guide for steps and permissions.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Must-read

Metadata Grounding lets coding agents search your org's Metadata by intent (opens in a new tab)

You will learn how the Metadata Grounding MCP Server indexes org metadata, how to connect it, and how to use describe, search and query so agents reuse existing components instead of rebuilding them.

  1. describe_metadata: list types and schemas
  2. search_metadata: find items by intent
  3. query_metadata: read the full record
The three Metadata Grounding tools run in order, so the agent checks the org before writing code

Coding agents working on a Salesforce org often build new components because they only see the part of the org that has been retrieved into a local project. The Metadata Grounding MCP Server (Beta) addresses this by searching a pre-indexed catalog of the whole org’s metadata, so an agent can check what already exists before writing code. It is one of three pieces in the Headless Toolkit, alongside Skills, which teach patterns, and the Headless 360 MCP Server, which lets the agent act. Metadata Grounding answers the question of what is currently in the org. It is read-only, runs as the authenticated user so it returns only what that user may access, and covers more than 70 core metadata types, though not Data 360 metadata.

The server exposes three tools: describe_metadata lists available types and their schemas, search_metadata finds components by natural-language intent with optional type and subtype filters, and query_metadata returns the full record for a result. The recommended workflow is describe, then search, then query. Behind it, Salesforce Catalog extracts metadata from the org, stores it in a Data 360 data lake object mapped to a Catalog data model, and indexes it with a hybrid of vector and keyword search. Catalog updates supported types incrementally and runs a full refresh every 24 hours, so very recent deployments may take time to appear.

The article illustrates two uses in Pronto, a sample food delivery org. In the first, a vague bug report about a non-working menu category was traced to an Apex controller and a Lightning Web Component found by describing the symptom, with the type filter narrowing noisy results. In the second, an agent found an existing Apex class with a summarize-reviews action and extended it rather than building a duplicate. The article advises adding a project rule telling agents to search the org first. It also covers setup: an org with a supported Data 360 edition, Salesforce Catalog enabled, and admin activation of the server, with the server available either standalone for any MCP client or inside the Headless 360 MCP Server, which will later be renamed the Salesforce MCP Server. Caveats include that search only finds candidates, which should be confirmed by query; the server does not return source code; and usage is metered in production but not in pre-production orgs. Planned additions are AI-generated metadata descriptions and a Metadata Graph for dependency analysis.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

How Salesforce uses headless patterns internally, and how to apply them (opens in a new tab)

You will learn how Salesforce applies headless architecture to agents, customer-facing experiences and internal tooling, and the three components it considers necessary for a trusted headless agent.

Why read this

You will also see the reported gains from building on Multi-Framework with React.

  1. Ground in business context via Data 360
  2. Interpret requests and act through tools
  3. Build governance in from the start
The three baseline components Salesforce uses to build a trusted headless agent

Salesforce presents its Headless Toolkit and AIforce as a way to bring platform capabilities, security and business context to any surface where work happens, rather than confining them to a single standard UI. The post follows its “Customer Zero” principle and describes four internal uses: an IT support agent that runs in Slack and a self-service portal on the same Flows and governance, a security and access agent that calls tools exposed by the Salesforce MCP server, a Headless Experience Layer playground for building widgets with mock data, and a React app that monitors a 15,000-engineer internal org.

The post says a trusted headless agent needs three baseline components: grounding in business context through Data 360, the ability to interpret requests and act through tools, and governance built in. It also reports that Builder Central’s frontend was rebuilt in React on Multi-Framework in a two-week sprint, where the previous stack would have taken two to three months, and that the development inner loop dropped from minutes of build and sync time to seconds.

Most of the piece is positioning and promotion, and it gives few concrete measurements or code. The architectural pattern of building logic once and exposing it through several surfaces is the useful takeaway for architects, with the timing claims as Salesforce’s own account.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Recommended

Running Apex tests on a local runtime, without an Org round trip (opens in a new tab)

You will learn what renmy runtime does, how it runs Apex and Flows locally against an embedded PostgreSQL, and which commands cover testing, debugging, AI agent integration and gated deploys.

Why read this

You will also see what the benchmark claims and what sits behind the Pro tier.

  1. Snapshot selected source into a bundle
  2. Run local validation and test gates
  3. Check-only validation in the target org
  4. Deploy the validated bundle
The gated deploy path from local source to the Salesforce org

Nimbus has been renamed renmy runtime, with the same tool and the same binary. It is a local Salesforce Apex runtime that executes real Apex, SOQL, DML and Salesforce Flows on a developer’s machine against an embedded PostgreSQL database. The runtime enforces platform rules such as governor limits, order of execution across triggers and flows, and per-test transaction isolation. It ships as a single binary for macOS, Linux and Windows and needs no org, Scratch Org, Docker or JVM.

The article’s benchmark compares four open-source Apex suites containing 837 tests. Run in a Salesforce org, they took about 1 minute 46 seconds, and locally they took about 2.4 seconds, roughly 45 times faster, with every test passing in both places. Around the runtime sit a language server that serves editors such as VS Code, Cursor, Neovim, Zed and JetBrains IDEs, a live debugger that supports breakpoints and stepping, and line and branch coverage reporting. Pro adds mutation testing, which the author says is the first of its kind for Apex, and watch mode. The toolkit also includes failure explanation and triage tools, a browser-based Dev UI, and a flaky-test finder.

For AI coding agents, renmy provides an MCP server with tools for running tests, executing anonymous Apex, reading coverage and explaining failures, so agents can verify Apex locally before anything reaches an org. The deployment path is gated: renmy deploy is free and snapshots the source, runs local tests and coverage gates, validates the same bytes in the target org with a check-only validation, and then deploys. The Pro renmy release commands split validation from deployment and produce a receipt that records the bundle digest, Git revision, gate results and the validation job ID, so a team can approve and deploy the validated payload from another machine. The article stresses that Sandboxes remain useful for end-to-end checks and user-facing testing.

The Free tier costs nothing without a card and covers unlimited local test runs, gated deploys, Salesforce CLI pass-through and IDE integrations on one machine. Pro, which adds the daemon, parallel runs, debugger stepping, mutation testing and the MCP server across three machines, and Team are both free during the public beta. Their list prices are $19 per month and $49 per developer per month, and Enterprise starts at $20,000 per year.

Read the original at dev.to (opens in a new tab)

Worth reading?

Build a Claude Code mod to display Salesforce CLI org context (opens in a new tab)

You will learn how to create a Claude Code mod that reads Salesforce CLI configuration files to show your default org, its type, and Scratch Org expiry directly above the command prompt.

Why read this

The guide covers the required plugin structure, event hooks, and testing steps.

The article walks through creating a custom plugin for Claude Code that surfaces Salesforce CLI context directly in the terminal interface. It explains how to set up the plugin manifest, define reactive state types, and structure the directory for hooks and tests.

Instead of running slow CLI commands, the mod reads internal Salesforce authentication and configuration files to determine the target org alias, My Domain, org type, and Scratch Org expiration date. It also tracks which organizations are connected to configured Salesforce MCP servers.

The tutorial details several event hooks that trigger when sessions start, directories change, or tool calls execute. A render hook draws a colored status band above the prompt, using theme-aware colors to distinguish production, sandbox, and Scratch environments. The author includes validation and testing procedures, plus instructions for making the plugin load automatically across sessions.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

Must-read

Preparing your org for the Claudeforce partnership and new billing model (opens in a new tab)

Readers will learn how to configure the Salesforce in Claude plugin, audit permissions for agentic access, and prepare for the November billing model using Flex Credits and agent registration.

  1. Audit Permission Sets and profiles
  2. Clean the fields the skills read
  3. Keep approvals on
  4. Pilot in a sandbox
  5. Name an owner for connections
Five checks to prepare your Salesforce org for Claudeforce and AIforce billing

Claudeforce, the expanded Salesforce and Anthropic partnership announced on August 26, 2026, works in two directions. Claude becomes a reasoning model inside Agentforce and the default model in Slack, while Salesforce reaches into Claude through the Salesforce in Claude plugin. That plugin bundles 37 prebuilt sales skills covering account research, call prep, pipeline review and CRM updates, with Salesforce and Slack connectors. It is in beta for approved orgs on paid Claude plans and requires the latest Sales Cloud Enterprise edition.

On security, sellers sign in with their own Salesforce credentials, so Claude can only do what their permissions allow, and by default it asks for approval before any write. Salesforce Help notes that when a custom action uses a Claude model hosted inside the Salesforce Trust Boundary, data stays inside that boundary, though Einstein Trust Layer data masking is disabled for those agents and zero data retention still applies. The article advises reading that page in full before writing a risk assessment, and it warns that most capability claims come from launch material and should be tested in a sandbox first.

The setup path has four stages. First, the org confirms eligibility and gets approval through the beta sign-up on AgentExchange. Second, a Salesforce admin creates an External Client App for Claude, because Connected Apps are not supported for MCP clients. Third, a Claude Primary Owner or Owner enables the plugin in Organization settings and enters the app’s consumer key and secret. Finally, each member signs in with their own Salesforce account on first use.

The billing changes are targeted for November. Admins register agents, each of which gets its own identity and can hold a narrower Permission Set than a human user. Every successful MCP or API call from a registered agent counts as a Headless Platform Interaction, paid with Flex Credits, though the rates are still TBA and metering applies only to active production orgs, with 30 days’ notice before it starts. Customers who buy on or after September 17, 2026 must register agents at purchase, while existing customers register at renewal. The article does not say how the Salesforce in Claude plugin will be classified under this model.

The article recommends five preparation steps: audit Permission Sets and Profiles, clean the fields the skills read, keep approvals switched on, pilot in a sandbox, and name an owner for connections and consumption. Cloud Odyssey’s own view is that Claudeforce exposes existing CRM data quality problems, and it suggests starting with a health check, connecting surrounding systems, piloting with one team, and keeping model choice open.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Recommended

Generate custom Salesforce Connect adapters with AI skills and headless registration (opens in a new tab)

You will learn how to use the platform-salesforce-connect-adapter-generate skill to automatically create DataSource classes for any REST API.

Why read this

The piece also explains how to register the external data source programmatically using the Headless 360 MCP Server instead of manual setup steps.

Custom Salesforce Connect Apex adapters require implementing DataSource.Provider and DataSource.Connection interfaces, which traditionally demands significant Apex expertise and careful handling of field types, pagination, and error contracts. The article introduces the platform-salesforce-connect-adapter-generate skill, an open-source capability that grounds coding agents in this exact framework so they produce syntactically correct and contract-compliant code on the first attempt.

Using a natural language prompt, a developer can instruct an agent like Claude Code or Agentforce Vibes to generate both adapter classes, map json fields to correct datasource datatypes, enforce required ExternalId columns, and wire Named Credentials without hardcoding secrets. The post demonstrates this with a public rail api example, showing how the generated Connection class handles query context and returns a properly structured TableResult.

After deploying the Apex classes via the Salesforce CLI, the article explains how the Headless 360 MCP Server exposes configuration operations as programmatic tools. This allows the same agent to create the external data source definition through an api call rather than navigating the Setup wizard. The author notes that Winter ’27 will expand this approach to cover the full lifecycle of external data sources and standard adapter extensibility.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?