Skip to main content

Overview

Connect your favorite tools and platforms directly to Migma using Model Context Protocol (MCP). Pull content automatically from Notion, Shopify, Linear, Stripe, and 20+ other services to generate data-driven, personalized emails.

26+ Integrations

Connect e-commerce, CRM, databases, and more

Pull Live Data

Access real-time data from connected tools

Automate Emails

Generate emails from your existing workflows

What is MCP?

Model Context Protocol (MCP) is an open standard that allows AI systems to securely access external tools and data sources. Migma uses MCP to connect with your productivity tools and pull content for email generation. Key Benefits:
  • No manual data entry - Pull content directly from your tools
  • Always up-to-date - Access live data when generating emails
  • Secure connections - OAuth 2.0 authentication for all integrations
  • Read-only access - Migma can view but not modify your data

Available MCP Servers

Migma supports 26 MCP servers across different categories:

E-commerce & Sales (7 servers)

Access:
  • Product catalog and inventory
  • Customer information
  • Order history and analytics
  • Store metrics
Use cases:
  • Product launch emails with live inventory
  • Order confirmation emails
  • Customer win-back campaigns
  • Sales performance reports
Authentication: OAuth 2.0
Access:
  • Email marketing data
  • Subscriber profiles and segments
  • Campaign performance metrics
  • Email templates and flows
Use cases:
  • Import existing email templates
  • Sync subscriber segments
  • Analyze campaign performance
  • Migrate email content
Authentication: OAuth 2.0
Access:
  • Products and invoices
  • Transaction history
  • Payment details and refunds
  • Subscription management
  • Dispute information
  • Shipment tracking
Use cases:
  • Payment confirmation emails
  • Invoice reminders
  • Transaction summaries
  • Refund notifications
Authentication: OAuth 2.0
Access:
  • Transaction data
  • Customer profiles
  • Inventory tracking
  • Payment processing
  • Sales analytics
Use cases:
  • Receipt emails
  • Customer loyalty campaigns
  • Sales reports
  • Inventory alerts
Authentication: OAuth 2.0
Access:
  • Customer data
  • Payment intents and invoices
  • Products and prices
  • Subscriptions and billing
  • Disputes and refunds
  • Balance information
Use cases:
  • Payment confirmations
  • Subscription updates
  • Invoice notifications
  • Failed payment recovery
Authentication: OAuth 2.0
Access:
  • Website content
  • E-commerce products
  • Site analytics
  • Booking data
Use cases:
  • Website update announcements
  • Product promotional emails
  • Booking confirmations
  • Site analytics reports
Authentication: OAuth 2.0
Access:
  • Lead and opportunity data
  • Contact information
  • Campaign metrics
  • Sales reports
Use cases:
  • Lead nurture emails
  • Sales pipeline updates
  • CRM-driven campaigns
  • Account-based marketing
Authentication: OAuth 2.0 Setup: Requires mcpverse.dev configuration

Productivity & Collaboration (5 servers)

Access:
  • Pages and databases
  • Notes and documentation
  • Content calendars
  • Team wikis
Use cases:
  • Newsletter from content calendar
  • Product updates from roadmap
  • Team updates from Notion docs
  • Documentation-based emails
Authentication: OAuth 2.0
Access:
  • Jira issues and projects
  • Confluence pages and spaces
  • Comments and discussions
  • Project metadata
Use cases:
  • Sprint recap emails
  • Release notes from Jira
  • Documentation updates
  • Team status reports
Authentication: OAuth 2.0
Access:
  • Issues and projects
  • Team workflows and cycles
  • Project documentation
  • Issue statuses and labels
Use cases:
  • Sprint updates
  • Bug fix announcements
  • Feature release emails
  • Project milestone reports
Authentication: OAuth 2.0
Access:
  • Channel messages
  • User information
  • Message search
  • Workflow data
Use cases:
  • Channel digest emails
  • Team communication summaries
  • Important message highlights
  • Slack-to-email notifications
Authentication: OAuth 2.0 Setup: Requires mcpverse.dev configuration
Access:
  • Tasks and projects
  • Labels and filters
  • Project hierarchy
  • Task metadata
Use cases:
  • Task reminder emails
  • Project progress reports
  • Weekly task summaries
  • Team task assignments
Authentication: OAuth 2.0 Setup: Requires mcpverse.dev configuration

Development & Code (3 servers)

Access:
  • Repositories and code
  • Issues and pull requests
  • Commits and branches
  • Code search
Use cases:
  • Release announcement emails
  • Code review summaries
  • Issue digests
  • Changelog emails
Authentication: OAuth 2.0
Access:
  • Error and issue tracking
  • Project information
  • Release data
  • Event details and attachments
  • Root cause analysis
Use cases:
  • Bug report emails
  • Error digest summaries
  • Incident notifications
  • Release stability reports
Authentication: OAuth 2.0
Access:
  • Design files and projects
  • Asset exports
  • Design comments
  • Project collaboration data
Use cases:
  • Design review emails
  • Asset delivery notifications
  • Design update announcements
  • Feedback compilation
Authentication: OAuth 2.0 Setup: Requires mcpverse.dev configuration

Design & Creative (2 servers)

Access:
  • Design search and browsing
  • Design pages and content
  • Folder management
  • Design generation
  • Export capabilities
Use cases:
  • Email with Canva-generated images
  • Design approval workflows
  • Brand asset emails
  • Creative collaboration
Authentication: OAuth 2.0
Access:
  • Site management
  • CMS content
  • Form submissions
  • Site analytics
Use cases:
  • Website update emails
  • Form submission notifications
  • CMS content emails
  • Site analytics reports
Authentication: OAuth 2.0

Databases (6 servers)

Access:
  • Database queries
  • Table management
  • Schema information
  • Query optimization
Use cases:
  • Data-driven email campaigns
  • Customer data emails
  • Report generation
  • Analytics emails
Authentication: Database credentials Setup: Requires mcpverse.dev configuration
Access:
  • SQL query execution
  • Table operations
  • Database backup
  • Performance optimization
Use cases:
  • Customer data extraction
  • Sales reports
  • Database-driven campaigns
  • Analytics summaries
Authentication: Database credentials Setup: Requires mcpverse.dev configuration
Access:
  • Base and record data
  • Table searches
  • Field values
  • Record relationships
Use cases:
  • CRM-based emails
  • Content calendar emails
  • Project status updates
  • Data-driven newsletters
Authentication: OAuth 2.0 Setup: Requires mcpverse.dev configuration
Access:
  • Serverless PostgreSQL database
  • Query execution
  • Database branching
  • Performance metrics
  • Backup data
Use cases:
  • Modern app data emails
  • Analytics reports
  • User data campaigns
  • Performance notifications
Authentication: OAuth 2.0
Access:
  • Vector database queries
  • Semantic search
  • Similarity matching
  • Collection management
  • Index statistics
Use cases:
  • AI-powered recommendations
  • Similar product emails
  • Content discovery
  • Personalized suggestions
Authentication: API key Setup: Requires mcpverse.dev configuration

Customer Support & Communication (1 server)

Access:
  • Customer conversations
  • Support tickets
  • User profiles and data
  • Conversation search
Use cases:
  • Support digest emails
  • Customer feedback summaries
  • Ticket status updates
  • Customer insight reports
Authentication: OAuth 2.0

Data & Analytics (2 servers)

Access:
  • Real-time crypto prices
  • Market data and trading volume
  • Trending coins
  • Exchange information
  • NFT data
Use cases:
  • Crypto price alerts
  • Market update emails
  • Portfolio reports
  • Trading insights
Authentication: OAuth 2.0
Access:
  • Knowledge base search
  • Information extraction
  • Documentation queries
  • Insight generation
Use cases:
  • Knowledge base emails
  • Documentation digests
  • Research summaries
  • Information reports
Authentication: OAuth 2.0

Infrastructure (1 server)

Access:
  • Static site management
  • Edge functions
  • CDN analytics
  • Domain configuration
Use cases:
  • Deployment notifications
  • Performance reports
  • Site status emails
  • Analytics summaries
Authentication: OAuth 2.0

Setup MCP Connections

Standard OAuth Setup (Most Servers)

Most MCP servers use direct OAuth 2.0 authentication:
1

Navigate to Integrations

Go to Settings → Integrations → MCP Servers
2

Select Server

Click “Connect” button for your desired server
3

Authorize Access

Sign in to the service and authorize Migma to access:
  • Specific workspaces/accounts
  • Read-only permissions
  • Required data scopes
Permissions are minimal - Migma requests only what’s needed
4

Configure Scope

Choose what Migma can access:
  • All data
  • Specific projects/folders
  • Selected resources only
5

Test Connection

Click “Test Connection” to verify setup works
6

Start Using

Data now available when creating emails

MCPverse.dev Setup (Some Servers)

Some servers require additional configuration through mcpverse.dev: Servers requiring mcpverse.dev:
  • Slack
  • PostgreSQL
  • MySQL
  • Airtable
  • Salesforce
  • Figma
  • Todoist
  • Pinecone
1

Create MCPverse Account

Visit mcpverse.dev and sign up
2

Add Server

Select the server you want to connect (e.g., Slack, PostgreSQL)
3

Configure Credentials

Enter required credentials:
  • API keys
  • Database connection strings
  • OAuth tokens
  • Server endpoints
4

Get MCP URL

MCPverse generates a hosted MCP server URL
5

Connect to Migma

In Migma Settings → Integrations → MCP Servers:
  • Click “Add Custom Server”
  • Paste the MCPverse URL
  • Test connection

Using MCP in Email Creation

Method 1: Direct Reference

Reference specific resources directly in prompts:
  • Notion
  • Shopify
  • Linear
  • Stripe
Create a newsletter from my Notion page:
notion://page/abc123-notion-page-id

Extract:
- Main headlines
- Key updates
- Action items

Format as professional email newsletter

Method 2: Search and Pull

Let Migma search your connected tools:
Search my Notion workspace for "Q4 Product Updates"
and create a product announcement email from that content
Find Linear issues completed in the last week
and generate a "What We Shipped" email
Get my top 10 selling Shopify products this month
and create a "Bestsellers" promotional email

Method 3: Database Queries

Pull structured data from databases and tools:
Query my Notion "Blog Posts" database for posts tagged "Featured"
published in the last 30 days, and create a newsletter
highlighting these articles with summaries
From Airtable "Customer Feedback" base,
get all 5-star reviews from this month
and create a testimonial email

Real-World Workflows

Newsletter from Notion Content Calendar

Notion Setup:
  • Database: “Content Calendar”
  • Properties: Title, Status, Publish Date, Category
Migma Prompt:
Create newsletter from my Notion "Content Calendar" database

Include articles from the last week marked as "Published"
Group by category
Add brief summary for each article
Include "Read More" links
Professional, engaging tone
Result: Automated weekly newsletter from Notion content

Product Launch Email from Shopify

Shopify:
  • Products tagged “Launch Q1 2024”
Migma Prompt:
Create product launch email for Q1 2024 collection

Pull from Shopify:
- Products tagged "Launch Q1 2024"
- Include product images
- Show pricing
- Add inventory status

Exciting, premium brand voice
Include "Shop Now" CTAs

Sprint Update from Linear

Linear:
  • Current sprint in “Engineering” team
Migma Prompt:
Create sprint update email from Linear

Team: Engineering
Cycle: Current sprint

Sections:
1. What We Shipped (completed issues)
2. In Progress (active issues)
3. Coming Next (planned issues)

Include issue titles and descriptions
Internal team tone

Payment Failed Email from Stripe

Stripe:
  • Failed payment intents
Migma Prompt:
Create payment retry email for failed subscription

Customer: [customer_id]
Subscription: [subscription_id]

Include:
- Amount that failed
- Retry instructions
- Update payment method link
- Support contact

Helpful, non-alarming tone

Advanced MCP Features

Multi-Source Content

Combine data from multiple MCP servers:
Create quarterly update email using:

1. Notion page: "Q4 Summary" - Company highlights
2. Shopify: Sales data for Q4
3. Linear: Engineering milestones completed
4. Stripe: Revenue growth metrics

Synthesize into cohesive quarterly update
Executive audience
Professional tone

Conditional Logic

Use smart queries with conditions:
From Shopify, get products where:
- Inventory less than 10 units
- Price over $100
- Category = "Premium"

Create "Last Chance" email for these low-stock premium items

Security & Permissions

Permission Management

Migma requests minimal permissions:Read-Only Access:
  • View content and data
  • Search and query
  • Access metadata
Cannot:
  • Modify files or data
  • Delete content
  • Share with others
  • Change settings
How Migma handles your data:
  • Content pulled only when requested
  • No permanent storage of source data
  • Used only for email generation
  • Not shared with third parties
  • Deleted after email creation
  • Encrypted in transit (HTTPS)
Your data stays yours
To disconnect MCP servers:
  1. Go to Settings → Integrations → MCP Servers
  2. Find connected server
  3. Click “Disconnect”
  4. Confirm disconnection
Also revoke in source service:
  • Check service’s connected apps settings
  • Remove Migma authorization

Best Practices

Connect only what you need - Only link necessary accounts and folders
Use specific IDs - Reference exact page/resource IDs for reliability
Test connections regularly - Ensure OAuth tokens remain valid
Be specific in prompts - Clear instructions get better results
Review before sending - Always review MCP-generated content
Refresh stale data - Migma caches for 5 minutes; refresh if needed

Troubleshooting

Problem: MCP server won’t connectSolutions:
  1. Re-authorize OAuth connection
  2. Check permissions granted
  3. Verify correct account selected
  4. Try disconnecting and reconnecting
  5. Check service status (not down)
Problem: Migma can’t find resourceSolutions:
  • Verify resource exists in connected account
  • Check sharing permissions
  • Use direct resource ID instead of search
  • Ensure not deleted or archived
  • Verify correct workspace/project
Problem: Email shows old dataSolutions:
  • Migma caches for 5 minutes
  • Click “Refresh” before generating
  • Wait a few minutes after updating source
  • Clear connection and reconnect
Problem: Access denied to specific resourcesSolutions:
  • Grant Migma access in source service
  • Check workspace-level permissions
  • Verify OAuth scopes granted
  • Re-authorize with broader permissions
Problem: Can’t configure server through mcpverse.devSolutions:
  • Verify account created on mcpverse.dev
  • Check credentials are correct
  • Test connection in mcpverse.dev first
  • Ensure server URL is correct
  • Contact mcpverse.dev support

API Access

Automate MCP workflows via Migma API:
// Generate email from Notion page
const response = await fetch('https://api.migma.ai/v1/emails/generate', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    prompt: "Create newsletter from Notion page",
    mcpSources: [{
      type: "notion",
      pageId: "abc123-page-id"
    }],
    projectId: "your_project_id"
  })
});

API Documentation

Complete MCP API reference

Next Steps


Need Help?