MCP Server for AI Assistants
The SealMetrics MCP Server enables AI assistants like Claude to access your analytics data through natural language queries. Ask questions about your marketing performance, traffic, conversions, and more — directly from your AI assistant.
What is MCP?
The Model Context Protocol (MCP) is an open standard that allows AI assistants to securely connect to external data sources. The SealMetrics MCP server acts as a bridge between Claude (or other MCP-compatible assistants) and your SealMetrics analytics data.
Features
Once connected, you can ask your AI assistant questions like:
- "How much traffic came from Google Ads yesterday?"
- "What's my ROAS for the last 30 days?"
- "Which landing pages are performing best?"
- "Show me conversion data by campaign"
- "Generate a conversion pixel for newsletter signups"
Available Capabilities
| Capability | Description |
|---|---|
| Traffic Analysis | Data segmented by source, medium, campaign, or geography |
| Conversion Tracking | Sales data with full attribution information |
| Microconversions | Engagement events like add-to-cart, signups, etc. |
| Funnel Analysis | Performance metrics across conversion stages |
| ROAS Evolution | Return on ad spend measurements over time |
| Landing Page Metrics | View counts and page effectiveness analysis |
| Pixel Generation | Create conversion tracking code for Google Tag Manager |
Installation
The SealMetrics MCP server is available as both an npm package (recommended) and a Python package.
Option 1: Using npx (Recommended)
No installation required. The package runs directly via npx:
npx -y @sealmetrics/mcp
Option 2: Using pip (Python)
pip install sealmetrics-mcp
Option 3: Using pipx (Python)
pipx installs the package in an isolated environment:
brew install pipx
pipx install sealmetrics-mcp
Configuration
Claude Desktop Setup
To connect the MCP server to Claude Desktop, modify the configuration file:
| Platform | Config File Location |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Choose the configuration that matches your preferred method:
Option A: npx Configuration (Recommended)
The simplest setup with no local installation required:
{
"mcpServers": {
"sealmetrics": {
"command": "npx",
"args": ["-y", "@sealmetrics/mcp"],
"env": {
"SEALMETRICS_API_TOKEN": "YOUR_API_TOKEN_HERE",
"SEALMETRICS_ACCOUNT_ID": "YOUR_ACCOUNT_ID_HERE"
}
}
}
}
Option B: pipx Configuration (Python)
First, find the path to the executable:
which sealmetrics-mcp
# Example output: /Users/YOUR_USER/.local/bin/sealmetrics-mcp
Then add this configuration using the full path:
{
"mcpServers": {
"sealmetrics": {
"command": "/Users/YOUR_USER/.local/bin/sealmetrics-mcp",
"args": [],
"env": {
"SEALMETRICS_API_TOKEN": "YOUR_API_TOKEN_HERE",
"SEALMETRICS_ACCOUNT_ID": "YOUR_ACCOUNT_ID_HERE"
}
}
}
}
Option C: uvx Configuration (Python)
{
"mcpServers": {
"sealmetrics": {
"command": "uvx",
"args": ["sealmetrics-mcp"],
"env": {
"SEALMETRICS_API_TOKEN": "YOUR_API_TOKEN_HERE",
"SEALMETRICS_ACCOUNT_ID": "YOUR_ACCOUNT_ID_HERE"
}
}
}
}
Replace YOUR_API_TOKEN_HERE and YOUR_ACCOUNT_ID_HERE with your actual credentials. Never commit these values to version control.
Post-Configuration Steps
- Save the JSON configuration file
- Restart Claude Desktop completely (Cmd+Q on macOS, then reopen)
- The SealMetrics tools will appear available in Claude Desktop
Environment Variables
| Variable | Required | Description |
|---|---|---|
SEALMETRICS_API_TOKEN | Yes* | Your API authentication token (recommended) |
SEALMETRICS_EMAIL | Yes* | Your SealMetrics email (alternative to token) |
SEALMETRICS_PASSWORD | Yes* | Your SealMetrics password (alternative to token) |
SEALMETRICS_ACCOUNT_ID | No | Default account ID (can be specified per query) |
*Authentication requires either SEALMETRICS_API_TOKEN OR (SEALMETRICS_EMAIL + SEALMETRICS_PASSWORD). The token method is preferred for security reasons.
Getting Your Credentials
API Token
Follow our guide to obtain your API token from the SealMetrics dashboard:
- Click on your profile icon in the top-right corner
- Select "Tags & Connectors"
- Navigate to the "Connectors" section
- Copy your API Token
For detailed instructions, see How to Obtain Your API Token.
Account ID
Your Account ID identifies which SealMetrics account to query. To find it:
- Use the Account Endpoints API to list all accounts linked to your credentials
- The response will include your Account ID(s) in this format:
{
"status": "ok",
"data": {
"000000000000000000001234": "Your Account Name"
}
}
The key (e.g., 000000000000000000001234) is your Account ID.
Usage Examples
Once configured, restart Claude Desktop and start asking questions:
Traffic Analysis
"Show me traffic from organic search for the last week"
Conversion Analysis
"What were my top converting campaigns last month?"
ROAS Tracking
"Compare ROAS between Google Ads and Facebook Ads"
Funnel Performance
"How many users reached checkout step 2 yesterday?"
Generate Tracking Code
"Create a conversion pixel for tracking newsletter signups"
Available Tools
The MCP server exposes eight main tools to the AI assistant:
| Tool | Description |
|---|---|
list_accounts | List all accounts linked to your credentials |
get_traffic | Retrieve traffic data with various filters |
get_conversions | Query conversion/sales data |
get_microconversions | Get engagement event data |
get_funnel | Retrieve funnel stage metrics |
get_roas_evolution | Track ROAS over time |
get_pages | Analyze landing page performance |
generate_pixel | Create conversion tracking code |
Troubleshooting
Claude doesn't see the MCP server
- Ensure the config file is in the correct location
- Verify JSON syntax is valid (use a JSON validator if needed)
- Restart Claude Desktop completely (Cmd+Q on macOS, not just close the window)
- For npx: ensure Node.js 18+ is installed
Test the Server Manually
You can test if the server runs correctly from the terminal:
# Using npx
SEALMETRICS_API_TOKEN="YOUR_API_TOKEN_HERE" npx -y @sealmetrics/mcp
# Using Python
SEALMETRICS_API_TOKEN="YOUR_API_TOKEN_HERE" ~/.local/bin/sealmetrics-mcp
Check Logs
Review Claude Desktop's MCP server logs for errors:
cat ~/Library/Logs/Claude/mcp-server-sealmetrics.log
Common Issues
| Problem | Solution |
|---|---|
| npx not found | Install Node.js 18+ from nodejs.org |
| Incorrect path | Run which sealmetrics-mcp to find the correct path (Python) |
| Invalid token | Verify your API token in the SealMetrics dashboard |
| Missing environment variables | Ensure SEALMETRICS_API_TOKEN is set in the config |
| Claude not restarted properly | Use Cmd+Q (macOS) or fully close and reopen Claude Desktop |
Authentication errors
- Verify your API token is correct
- Check that the token hasn't expired
- Ensure your account has API access enabled
No data returned
- Confirm your Account ID is correct
- Check that the date range contains data
- Verify the account has tracking data
Resources
- npm Package: npmjs.com/package/@sealmetrics/mcp
- PyPI Package: pypi.org/project/sealmetrics-mcp
- GitHub Repository: github.com/sealmetrics/mcp-server
- MCP Protocol: modelcontextprotocol.io
- API Documentation: SealMetrics API Reference
Support
Need help with the MCP server?
- GitHub Issues: Report bugs or request features
- Email: support@sealmetrics.com
- API Documentation: Full API reference