Understand the difference between asking another assistant about Cedar context and letting Cedar use connected external tools.
Book a demo and see how Cedar helps you process your inbox in a fraction of the time.
MCP connects assistants with tools and context. For a sales team, the useful question is what work that connection enables: finding account evidence, reviewing a commitment or preparing an action in a connected system.
There are two distinct directions in Cedar. An external assistant can access Cedar through Cedar's MCP interface. Separately, Cedar's own agents can use configured external MCP tools. Those paths have different authentication and tool boundaries; one connection does not automatically grant access to every other system.
A rep working in another assistant may need to understand a deal without pasting a new transcript every time. Cedar's MCP interface provides access to supported workspace tools and context under the connected account's permissions.
A useful request is specific: identify the buyer's unresolved evaluation questions, distinguish confirmed commitments from suggestions, and reference the source for each finding. Ask for uncertainty to remain visible. A summary should not turn an unconfirmed introduction into an engaged stakeholder.
Cedar can also use external MCP tools configured for its in-product agents. This can support workflows that need information or an action outside the core Cedar workspace. The available operations depend on that server, its credentials and the permissions granted.
Read access does not imply write access. A tool that can find a support issue may not be able to create one. Validate the actual operation needed for your workflow before treating a connection as complete.
| Decision | Example |
|---|---|
| Starting event | A processed customer meeting contains an unresolved technical question |
| Required context | Account history, the exact question and relevant support information |
| Allowed work | Retrieve supporting context and prepare a response |
| Review boundary | The account owner confirms the response before sending |
| Evidence | Source references and the result of any connected-tool operation |
This is a workflow specification, not a claim that every MCP server supports every step. Start with one supported operation and make errors visible.
An external assistant connected to Cedar should connect separately to other servers it needs. Do not assume Cedar acts as a universal proxy for those credentials. Likewise, a colleague's connected integration does not prove the same tool is available to your account.
Keep the workflow's ownership clear: who maintains the connection, who can approve sensitive updates and what happens if the tool becomes unavailable? A useful failure result says what could not be completed instead of presenting a draft as a successful action.
Check source accuracy, completeness, tool success and review effort. Generating a plausible answer is not enough if it used the wrong account or missed a later message. For writes, inspect the destination and verify the intended record changed through the approved workflow.
The benefit is reusable sales context and concrete work across connected tools, with permissions and evidence intact. Explore Cedar's data layer, or read how to maintain living account knowledge.