MeshMesh
Guides

Adding Integrations

Connect additional services and custom MCPs to MeshMesh

Beyond Salesforce, MeshMesh supports several built-in integrations and lets you connect custom MCP servers for additional capabilities.

Built-in Integrations

Open the Integrations menu to see available connections:

Salesforce Marketing Cloud Engagement — Connect to MCE for email campaigns, journeys, data extensions, and automations. Requires a Client ID and Secret from an Installed Package with Server-to-Server authentication.

B2C Commerce Cloud — Connect to SFCC for code deployment, WebDAV file management, job execution, sandbox management, and more. Requires an Account Manager API Client with OCAPI and WebDAV permissions. See the B2C Commerce Cloud setup guide for step-by-step instructions.

Mulesoft Anypoint Platform — Connect to Mulesoft for API-led connectivity and integration patterns. Requires a Connected App Client ID and Secret from Anypoint Access Management.

Image Generation (Gemini) — Generate images using Google Gemini. Requires a Gemini API key.

Slack — Bring your own Slack apps and bots to MeshMesh. Send messages, manage channels, and run workflows. Requires a Bot User OAuth Token (xoxb-...) from your Slack App.

GitHub — Connect to GitHub for repository access and git operations. Requires a Personal Access Token (PAT). We recommend using a fine-grained PAT scoped to only the repositories and permissions your agent needs, with a short expiration (e.g. 7 days) for maximum security. You can create one at GitHub → Settings → Developer settings → Fine-grained tokens.

Always prefer fine-grained PATs over classic tokens. Limit the token to specific repositories and grant only the permissions required (typically Contents: Read and write). Set the shortest practical expiration — you can always generate a new token when it expires.

Each integration has its own setup flow. Select it from the Integrations menu and follow the prompts to enter your credentials.

Custom MCP Servers

MeshMesh supports the Model Context Protocol (MCP), so you can connect any MCP-compatible server to extend your agent's capabilities.

To add a custom MCP, go to Integrations → Add Custom MCP and paste your MCP configuration. The format is the same as Claude Desktop and other MCP clients:

{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-github"],
  "env": {
    "GITHUB_TOKEN": "ghp_your_token_here"
  }
}

MeshMesh automatically detects the required credentials and prompts you to fill them in securely.

Examples

Jira / Atlassian:

{
  "url": "https://mcp.atlassian.com/v1/mcp",
  "type": "http"
}

Braze:

{
  "command": "uvx",
  "args": ["--native-tls", "braze-mcp-server@latest"],
  "env": {
    "BRAZE_API_KEY": "your-braze-api-key",
    "BRAZE_BASE_URL": "your-braze-endpoint-url"
  }
}

Once connected, your agent can use the MCP's tools automatically based on your requests.