MCP reference

Overview

MailRaft tools use the same policy layer as the API. Tools include mailraft_list_messages, mailraft_read_message, mailraft_create_draft, mailraft_request_send, mailraft_request_campaign_start, mailraft_list_integrations, mailraft_test_integration, mailraft_call_integration and mailraft_get_operation.

Setup & requirements

Important sends and campaigns remain pending approval. Local allow/deny tests exist; a public remote MCP transport has not been deployed. Do not point a generic MCP client at a fabricated /mcp route or supply provider tokens.

Usage & verification

The supported transport is the repository stdio gateway. Set MAILRAFT_MCP_CONFIG to an owner-only JSON file containing api and a MailRaft token, then start node apps/mcp/server.mjs. Use https://api.mailraft.com as api. Never pass provider credentials or a token on the command line. A public /mcp route is not implemented.

Tools also include mailraft_list_leads and mailraft_prepare_campaign. Each invocation rechecks membership, scopes, quotas and revocation through /v1/call; a cached client session does not retain access after revocation. Tool content cannot approve itself. Campaign start and important sends return pending_approval.

Project code examples

Browse MailRaft source references and HTTP examples in Node.js, Python, Ruby, PHP, Go, Rust, Java, .NET, Elixir and cURL.