Connections
Connect your tools to MeshMesh securely
Connections & Integrations
Connect MeshMesh to your Salesforce products, extend capabilities with MCPs (Model Context Protocol), and enable agent-to-agent communication with A2A. All connections are encrypted and you maintain full control over data access.
Quick Setup: Most connections take less than 5 minutes to configure
Overview
MeshMesh integrates with your tools and services through three main connection types:
Salesforce Products
Direct connections to Sales Cloud, Marketing Cloud, Service Cloud, Data Cloud, and more using Salesforce OAuth and APIs
MCPs (Model Context Protocol)
Extend AI capabilities with specialized tools, external services, databases, and custom integrations
A2A (Agent-to-Agent)
Enable communication between AI agents for multi-agent workflows and specialized service delegation
Salesforce Products
Connect your Salesforce ecosystem to query data, manage campaigns, automate workflows, and more.
Supported Products
Salesforce Core Products
Connect via Salesforce OAuth for:
- Sales Cloud
- Revenue Cloud
- Service Cloud
- Industry Cloud
- Data Cloud
- Agentforce
- Einstein
- CRM Analytics
- Commerce Cloud
- Experience Cloud
- Marketing Cloud Growth
- Marketing Cloud Advanced
- Marketing Cloud Next
- Flows
- APEX
- Lightning Apps
What is Salesforce OAuth? A secure authentication method that allows MeshMesh to connect to your Salesforce org through your browser, without requiring credentials to be stored.
Permissions: MeshMesh can only act on Salesforce products, features, and data capabilities based on your specific user permissions in Salesforce.
Marketing Cloud Engagement
Connect via Install Packages with Server-to-Server component for:
- Data Extensions
- Email Studio
- Journey Builder
- Automation Studio
- Content Builder
Required Information:
- Client ID and Secret
- Authentication Base URI
- REST Base URI
- SOAP Endpoint URL
Permissions: Data Extensions, Email, Journeys, Automation (Read/Write)
Learn more: Marketing Cloud Install Packages
Mulesoft MCP Gateway
Connect via MCP Server Integration for:
- API-led connectivity
- Integration patterns
- MCP server capabilities
Required Information:
- MCP Gateway access credentials
- API endpoint configuration
- Integration permissions
Learn more: Mulesoft MCP Server
Salesforce Setup
MCPs (Model Context Protocol)
MCPs extend your AI tasks with specialized capabilities—from querying databases to calling APIs to generating content. Think of MCPs as plugins that give your AI superpowers.
What are MCPs?
Model Context Protocol is a standardized way for AI models to interact with external systems. MCPs enable your tasks to:
- Access real-time data from external services
- Query databases and data warehouses
- Call third-party APIs
- Generate specialized content
- Communicate with other AI agents
Built-in MCPs
Several MCPs are automatically available with no additional setup required:
SFMC (Salesforce Marketing Cloud)
Query Data Extensions, manage Journeys, create Email campaigns, and automate marketing workflows
A2A (Agent-to-Agent)
Connect to and communicate with other AI agents using the Agent-to-Agent protocol
Artifact Creator
Generate structured content, documents, and formatted outputs
Social Media
Create platform-specific content for LinkedIn, Twitter, Facebook, and more
Built-in MCPs are ready to use immediately in any task—just reference them naturally!
Example Usage:
"Query Marketing Cloud for all active journeys"
"Generate a LinkedIn post about our new product"
"Call the weather-agent to get today's forecast"
"Create a summary document from this data"Import Custom MCPs
Add any standard MCP to extend capabilities further:
Go to Connections Page
Navigate to Connections → Import MCP Config
Paste MCP Configuration
Enter your MCP JSON configuration:
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-brave-search"],
"env": {
"BRAVE_API_KEY": "YOUR_API_KEY_HERE"
}
}Other examples:
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}{
"command": "node",
"args": ["/path/to/your/mcp-server.js"],
"env": {
"DATABASE_URL": "postgresql://...",
"API_KEY": "your-key"
}
}{
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN",
"Content-Type": "application/json"
}
}Auto-Detection
MeshMesh automatically detects:
- Required credentials and environment variables
- Field types (passwords, URLs, numbers, text)
- MCP communication type (stdio, HTTP, SDK)
Enter Credentials
Fill in the detected credential fields securely
Save and Use
Your MCP is now available in all tasks!
Any MCP following the standard Model Context Protocol will work with MeshMesh
Using MCPs in Tasks
Once configured, MCPs work seamlessly with natural language. The AI automatically selects the right MCP based on your request:
A2A (Agent-to-Agent Protocol)
A2A enables AI agents to discover and communicate with each other, allowing for sophisticated multi-agent workflows and specialized service delegation.
What is A2A?
The Agent-to-Agent protocol allows different AI agents to:
- Discover each other's capabilities automatically
- Communicate using standardized message formats
- Collaborate on complex, multi-step tasks
- Delegate specialized work to expert agents
The A2A MCP is built-in and available immediately—no manual configuration required!
Use Cases
Specialized Services
Connect to domain-specific agents like weather services, financial analysis, data analytics, or industry-specific tools
Multi-Agent Workflows
Orchestrate complex tasks where different agents handle their areas of expertise (research, analysis, content creation)
External Integration
Bridge MeshMesh with A2A-compatible services from other platforms and vendors
Microservices Architecture
Build modular AI systems where each agent has clear responsibilities and can be updated independently
Getting Started with A2A
Basic A2A Operations:
A2A Message Flow
A2A Security Features
- In-memory registry - Agents registered per session (not persisted)
- Network timeouts - Automatic timeout handling for unresponsive agents
- Error handling - Graceful degradation when agents are unavailable
- Future authentication - OAuth2/JWT support planned
A2A agents are session-scoped for security—they don't persist between sessions and must be re-registered
Connection Architecture
All connection types work together seamlessly in your AI tasks:
Security
Encryption
All credentials encrypted at rest and in transit with zero-knowledge architecture and SOC 2 compliance
Access Control
You control permissions through Salesforce scopes, MCP configurations, and connection settings. Audit logs track all actions.
Environment Isolation
Credentials never exposed in logs, task outputs, or error messages
Token Management
Automatic token refresh keeps connections active without manual intervention
Connection Control
Enable, disable, or revoke any connection instantly without affecting others
Session Security
A2A agents are session-scoped and don't persist, reducing security risks
Security Best Practices
For all connections:
- Never share API credentials or tokens publicly
- Use least-privilege permissions and scopes
- Regularly rotate credentials and API keys
- Monitor connection audit logs
- Review permissions before enabling new connections
For Salesforce:
- Regularly review and audit connected apps
- Use dedicated users with appropriate permissions for integration work
For MCPs:
- Never commit MCP configurations with real credentials to version control
- Use environment variables for sensitive data
- Review MCP permissions before importing
For A2A:
- Only register trusted A2A agents
- Verify agent URLs before registration
- Monitor agent calls in audit logs
Troubleshooting
Build Your Own
Want to create custom MCPs or A2A agents?
Any tool following the MCP or A2A standards will work with MeshMesh—no proprietary integration needed!