emcee Talk to us

Don’t give AI your whole Salesforce org.

emcee is a control layer and scoped Salesforce MCP server for bounded assistants. You publish assistant-specific access for a team or workflow, assign it to named users, and keep it inside the surface the admin approved.

Most Salesforce MCP setups widen blast radius because one connector exposes a broad org surface to every attached agent. emcee goes the other way: focused assistant surfaces and focused runtime endpoints.

Talk to us Read the security page

Assistant-scoped MCP access. Named-user runtime. Structured audit events.

Need the technical version? Read the Salesforce MCP overview.

What emcee actually does

  • Connect your Salesforce org.
  • Publish assistant-specific Salesforce scopes.
  • Grant access to named users deliberately.
  • Issue a focused MCP endpoint and bind each runtime session to tenant, org, user, and assistant.
Admin setup screen
Current setup and release surface.
emcee admin dashboard showing Salesforce org connection and bounded assistant setup

How it works

emcee is configured and released deliberately. These are the three steps from one Salesforce org to one live assistant.

1. Connect Salesforce org.

Start from the system the team already works in. Do not export data into a separate AI silo.

2. Publish bounded assistants per workflow.

Choose the objects, fields, bundles, and tools that assistant is allowed to use. If it was not published, it is out of bounds.

3. Assign it to named users.

Users receive assistant access explicitly. Runtime sessions resolve to one org and one assistant at a time.

Recruitment assistant setup
Current template-based setup flow.
emcee recruitment assistant template setup with bounded Salesforce field access

Where this is useful first

Recruitment is the clearest live example. Sales and service fit the same pattern when a team needs answers without widening the CRM blast radius.

Recruitment

Summaries across jobs, applications, interviews, notes, and placements without stitching context together by hand.

Sales

Account and opportunity context for teams that need answers without opening five tabs or broadening CRM access.

Service

Case history and activity context inside a defined assistant surface instead of a generic support bot.

Brutal honesty.

emcee is early access. The product is real, but rollout is still hands-on and best suited to teams with a specific workflow in mind.

  • Not self-serve today.
  • Not a wide-open MCP endpoint for your whole Salesforce org.
  • Not claiming certifications or controls that do not exist yet.
  • Best fit when you already know the team and workflow you want to support.
Runtime access screen
Part of the control model, not decoration.
emcee end-user portal showing named-user seat access and assistant runtime binding

What security can review today

  • Bounded assistant surfaces.
  • Named-user access and seat assignment.
  • Runtime session binding to tenant, org, user, and assistant.
  • Structured runtime audit events.
Read the full security page

Talk to us about your workflow.

Start with the workflow that creates the most report debt, the most context stitching, or the first security objection.

What to send us

  • Which team you want to start with.
  • Which Salesforce workflow is painful today.
  • Which security question will come up first.

If there is a real use case, we will talk specifics.

We will talk through the assistant surface, the rollout path, and the security questions directly.