Kraiter

Created By
3 months ago
Kraiter is an email automation platform with an MCP server published on npm (@kraiter/mcp-server, v0.3.4). It exposes 62 tools for managing contacts, drip campaigns, transactional sends, segments, templates, domains, and metrics — all via natural language.
Overview

@kraiter/mcp-server
TypeScript icon, indicating that this package has built-in type declarations

0.3.4 • Public • Published

@kraiter/mcp-server

Model Context Protocol (MCP) server for the Kraiter email platform. Lets Claude and other AI assistants manage contacts, send emails, run sequences, and more — via natural language.

Installation

npm install -g @kraiter/mcp-server

Configuration

The server requires a KRAITER_API_KEY environment variable. Generate one from Settings in the dashboard.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "kraiter": {
      "command": "npx",
      "args": ["-y", "@kraiter/mcp-server"],
      "env": {
        "KRAITER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Claude Code

claude mcp add kraiter -- npx -y @kraiter/mcp-server

Then set the environment variable in your project's .claude/settings.json:

{
  "env": {
    "KRAITER_API_KEY": "your-api-key-here"
  }
}

Or add the full server config manually:

{
  "mcpServers": {
    "kraiter": {
      "command": "npx",
      "args": ["-y", "@kraiter/mcp-server"],
      "env": {
        "KRAITER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "kraiter": {
      "command": "npx",
      "args": ["-y", "@kraiter/mcp-server"],
      "env": {
        "KRAITER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json or via Cursor Settings > MCP:

{
  "mcpServers": {
    "kraiter": {
      "command": "npx",
      "args": ["-y", "@kraiter/mcp-server"],
      "env": {
        "KRAITER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Available tools (62)

ResourceToolsDescription
Contacts12Create, read, update, delete, upsert contacts; list sends, sequences, segments, and timeline
Events3Track events and list event history
Templates7Upsert email templates, preview renders, and manage versions
Sequences10Upsert drip campaigns, manage contact enrolment, versions, and dry runs
Campaigns9Organise sequences and templates into campaigns
Segments5Define and manage audience segments
Domains5Register and verify sending domains
Send4Send transactional emails and view send history
Scheduled Sends2List and inspect scheduled sends
Metrics5Tenant, sequence, and template metrics

Example usage

Once configured, you can ask Claude things like:

Documentation

Full documentation is available at kraiter.com/docs/mcp-server.

Licence

MIT

Server Config

{
  "mcpServers": {
    "kraiter": {
      "command": "npx",
      "args": [
        "-y",
        "@kraiter/mcp-server"
      ],
      "env": {
        "KRAITER_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
2 months ago
Author Name
-
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago