BoldGroup Agentforce MCP Server
Provides tools for interacting with Salesforce Agentforce agents through the Salesforce Agent API v1, enabling MCP clients to create Agent API sessions, send messages to agents, end sessions, and maintain multi-turn conversation context with agents exposed as individual tools.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
BoldGroup Agentforce MCP Server
A small MCP (Model Context Protocol) server that bridges Claude — or any MCP client — to Agentforce agents living in a Salesforce org, so Claude can call them as tools in a conversation.
Claude → MCP (Streamable HTTP) → this server → Salesforce Agent API v1 → Agentforce agentEach agent in src/config/agents.registry.json is exposed as one MCP tool (e.g. ask_simone).
The server authenticates to Salesforce once via OAuth 2.0 Client Credentials Flow, caches the
token, and maps each MCP client session to its own Agent API session so multi-turn conversations
stay in context.
Start here
DEPLOYMENT.md — step-by-step runbook for setting this up against a new org/agent and deploying to Heroku. Every real error we hit building this is called out there as a named pitfall, not just the happy path.
NATIVE_MCP_SERVER.md — a second, parallel way to expose the same agents via MCP, hosted natively inside Salesforce instead of on this external server. No code (pure Setup config), but documented the same way — what it is, how it compares, how to rebuild it, and the gotchas that are different from the Heroku path.
Related MCP server: MCP Force
Project layout
src/
index.ts # Express app, Streamable HTTP transport, inbound auth, /healthz
config/
env.ts # env var validation (zod)
agents.ts # loads + validates the agent registry
agents.registry.json # which agents are exposed, and as what tool names
contacts.ts # loads + validates the email -> ContactId registry
contacts.registry.json # known demo customers, for identity context (see below)
auth/inboundAuth.ts # Bearer-token (or ?key=) auth for inbound MCP clients
salesforce/
tokenManager.ts # OAuth client-credentials token fetch + cache
agentApiClient.ts # Agent API v1 client: create/send/end session
contactLookup.ts # email -> ContactId (see "Customer identity" below)
types.ts
mcp/
server.ts # McpServer, one tool per registry entry
toolFactory.ts # agent config -> MCP tool definition + handler
sessionStore.ts # MCP session -> Agent API sessionId mapping
util/logger.ts
scripts/
smoke-test-agent-api.ts # standalone CLI to test the Salesforce client without any MCP code
test/Local development
npm install
cp .env.example .env # fill in real values — see DEPLOYMENT.md step 5
npm run dev # tsx watch, local server on :3000
npm run smoke-test -- <agentId> # exercise the Salesforce client directly, no MCP involved
npm test # vitestWhy Agent API v1, not v2/A2A
Salesforce's newer Agent API v2 speaks the open A2A (Agent2Agent) protocol, which is the more
modern/standard choice — this server was originally built against it. In practice it required an
org-level permission (AgentApiA2A) that's pilot/internal-only and has to be explicitly granted,
not something self-serve in Setup. Agent API v1 doesn't have that restriction and is available to
external customers today, so that's what this server actually talks to. If/when the v2 permission
is granted, the Salesforce client layer (src/salesforce/agentApiClient.ts) is the only thing that
would need to change — the MCP/tool layer above it doesn't know or care which Agent API version is
underneath.
Customer identity (ContactId)
Agentforce agents often require a ContactId session variable before they'll touch anything
order/account-specific — the MIAW widget gets this for free from the logged-in customer's session,
but a headless API caller has no equivalent. The ask_* tools accept an optional email
parameter for exactly this: when Claude knows who it's talking to, it can pass their email, and
the server resolves it to a ContactId and sets it when creating the Agent API session (variables
can only be set at session creation, so a new/changed email forces a fresh session).
The resolution itself is a small checked-in lookup (src/config/contacts.registry.json), not
a live Salesforce query — the "Salesforce Integration" license that Client Credentials Flow
requires explicitly blocks standard CRM objects (Contact, Account) regardless of permission
sets, so this integration user can't query Contact at all. A real dynamic lookup would need a
second, differently-licensed integration path. Add known test customers to the registry file (or
override via the CONTACTS_REGISTRY_JSON Config Var, same pattern as AGENT_REGISTRY_JSON).
Adding another agent
Add an entry to src/config/agents.registry.json (name, toolName, agentId, description)
and redeploy — or, on Heroku, set the AGENT_REGISTRY_JSON Config Var to override the checked-in
file without a redeploy at all (a Config Var change triggers a dyno restart).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build and manage AI-native customer support agents from Claude or any MCP client.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides tools to interact with the Salesforce Agentforce API, allowing authentication, session creation, and message exchange with Salesforce agents.10-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Salesforce organizations through natural language by exposing Salesforce APIs (REST, Bulk v2, GraphQL, Tooling, Auth) as MCP tools for querying data, managing records, and executing SOQL queries.19MIT
- AlicenseNot gradedqualityDmaintenanceBridges your claude.ai authorized connectors (Slack, Atlassian, Gmail, Google Calendar) to any MCP client, enabling use of those tools without credential setup.2MIT
- AlicenseNot gradedqualityDmaintenanceConnects any MCP-compatible AI assistant directly to a Salesforce org for querying data, exploring schema, running Apex, and managing deployments.25 npmMIT