Publish one assistant surface
Admins define which objects, fields, bundles, and tools one assistant is allowed to use.
Salesforce MCP server for teams that need boundaries.
emcee is a remote Salesforce MCP server and control layer for bounded assistants. It uses Model Context Protocol to expose assistant-specific Salesforce tools instead of giving a generic AI client broad org access.
The current runtime base host is https://runtime.emcee-ai.com.
Published assistants receive their own scoped MCP URL under
/mcp, transport is Streamable HTTP, and the runtime
surface is intentionally narrower than a broad Salesforce
connector.
No raw SOQL passthrough. Assistant-scoped endpoints. Named-user runtime binding.
What emcee is
- A remote Salesforce MCP server with assistant-scoped URLs under
/mcp. - A bounded tool surface over Salesforce REST.
- A publish-before-runtime model for assistant-specific access.
- A named-user runtime with tenant, org, user, and assistant binding.
- An early-access product, not a generic whole-org connector.
Recruitment assistant setup
Real product screenshot from the current assistant setup flow.
Why this has a smaller blast radius than most Salesforce MCPs
Many Salesforce MCP servers focus on broad object access, org-wide record search, or free-form query power. emcee is built around a narrower problem: giving one team a useful assistant without turning the whole Salesforce org into one wide-open agent surface.
Give that assistant its own endpoint
Published assistants get a scoped MCP URL instead of sharing one catch-all org endpoint.
Assign named users
Assistant access is granted deliberately to people, not assumed from a shared connector.
Bind runtime per assistant
Each runtime session resolves to one tenant, one org, one user, and one assistant.
Current Salesforce MCP posture
The current remote runtime is intentionally specific. It supports bounded retrieval, document, activity, and note operations, and assistant-scoped context assembly. It does not expose generic SOQL passthrough.
Transport
Streamable HTTP on assistant-scoped URLs under /mcp behind the public runtime host https://runtime.emcee-ai.com.
OAuth model
OAuth 2.0 discovery and dynamic client registration for MCP clients that connect through OAuth.
Tool surface
Schema discovery, structured listing, structured aggregates, record bundle assembly, and bounded document, activity, and note follow-up actions.
What it does not expose
No raw SOQL passthrough, no generic whole-org search surface, and no pretending the endpoint is broader than it is.
Salesforce MCP FAQ
These are the plain questions people ask when they are comparing MCP servers, Salesforce connectors, or early-access runtime products.
Is emcee a Salesforce MCP server?
Yes. emcee exposes a remote MCP runtime for Salesforce through Model Context Protocol, but the surface is bounded per assistant instead of broad by default.
What is the MCP endpoint?
The current runtime host is https://runtime.emcee-ai.com. Published assistants receive their own scoped MCP URL under /mcp, rather than sharing one catch-all org endpoint.
Does it support OAuth discovery and DCR?
Yes. emcee supports OAuth 2.0 discovery and dynamic client registration for MCP clients that authenticate through OAuth.
Does it expose raw SOQL?
No. The current runtime uses Salesforce REST underneath and intentionally avoids generic SOQL passthrough as a product surface.
How is access scoped?
Admins publish one assistant surface, assign named users, and runtime sessions bind to one tenant, one org, one user, and one assistant.
Which teams are the best fit first?
Recruitment is the clearest live example today. Sales and service follow the same pattern when the problem is safe retrieval, not a general chatbot.
Is this self-serve already?
No. emcee is early access and the rollout is still hands-on. That is deliberate and part of the current product posture.
When this page is useful
- You are searching for a Salesforce MCP server, not a generic AI demo.
- You need a remote runtime endpoint instead of a local-only connector.
- You need assistant-scoped endpoints, named-user access, and a security answer that stands up in review.