The MCP Tools Integration allows you to connect your SigmaMind agents to any Model Context Protocol (MCP) server. This enables your agents to access dynamic tools from platforms like Zapier, Make, Composio, and custom MCP servers without individual API configuration for each tool.Documentation Index
Fetch the complete documentation index at: https://docs.sigmamind.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
MCP (Model Context Protocol) is a standardized protocol for connecting AI agents to external services and tools. By integrating an MCP server with your SigmaMind agent, you can:- Access hundreds of pre-built tools from MCP providers
- Execute actions dynamically during agent conversations
- Avoid repetitive API configuration for each tool
- Scale your agent capabilities instantly
How MCP Tools Work
- SigmaMind connects to the MCP server
- Available tools from the server are fetched dynamically
- Agent can invoke any of these tools during conversations
- Results are returned to the agent and integrated into responses
Quick Setup
Follow these steps to add an MCP tool to your agent:Step 1: Get Your MCP Server URL
Obtain an MCP server URL from your provider: Zapier MCP:- Visit: https://mcp.zapier.com/mcp/?client=sigmamind
- Generate and copy your MCP server URL
- Log in to Make account
- Go to: Profile > API Access > Tokens
- Click “Add token” and copy the MCP URL
- Log in to: https://mcp.composio.dev/dashboard
- Select tools you want to integrate
- Create server and copy the generated URL
- Ensure your MCP server is running
- Obtain the server endpoint URL (e.g., https://your-server.com/mcp)
Step 2: Add MCP Tool in SigmaMind
- Open Agent Builder
- Click Manage Tools/Apps
- Click Add Custom Tool/App
- Enter:
- Tool/App name: “Zapier Integration” (or your provider name)
- Description: “Access to MCP tools from Zapier”
- Click Submit Tool/App
Step 3: Configure Authentication
- Click the newly created MCP tool
- Click Configure Authentication
- Select Bearer Token (most common for MCP servers)
- Paste your MCP server URL as the token
- Click Submit Authentication

Step 4: Add Tool Actions
MCP servers expose tools dynamically. Rather than adding individual actions, the MCP server provides them automatically. However, you can test tool availability:- Click Add Tool Actions
- Enter test values to verify connectivity
- The MCP server responds with available tools
Step 5: Add to Your Agent
- Open your agent in Agent Builder
- Click Add Tool/Function Calls
- Select App Tool Call
- Select your MCP tool from the list
- Click Submit
Supported MCP Providers
Zapier MCP
7,000+ apps and 30,000+ actions Zapier’s MCP server provides access to thousands of pre-built integrations. Setup:- Visit https://mcp.zapier.com/mcp/?client=sigmamind
- Generate your MCP server URL
- Add to SigmaMind as MCP tool with Bearer Token authentication
- Your agent instantly has access to Zapier’s full ecosystem
- Send emails
- Create calendar events
- Post to social media
- Update spreadsheets
- And thousands more
Make MCP
Custom Scenarios & Workflows Make allows you to build custom automations and expose them as MCP tools. Setup:- Create your scenarios in Make with defined inputs/outputs
- Set scenarios to “Schedule on Demand”
- Get your MCP Token from Profile > API Access > Tokens
- Add to SigmaMind as MCP tool with Bearer Token authentication
- Custom business logic automation
- Multi-app workflows
- Data processing pipelines
- Scheduled tasks triggered by agents
Composio MCP
Popular Tool Integrations Composio provides pre-built connections to tools like Gmail, Slack, GitHub, Notion, and more. Setup:- Log in to https://mcp.composio.dev/dashboard
- Select tools you want to integrate (Gmail, Slack, etc.)
- Complete authentication flows
- Create server and copy the MCP server URL
- Add to SigmaMind as MCP tool with Bearer Token authentication
- Gmail, Outlook (email)
- Slack, Teams (messaging)
- GitHub, GitLab (code)
- Notion, Asana (productivity)
- And many more
Custom MCP Servers
You can build and deploy your own MCP server to expose custom tools. Setup:- Deploy your MCP server and ensure it’s accessible
- Obtain the server endpoint URL
- Add to SigmaMind as MCP tool
- Configure any required authentication headers
Configuration
Basic MCP Tool Configuration
In the Manage Tools/Apps section, configure your MCP tool: Tool Setup:| Field | Value |
|---|---|
| Tool/App name | Zapier Integration |
| Description | Access to Zapier tools |
| Authentication Type | Bearer Token |
| Token | Your MCP server URL |
Agent System Prompt
Include guidance in your agent’s system prompt about MCP tools:How MCP Tools Execute
Execution Flow
When your agent decides to use an MCP tool:- Tool Selection - Agent determines the appropriate MCP tool for the user’s request
- Parameter Extraction - Agent extracts values from conversation context
- Server Connection - SigmaMind connects to the MCP server using your URL
- Tool Invocation - MCP server invokes the requested tool with parameters
- Result Processing - Results are returned to the agent
- Response Generation - Agent incorporates results into its response to the user
Request Headers
MCP requests include context headers for tracking:- X-Call-Id - Included in voice calls to identify the specific call
- X-Chat-Id - Included in chat interactions to identify the chat
- X-Session-Id - Included if the chat is part of a session
Best Practices
Security
- Treat MCP server URLs as sensitive credentials
- Store URLs in environment variables, never in code
- Regularly rotate API tokens from MCP providers
- Use HTTPS for all MCP connections
Agent Instructions
- Clear Prompts: Tell your agent when and how to use MCP tools
- Error Handling: Include fallback instructions if tools fail
- Confirmation: For critical actions, have the agent confirm with users first
- Transparency: Inform users which tools are being used
Performance
- Test First: Verify MCP tools work with test requests
- Monitor Usage: Track which tools are used and how often
- Handle Delays: Be aware MCP calls may take 2-5 seconds
- Rate Limits: Check rate limits on MCP provider accounts
Troubleshooting
MCP Tool Not Available
Problem: Agent can’t access MCP tools Solutions:- Verify MCP server URL is correct and accessible
- Check Bearer Token authentication is properly configured
- Ensure agent has been published after adding MCP tool
- Refresh the dashboard to see changes
Tool Execution Fails
Problem: MCP tool returns errors Solutions:- Test the MCP server independently with cURL:
- Verify agent’s system prompt provides correct tool names
- Check MCP provider status page for outages
- Review error message for specific issues
Slow Response Times
Problem: MCP tools are slow Solutions:- MCP calls typically take 2-5 seconds - this is normal
- Check MCP provider’s server status
- Verify your network connection
- Consider switching to faster MCP provider if needed
Authentication Failed
Problem: MCP server rejects requests Solutions:- Verify the MCP server URL/token is correct
- Ensure you copied the entire URL without spaces
- Check if the token has expired (regenerate if needed)
- Verify Bearer Token is selected as authentication type
Next Steps
- Choose your MCP provider (Zapier, Make, Composio, or custom)
- Generate your MCP server URL from the provider
- Add MCP tool to SigmaMind with Bearer Token authentication
- Update your agent’s system prompt with tool instructions
- Test MCP tool with sample user requests
- Deploy and monitor usage
Related Documentation
Resources
- Zapier MCP: https://mcp.zapier.com
- Make MCP: https://developers.make.com/mcp-server
- Composio MCP: https://composio.dev
- MCP Specification: https://modelcontextprotocol.io