> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senderkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Use SenderKit from AI agents over the Model Context Protocol.

The SenderKit MCP server lets an AI assistant — Claude, Cursor, Windsurf, or any
other [MCP-compatible client](/mcp/installation) — operate SenderKit through tool
calls. Once connected, an agent can send a test notification, scaffold and edit
templates, and inspect message delivery without ever leaving your editor or chat.

## Who it's for

* **Developers using AI coding tools.** Wire SenderKit into your assistant once;
  after that, "send the welcome email to [user@example.com](mailto:user@example.com)" is one line in the chat.
* **Agent authors.** Building an autonomous workflow that needs to send
  notifications? Point it at SenderKit over MCP and let it dispatch through the
  same templates and key prefixes your app already uses.

## What you can do with it

The server exposes a small surface that mirrors SenderKit's main operations:

* **Send** a templated message, or [raw inline content](/concepts/sending#template-sends-and-raw-sends),
  to one recipient.
* **List and inspect [templates](/concepts/templates)** by slug.
* **Query and cancel [messages](/concepts/messages)** — list recent sends with
  filters, fetch a single message, or cancel a still-pending one.
* **Check your connection mode** with `senderkit_context` — confirm whether the
  active connection is live or test before sending.

All in [test mode by default](/concepts/environments) — use an `sk_test_` key and
your assistant can experiment without anything leaving the building.

## How it runs

Three ways to connect:

<CardGroup cols={3}>
  <Card title="OAuth" icon="key">
    Connect from Claude (web, desktop, mobile) or any OAuth-compatible MCP
    client — no API key needed. Sign in and pick a workspace + mode.
  </Card>

  <Card title="Hosted (API key)" icon="cloud">
    Point your client at `https://mcp.senderkit.com`. Auth is
    `Authorization: Bearer <key>`. SenderKit runs the server.
  </Card>

  <Card title="Local (stdio)" icon="terminal">
    Run `senderkit mcp` from the [CLI](/cli/installation) — a stdio MCP server
    that reads `SENDERKIT_API_KEY` from your environment.
  </Card>
</CardGroup>

The hosted and local options are API-key authenticated and behave identically —
pick whichever fits your setup. OAuth is for clients that handle auth themselves
rather than accepting a custom header.

<CardGroup cols={3}>
  <Card title="Quickstart" icon="bolt" href="/mcp/quickstart">
    Connect Claude Code and make your first tool call.
  </Card>

  <Card title="Installation" icon="plug" href="/mcp/installation">
    Config for every supported client.
  </Card>

  <Card title="Tools" icon="screwdriver-wrench" href="/mcp/tools">
    The full surface, parameter by parameter.
  </Card>
</CardGroup>