Salesforce MVP Hall of Fame · Certified Partner since 2010
MCP connectors your security team can inventory.
Model Context Protocol is how an agent calls a database, a SaaS API, or an internal service without a one-off integration for every model. We implement the servers, the allow-list, and the review process. The deep governance write-up lives in our MCP guide. The first week is in the org, reading what already exists.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agents · Agentforce, CrewAI, ADK, A2A
- 03Memory · Neo4j, Cognee, RAG
- 04Identity · IndyKite, SSO, entitlements
- 05Governance · policy, audit, human override
What we put in
The work on this layer.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Use cases
Where this shows up in the work.
These are the use cases we usually pair with Model Context Protocol.
AI IT Support Transformation
Ticket routing and a knowledge desk. An agent on the repeats. A person on the exceptions.
Legal document review
Contracts as a desk. Review, redline, and a lawyer on the exceptions. We will not invent a 209% ROI.
Data analytics
A view on records the org already trusts. Tableau or the CRM report after the duplicates are gone.
Related reading
From the blog.
Research-led notes that back this page.
Dots vs Grok Bot: agents and workspaces
Where each always-on agent runs, what it costs, and what to check before one touches Salesforce.
Salesforce MCP server: switch on read first
Which server to enable first, what the audit log names, and how to stop an agent.
Salesforce will bill agent calls: ask first
What Salesforce says it will meter, which agents count, and what to settle at renewal.
Questions
What we actually say.
- Is MCP a product you sell, or a protocol you implement?
- A protocol. We implement the servers, the register, and the access review. The longer security write-up is on our MCP governance guide.
- How is MCP different from A2A?
- MCP is agent-to-tool. A2A is agent-to-agent. Production stacks usually need both.
- Where do you host MCP for production agents?
- Behind Flex Gateway when the caller needs identity, rate limits, and an audit trail. Discovery is not permission.
- What does a good MCP estate look like?
- A catalogue of versioned servers, entitlements per caller, policy order fixed on the hop, and usage tagged to the team that spent it. The pattern matters more than the server list.
- Where is the full governance checklist?
- In the MCP governance guide. This page is the implementation offer; that page is the control detail.
The brief
Agents already calling tools you have not inventoried?
We will list the connectors, tighten scope, and put an approval step in front of production data.
Tell us the process
Name the job a person still does by hand. We read the org and write what is worth fixing.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks