tinysend
sign in

MCP server — tinysend agents

The tinysend MCP server is live. Agents in Claude, ChatGPT, Cursor, and similar tools can use tinysend as a built-in tool over the Model Context Protocol.

Endpoint

  • transport: streamable HTTP at https://mcp.tinysend.com (the bare root and /mcp both work)
  • auth: OAuth 2.1 for interactive clients (sign in once in the browser, no key pasting), or a static bearer token for scripts and CI — see below

Connect

Claude Code:

claude mcp add --transport http tinysend https://mcp.tinysend.com

The first time you connect, your browser opens to sign in at tinysend.com/signin, then a branded “Authorize access” consent screen. Approve it and you’re connected — no API key to copy. Discovery is automatic: the server returns a WWW-Authenticate header pointing at its protected-resource metadata, which names id.tinysend.com as the authorization server, with dynamic client registration and PKCE.

Any MCP client that supports OAuth over streamable HTTP works the same way: point it at the endpoint and complete the browser sign-in.

Scripts and CI

For non-interactive use, a static bearer token still works — pass it as a header and skip the browser flow entirely:

claude mcp add --transport http tinysend https://mcp.tinysend.com --header "Authorization: Bearer sk_..."

See agent authentication for how to get a token.

Tools

19 tools, mirroring the REST API:

  • newsletters: list_newsletters, get_newsletter, create_newsletter, get_newsletter_stats
  • subscribers: list_subscribers, add_subscriber, remove_subscriber
  • posts: list_posts, get_post, create_post, update_post, send_post, delete_post, get_post_delivery
  • contacts: list_contacts, get_contact, search_contacts, update_contact
  • usage: get_usage

Because the tools mirror the API, the API reference and the OpenAPI spec describe what each tool does.

Questions?

Contact us at hi@tinysend.com.