Developer Tooling
SENDKIT
ROLE
SOLO BUILD — OSS MAINTAINER
TIMELINE
SHIPPED · v1.0.3 ON NPM
SCOPE
STACK
OVERVIEW
Messaging integrations are fragmented — every provider has its own API. SendKit wraps them behind one type-safe interface consumable three ways: as an SDK, an interactive CLI, or an MCP server that teaches AI agents to send messages themselves.
The core engine is strict TypeScript with Zod v4 validation over plain fetch, which keeps it zero-config and runnable on Vercel Edge, Cloudflare Workers, Deno, Bun and Node. Telegram ships first; Discord, Slack and SMTP follow the same provider contract.
The CLI (Commander + Clack) gives a guided setup wizard with secure token input, connectivity health checks and a polished terminal UI. The MCP layer runs two ways: a local stdio server for Cursor, Windsurf and Claude Desktop, and a remote Hono deployment on Vercel Edge secured with Clerk OAuth 2.0.
Built as a Bun monorepo with tsdown (Rolldown) builds, oxlint/oxfmt tooling, Conventional Commits, a security policy, and fifteen tagged releases — maintained like a real open-source product, because it is one.
OUTCOMES
npx sendkit init — thirty seconds later your agent can message you.