1msg MCP
Enables interaction with the 1msg Chat API through 60 public MCP tools, supporting stdio and hosted HTTP transports. It lets users leverage chat API functionality in Cursor, Claude Desktop, and other MCP clients.
README
@1msg/mcp
MCP server for the 1msg Chat API — 60 public tools for Cursor, Claude Desktop, and other MCP clients.
Transports: stdio (local) and Streamable HTTP (hosted).
| npm | @1msg/mcp |
| Hosted prod | https://mcp.1msg.io/mcp |
| Hosted stage | https://mcp.stage.1msg.io/mcp |
| SDK | @1msg/sdk |
Source of truth for codegen of
tools.generated.ts/handlers.generated.tsstill lives in the1msg-apimonorepo (packages/mcp). This repository is the distribution package for running and hosting the server.
Quick start
npx (stdio)
export ONE_MSG_BASE_URL=https://api.stage.1msg.io
export ONE_MSG_INSTANCE_ID=your-instance-id
export ONE_MSG_TOKEN=your-channel-token
npx -y @1msg/mcp
# or, after clone + build:
# npm start
Deprecated aliases still work: CHAT_API_BASE_URL, CHAT_API_TOKEN, CHAT_API_INSTANCE_ID.
Clone and run
git clone https://github.com/1msg/1msg-mcp.git
cd 1msg-mcp
npm install
npm run build
export ONE_MSG_BASE_URL=https://api.stage.1msg.io
export ONE_MSG_INSTANCE_ID=your-instance-id
export ONE_MSG_TOKEN=your-channel-token
npm start # stdio → dist/index.js
npm run start:http # Streamable HTTP → dist/http.js
Environment variables
| Variable | Required | Description |
|---|---|---|
ONE_MSG_BASE_URL |
yes (stdio) | API base, e.g. https://api.stage.1msg.io or https://api.1msg.io |
ONE_MSG_TOKEN |
yes (stdio) | Channel API token |
ONE_MSG_INSTANCE_ID |
yes (stdio) | Channel instance id |
MCP_HTTP_HOST |
no | HTTP bind host (default 0.0.0.0 in Docker) |
MCP_HTTP_PORT |
no | HTTP port (default 3100) |
MCP_RATE_LIMIT_RPM |
no | Per-token rate limit for HTTP (default 60) |
For hosted HTTP, upstream ONE_MSG_BASE_URL is set on the server; clients send credentials per request (see below).
Cursor (mcp.json)
Local stdio
{
"mcpServers": {
"1msg": {
"command": "npx",
"args": ["-y", "@1msg/mcp"],
"env": {
"ONE_MSG_BASE_URL": "https://api.stage.1msg.io",
"ONE_MSG_INSTANCE_ID": "your-instance-id",
"ONE_MSG_TOKEN": "your-channel-token"
}
}
}
}
Hosted URL (Streamable HTTP)
Prod: https://mcp.1msg.io/mcp · Stage: https://mcp.stage.1msg.io/mcp
{
"mcpServers": {
"1msg": {
"url": "https://mcp.1msg.io/mcp",
"headers": {
"Authorization": "Bearer your-channel-token",
"X-Instance-Id": "your-instance-id"
}
}
}
}
Header aliases: X-1msg-Instance-Id (and deprecated X-Chat-Api-Instance-Id). Do not commit real tokens.
Hosted HTTP locally
export ONE_MSG_BASE_URL=https://api.stage.1msg.io
export MCP_HTTP_PORT=3100
npm run start:http
- Auth:
Authorization: Bearer <token>+X-Instance-Id: <instanceId> - Health:
GET /healthz,GET /readyz
docker build -t 1msg/1msg-mcp-http:local .
docker run --rm -p 3100:3100 \
-e ONE_MSG_BASE_URL=https://api.stage.1msg.io \
1msg/1msg-mcp-http:local
Scripts
| Script | Purpose |
|---|---|
npm run build |
Compile TypeScript → dist/ |
npm test |
Jest unit tests |
npm run smoke:tools-list |
Stdio tools/list smoke (expects 60 tools; uses dummy token) |
npm start / npm run start:http |
Run stdio / HTTP servers |
Architecture
All Chat API HTTP goes through @1msg/sdk. See ARCHITECTURE.md.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.