What are MCP Pro Actions?

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 → API key authentication
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

Available Integrations

CRM & Sales

Automation

Data & RAG

Web Data

E-Commerce & Payments

Communications

Software Development

AI Platforms

Infrastructure

Markets & Forecasting

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, Asana, Atlassian
• Setup: Click "Connect" → Authorize in popup
• Security: Tokens managed automatically, can revoke anytime
• Best For: User-specific data access

API Key

• Services: HubSpot, Close, Needle, Apify
• 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)

• Services: Asana, Semgrep, Dodo Payments
• Setup: Real-time streaming connection
• Best For: Live updates and monitoring

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, Asana, Atlassian)

1. Go to Build → Capabilities → Add Pro Action
2. Find your service (e.g., Notion)
3. Click Connect
4. Authorize in the popup window
5. Select which tools to enable
6. Click Save

API Key Services (HubSpot, Close, Needle)

1. Get your API key from the service:
   • HubSpot: Settings → Integrations → API Key
   • Close: Settings → Your API Keys → Create Key
   • Needle: Dashboard → API Keys → Generate
2. Go to Build → Capabilities → Add Pro Action
3. Find your service
4. Click Configure
5. Paste API key
6. Select transport type (HTTP or SSE)
7. Click Test & List Tools
8. Enable desired capabilities
9. Click Save

Custom Remote MCP Server

Have your own MCP server? Connect it:

1. Click Custom Remote MCP
2. Enter server URL (e.g., https://your-mcp-server.com/mcp)
3. Choose transport: HTTP or SSE
4. Select auth type: None, Bearer, or API Key
5. Add credentials if required
6. Click Test & List Tools
7. Enable tools
8. Click Save

Troubleshooting

OAuth Connection Fails

Problem: Popup closes without connecting

Solutions:

• Allow popups for app.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:

• ✅ Pro plan ($29/mo)
• ✅ Team plan ($99/mo)
• ✅ Business plan ($299/mo)
• ✅ Enterprise (custom pricing)

Individual service costs (separate from Chipp):

• Most services have free tiers
• Enterprise features may require paid plans
• Check each provider's pricing page

What's Next?

Need Help?

• 💬 Join Discord
• 📧 Email support@chipp.ai
• 📚 Browse all docs
• 🚀 Start building