# What are MCP Pro Actions? Connect to 20+ enterprise services instantly with Model Context Protocol --- > **Note:** MCP Pro Actions require a Studio plan or higher. > href="https://build.chipp.ai/plans" > target="_blank" > rel="noopener noreferrer" > > > > Upgrade to Studio → > MCP (Model Context Protocol) Pro Actions give your AI assistant instant access to popular enterprise services like HubSpot, Zapier, and 20+ other platforms, without writing any code. Unlike custom actions where you configure individual API calls, MCP Pro Actions connect to entire service ecosystems with hundreds of pre-built capabilities. ## How It Works 1. **Select a provider** → Choose from HubSpot, Zapier, and more 2. **Authenticate once** → Sign in with OAuth or paste an API key, depending on the provider 3. **Pick capabilities** → Enable specific tools (e.g., "Search HubSpot contacts", "Create Zapier zap") 4. **Start using** → Your AI can now interact with that service ## MCP vs Custom Actions | Feature | MCP Pro Actions | Custom Actions | |---------|-----------------|----------------| | **Setup Time** | 2 minutes | 10-30 minutes per action | | **Capabilities** | 10-100+ per service | 1 per configuration | | **Authentication** | OAuth sign-in or API key | Manual API key setup | | **Maintenance** | Provider handles updates | You maintain endpoints | | **Best For** | Popular enterprise services | Your own APIs | ## Available Integrations ### CRM & Sales
HubSpot
HubSpot (OAuth)
Close
Close (API Key)
### Recruiting
SeekOut
SeekOut (OAuth)
### Productivity
Granola
Granola (OAuth)
Otter
Otter.ai (OAuth)
Fireflies
Fireflies (API Key)
### Developer Tools & AI Platforms
Cloudflare (OAuth, plus Docs and Blog with no sign-in)
ElevenLabs (OAuth)
### Automation
Zapier
Zapier
### Data & RAG
Needle
Needle (API Key)
Dappier
Dappier (API Key)
Audioscrape
Audioscrape
LLM Text
LLM Text (SSE)
### Web Data
Apify
Apify (OAuth)
### E-Commerce & Payments
Mercado Libre
Mercado Libre (API Key)
Mercado Pago
Mercado Pago (API Key)
Dodo Payments
Dodo Payments (API Key, SSE)
### Communications
Telnyx
Telnyx (API Key)
### Software Development
Semgrep
Semgrep (SSE)
GitMCP
GitMCP
Javadocs.dev
Javadocs.dev
### AI Platforms
Hugging Face
Hugging Face
### Infrastructure
OpenMesh
OpenMesh
### Markets & Forecasting
Manifold Markets
Manifold Markets
## Real Examples ### Notion: Create Project Documentation User: "Create a Notion page for our Q1 Marketing Campaign with sections for goals, timeline, and budget" The AI: 1. Creates a new page in your Notion workspace 2. Adds structured headings and content 3. Links to related pages 4. Returns the page URL ### HubSpot: Lead Qualification User: "Is jane.doe@company.com in our CRM? If so, what's their deal status?" The AI: 1. Searches HubSpot contacts 2. Finds the contact record 3. Checks associated deals 4. Reports current stage and value ### Zapier: Automated Workflows User: "When a new contact is added to HubSpot, trigger our welcome email workflow" The AI: 1. Monitors HubSpot for new contacts 2. Triggers designated Zapier workflow 3. Executes connected automation steps 4. Confirms workflow completion ## Authentication Types ### OAuth (Recommended) - **Services**: Notion, HubSpot, Otter.ai, SeekOut, Apify - **Setup**: Click "Connect" → Authorize in popup - **Security**: Tokens managed automatically, can revoke anytime - **Best For**: User-specific data access ### API Key - **Services**: Fireflies, Close, Needle, Telnyx - **Setup**: Paste your API key from the service - **Security**: Encrypted storage, never exposed to AI - **Best For**: Workspace or account-level access ### Server-Sent Events (SSE) transport SSE is a transport, not an authentication type. - **Services**: Semgrep, Dodo Payments - **Setup**: Chipp preselects the SSE transport for these providers. Authenticate as the provider requires (Dodo Payments uses an API key, Semgrep needs none) ## Security & Privacy **Your data stays secure:** - OAuth tokens stored encrypted - API keys never logged or exposed - Scoped permissions (read-only when possible) - Revoke access anytime in settings **What the AI can access:** - Only what you authorize during OAuth - Limited to specific tools you enable - No access to credentials or tokens - All actions logged for audit ## Setup Guide ### OAuth Services (Notion, Otter.ai, SeekOut) 1. Go to **Brain** → **Integrations** → **Browse all integrations** 2. Find your service (e.g., Notion) 3. Click **Connect Notion** (the button names the service) 4. Authorize in the popup window 5. Select which tools to enable 6. Click **Save & Enable** ### API Key Services (Fireflies, Close, Needle) 1. Get your API key from the service: - **Fireflies**: Settings → Developer Settings → API Key - **Close**: Settings → Your API Keys → Create Key - **Needle**: Dashboard → API Keys → Generate 2. Go to **Brain** → **Integrations** → **Browse all integrations** 3. Find your service 4. Click **Configure** (the button names the service) 5. Paste API key 6. Leave the transport as preselected (HTTP or SSE) 7. Click **Test & List Tools** 8. Enable desired capabilities 9. Click **Save & Enable** ### Custom Remote MCP Server Have your own MCP server? Connect it: 1. In **Browse all integrations**, click **Custom Server** (under **Custom**) 2. Enter an integration name and the server URL (e.g., `https://your-mcp-server.com/mcp`) 3. Choose transport: HTTP (Streamable) or SSE (Legacy) 4. Select authentication: **None**, **Bearer Token / API Key**, or **API Key (Custom Header)** 5. Add credentials if required 6. Click **Test & List Tools** 7. Enable tools 8. Click **Save & Enable** > **Warning:** A custom server has no per-user OAuth option. Every user of your app shares the one credential you enter here. Per-user sign-in (each end user connects their own account) is available only for some built-in providers. ## Troubleshooting ### OAuth Connection Fails **Problem**: Popup closes without connecting **Solutions**: - Allow popups for build.chipp.ai - Try in an incognito window - Check service status page - Re-authorize from scratch ### API Key Invalid **Problem**: "Authentication failed" error **Solutions**: - Verify key is copied completely - Check key hasn't expired - Ensure key has required permissions - Generate a new key if needed ### Tools Not Appearing **Problem**: No tools listed after connecting **Solutions**: - Check service is operational - Verify authentication succeeded - Try reconnecting - Contact support if persists ### Rate Limits **Problem**: "Too many requests" error **Solutions**: - Check service rate limits - Upgrade service plan if needed - Implement delays in prompts - Contact provider support ## Best Practices **Start small**: Enable 3-5 tools initially, expand as needed **Be specific**: Use clear tool descriptions so AI knows when to use them **Test first**: Try the action manually before letting AI use it **Monitor usage**: Check logs regularly to understand AI behavior **Revoke unused**: Disable tools you're not actively using **Rotate keys**: Update API keys periodically for security ## Limitations **Per service**: - Most MCP providers support 10-100+ tools - Rate limits vary by provider - Some require paid service plans **Per app**: - No hard limit on MCP connections - Performance may vary with 50+ enabled tools - Consider grouping related capabilities ## Pricing MCP Pro Actions are included with: - ✅ Studio plan ($99/mo) - ✅ Studio plan ($99/mo) - ✅ Studio Pro plan ($299/mo) - ✅ Build For You (\$2,500/mo) and Fractional CTO (starts at \$12,500/mo) Individual service costs (separate from Chipp): - Most services have free tiers - Some MCP-connected services may require their own paid plans - Check each provider's pricing page See current plans and pricing at [chipp.ai/pricing](https://chipp.ai/pricing). ## What's Next?
## Need Help? - 💬 [Join Discord](https://discord.gg/chipp) - 📧 [Email support@chipp.ai](mailto:support@chipp.ai) - 📚 [Browse all docs](/docs) - 🚀 [Start building](https://build.chipp.ai)