Samva MCP

dev.samvaPublished by samva.devOfficial publisherv1.0.0Updated Oct 24, 2026

Authenticated Samva email tools, including public documentation and template discovery.

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Authenticated Samva MCP server for email work: sending transactional email, templates, delivery events and signed webhooks, plus public docs discovery.

What you can do
  • Discover Samva public documentation, cookbooks and agent plugins
  • Find and work with email templates, including TSX template projects
  • Send transactional email and connect auth email flows
  • Handle delivery events and verify signed webhooks
  • Look up package integrations and runnable examples
When to use it
Useful when an assistant helps build or operate Samva email integrations — transactional sends, auth email callbacks, template rendering and publishing, or webhook verification — and needs the current docs and templates at hand.
Requirements
A remote streamable HTTP endpoint at mcp.samva.dev; OAuth authentication is required. No environment variables or headers are declared. The README's local monorepo workflow (Bun, Turborepo) applies to the open-source repository, not to connecting the hosted server.
Before you install
Access is tied to an authenticated Samva account via OAuth, so the assistant acts with that account's permissions. Sending email and handling delivery or webhook events affect real recipients and production flows; review any send or publish action before it runs. The README notes the 0.x SDK line (0.33) is the only maintained integration target.

Installation

In SourceWeft

  1. Open Samva MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.samva%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "samva": {
      "type": "http",
      "url": "https://mcp.samva.dev/"
    }
  }
}

README

Samva

Open-source packages, examples, cookbooks, and agent plugins for integrating Samva into real applications.

Use these to send transactional email, connect auth email flows, work with templates, handle delivery events, and verify signed webhooks. Ask questions about the code on DeepWiki.

Structure

  • packages/* — package integrations (@samva/*).
  • examples/* — complete, runnable example apps.
  • cookbooks/*.md — documentation-first, copy-pasteable recipes.
  • plugins/* — coding-agent plugins and public documentation.

While Samva is 0.x, the maintained integrations support only the current SDK minor: 0.33. Workspace packages require samva@^0.33.0 as a peer and test against 0.33.0. Examples use samva@^0.33.0; copyable external import maps pin [email protected].

Package integrations

Agent plugins

  • samva — OpenAI Codex and Cursor packaging for the canonical hosted MCP server and Samva agent skill.
  • Samva in ChatGPT — the published ChatGPT plugin is a separate listing from the Codex and Cursor package; the guide covers connecting one organization and a read-only first check.

Cookbooks

Integrations land as individual pull requests. See CONTRIBUTING.md to propose or build one.

Examples

  • astro-email — Astro Action and JSON endpoint on Cloudflare Workers.
  • better-auth-nextjs — Better Auth callbacks in a Next.js App Router application.
  • clerk-webhook — Clerk webhook verification and transactional email in Next.js.
  • effect-sdk — Email sends through the samva/effect SDK entrypoint.
  • email-sdk — Email SDK sends through the provider-owned Samva community adapter.
  • hono-cloudflare-workers — Hono Worker with a JSON email endpoint.
  • inbound-email-replies — receives an inbound reply, verifies the signed webhook, and answers in-thread.
  • mailbox-agent — an agent that follows a mailbox event stream and replies in approval mode, plus the same behavior as an @samva/mailbox webhook extension.
  • nextjs-transactional — App Router contact form plus /api/send route handler using the Samva SDK.
  • react-email-samva — React Email rendering and delivery through Samva.
  • supabase-auth-hook — Supabase Auth Send Email Hook implemented as an Edge Function.
  • sveltekit-transactional — SvelteKit form action and raw email endpoint.
  • tanstack-start-transactional — TanStack Start server function and server route.
  • tsx-template-samva — a defineTemplate email project: check, render, preview, and publish with the Samva CLI.

Getting started

This is a Bun + Turborepo monorepo.

sh
bun installbun run buildbun run typecheckbun run testbun run lintbun run format:check

Related open source

  • SML — the markup, Vite plugin, and editor behind Samva's TSX templates.
  • DomainKit — Samva sets up customer domains with DomainKit. See how it works.

Contributing

Contributions are welcome — see CONTRIBUTING.md for local setup, package conventions, and how to propose a new integration. Maintainers use the Tegami release flow for package versions, changelogs, npm publication, tags, and GitHub Releases. GitHub Actions publishes; merging the Version Packages pull request is the human gate.

Security

To report a vulnerability, see SECURITY.md. Please do not file public issues for security reports.

License

MIT © Arya Labs, Inc.

Source: README.md at commit 5e8d058

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts