humanic-mcp-server

This repo contains information about Humanic MCP server

Humanic MCP Server

The official MCP server for Humanic — an AI-native email marketing platform built for product-led growth teams. Connect Humanic directly to your AI tools and agents to create campaigns, manage audiences, and trigger email workflows programmatically from any MCP-compatible environment.

Overview

MCP (Model Context Protocol) is an open standard that lets AI models communicate with external tools and services in a standardized way. The Humanic MCP server acts as a bridge between your AI environment and your Humanic account — enabling AI agents to create, manage, and trigger email campaigns without ever opening the Humanic dashboard.

Whether you're using Claude, Cursor, or building a custom agentic workflow, the Humanic MCP server gives you full programmatic access to your Humanic organization.

Authentication

The Humanic MCP server supports two authentication methods:

Option 1 — Clerk OAuth (Recommended for personal use)

Connect directly by passing the MCP server URL into your MCP client. Humanic uses Clerk for authentication, so you'll be prompted to sign in via your existing Humanic account credentials. No API key required — your identity is verified through the OAuth flow.

Server URL:

https://mcp.humanic.ai/mcp

Use this method when connecting directly from tools like Claude.ai that support URL-based MCP connections with browser-based authentication.

Option 2 — API Key (Recommended for automation & production)

Generate an API key from the Humanic platform and pass it as a Bearer token in the Authorization header. This is the preferred method for automated workflows, CI/CD pipelines, and any headless integration where interactive browser login isn't feasible.

Server URL:

https://mcp.humanic.ai/mcp

Authorization Header:

Bearer YOUR_API_KEY

⚠️ Security note: API keys grant full organizational access to the Humanic MCP server. Store them securely — the plaintext value is shown only once at creation time. Never commit keys to source code or share them in plain text.

Generating an API Key

1. Open the Humanic dashboard and click your profile avatar in the bottom-left corner.
2. Select API Keys from the menu.
3. Click + New Key in the top-right corner.
4. Give your key a descriptive name (e.g., Claude Integration, Cursor Workflow).
5. Click Confirm — your key will be shown once. Copy it immediately and store it securely.
6. Use the key as the Bearer token when configuring your MCP connection.

Keys expire one year from creation. Create one key per integration so individual keys can be revoked without affecting other workflows.

Connecting to Your MCP Client

Claude (claude.ai)

In the Claude interface, navigate to Settings → Integrations → Add MCP Server and enter:

| Field | Value | |---|---| | Name | Humanic | | Server URL | https://mcp.humanic.ai/mcp | | Authorization Header | Bearer YOUR_API_KEY |

Once connected, Claude can use Humanic tools natively in conversation — create campaigns, query audience segments, or trigger email workflows directly from a prompt.

Claude Code

Via URL (API key):

claude mcp add humanic \
  --transport http https://mcp.humanic.ai/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor

Open Cursor Settings → MCP → Add new global MCP server and add the following to your config:

{
  "mcpServers": {
    "humanic": {
      "url": "https://mcp.humanic.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop

Open Claude Desktop → Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "humanic": {
      "url": "https://mcp.humanic.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Any MCP-Compatible Client

For any other MCP-compatible tool, the connection details are always the same:

| | | |---|---| | Protocol | Streamable HTTP | | Endpoint | https://mcp.humanic.ai/mcp | | Auth | Authorization: Bearer YOUR_API_KEY |

Refer to your tool's MCP documentation for the specific configuration format.

What You Can Do

Once connected, AI agents in your environment can interact with Humanic programmatically. Example capabilities include:

• Campaigns — Create, activate, pause, and monitor email campaigns
• Audiences — Query and segment users based on product behavior and cohort data
• Email generation — Prompt-based email creation with AI-driven personalization
• Analytics — Retrieve campaign performance data (open rates, click rates, deliverability)
• Contacts — Create and manage contact records and lifecycle stages
• Domains — Inspect sending domain configuration and deliverability status

Managing Your API Keys

All API keys are managed from the API Keys page in your Humanic dashboard.

| Action | How | |---|---| | Rename | Click the pencil icon next to any key | | Deactivate | Click Deactivate — this is immediate and permanent | | Delete | Click the trash icon to remove the key from your account |

The Last used timestamp on each key helps identify idle or unrecognized keys. Deactivate any key that is no longer in use or shows unexpected activity.

Security Best Practices

• Never commit API keys to source control. Use environment variables or a secrets manager.
• One key per integration. This way a single compromised key can be revoked without disrupting other workflows.
• Rotate keys regularly. Keys expire after one year; update your integrations before expiry to avoid downtime.
• Audit key usage. Review the API Keys page regularly and deactivate anything idle or unrecognized.
• If a key is compromised, deactivate it immediately from the API Keys page and generate a replacement.

Frequently Asked Questions

How many API keys can I create? There is no stated limit. The recommended approach is one key per integration.

What level of access does an API key grant? Each key grants full organizational access to the Humanic MCP server. Scoped or read-only keys are not currently available — treat every key as having full permissions.

What happens when a key expires? Keys expire one year from creation. Any integration using an expired key will lose access. Generate a new key and update your configuration before the expiration date.

Can I see what a key has been used for? The Last used field shows the most recent timestamp. For detailed activity logs, contact Humanic support.

What should I do if a key is compromised? Deactivate it immediately from the API Keys page and generate a replacement. Update all affected integrations as quickly as possible.

Resources

• Humanic Platform
• Humanic Documentation
• MCP Protocol Specification
• Getting Started Video Series
• WhatsApp Support

License

MIT