MCP Servers
MCP (Model Context Protocol) servers are external integrations that expose tools and data sources to your agents via a standardized protocol. They allow agents to connect to databases, APIs, SaaS platforms, and custom services.
Adding an MCP Server
Click the + Create button to register a new MCP server:
- Name — a descriptive name for the server
- Server URL — the endpoint where the MCP server is running (include
/mcpif applicable) - Transport type — how to communicate with the server
- Authentication — credentials if the server requires auth
Transport Types
| Transport | Use For | Description |
|---|---|---|
| SSE | Remote servers | Server-Sent Events — most common for remote MCP servers |
| HTTP | REST-based servers | Standard HTTP request/response |
| Stdio | Local processes | For MCP servers running as local child processes |
| WebSocket | Real-time servers | Persistent bidirectional connection |
Tip: Use SSE transport for most remote MCP servers. It's the most widely supported and reliable option.
How MCP Integration Works
Register MCP Server (URL + credentials)
↓
Platform discovers available tools from the server
↓
Tools become available to attach to agents
↓
Connectors manage credentials and connection state
↓
Agent invokes tools → requests routed to MCP server
Using MCP Tools
Once an MCP server is connected:
- Its tools automatically appear in the tools list
- Attach them to agents just like any other tool
- Connectors handle credential management per tool
- The agent calls tools normally — the platform routes requests to the MCP server
Connection Management
- Validate — test that the server is reachable before registering
- Monitor status — check if the server is online and responding
- Credential profiles — set up auth profiles for servers that require authentication
- Timeouts — the platform uses 60s connection timeout and 600s read timeout with automatic retries
Available Connectors (85+)
Kaman ships with 85+ pre-built MCP connectors organized by category:
| Category | Connectors |
|---|---|
| Databases | PostgreSQL, MySQL, MongoDB, Oracle, SQL Server, IBM DB2, SAP HANA, Sybase, DynamoDB, Elasticsearch, Weaviate, Firebase, Supabase |
| CRM & Sales | Salesforce, HubSpot, Zoho CRM, Pipedrive, Freshdesk, Intercom, Zendesk |
| ERP & Business | SAP OData, SAP API, NetSuite, ERPNext, Odoo, ServiceNow |
| Project Management | Jira, Asana, Monday.com, ClickUp, Trello, Basecamp, Todoist, Clockify, Calendly |
| Google Suite | Google (Gmail + Drive), Google Drive, Google Sheets, Google Ads, Google Analytics |
| Microsoft & Office | Outlook, OneDrive, SharePoint |
| Zoho Suite | Zoho CRM, Zoho Books, Zoho People, Zoho POS |
| Communication | Twilio, Telegram, Discord, SendGrid, Brevo, Mailchimp |
| E-Commerce | Shopify, WooCommerce, Etsy, Square |
| Payments & Fintech | Stripe, PayPal, Razorpay, Plaid, Instamojo, Pabbly, CoinDCX, Zerodha, QuickBooks, Xero |
| Social Media | Meta (Facebook/Instagram), Twitter/X, LinkedIn, Reddit |
| Content Management | WordPress, Strapi, Confluence, Notion |
| Knowledge & Collaboration | Airtable, Google Sheets, Dropbox |
| Code & DevOps | GitHub, GitLab, Git |
| File & Storage | SFTP, Dropbox, OneDrive, Google Drive |
| Search & Security | SerpApi, Wazuh SIEM, Home Assistant |
| Data & Feeds | RSS |
| Infrastructure | Kaman Data Gateway (on-premise bridge) |
All connectors support webhook-based change notifications, credential encryption, and multi-scope access control.
Quick Tips
- Test your MCP server endpoint before registering it
- Use SSE transport for most remote MCP servers
- Always use the full URL including
/mcpendpoint path - Set up credential profiles for servers that require authentication
- Monitor connection status — MCP servers need to be running and reachable
- Check the platform logs if you see "Session terminated" errors during sync