Templated
email.templatedPublished by templated.emailOfficial publisherv0.1.1Updated Oct 24, 2026
Create and manage Templated email templates from any MCP client - bring your own model.
Overview
Lets an assistant create and manage Templated email templates from any MCP client.
- What you can do
- Templated exposes its email-template service to MCP clients so an assistant can create and manage email templates. It is offered both as a remote streamable HTTP endpoint and as a local npm package that speaks stdio. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Useful when you build or maintain transactional or marketing email templates in Templated and want an assistant to work with them directly from your MCP client. Less relevant if you do not use Templated or only need to send one-off email.
- Requirements
- Either connect to the remote endpoint at app.templated.email or run the npm package @templatedemails/mcp locally over stdio, which needs Node.js. OAuth authentication is required, and a Templated API key (TEMPLATED_API_KEY, format tmpl_sk_...) from Integrations then API Keys. TEMPLATED_API_URL optionally overrides the API base URL.
Installation
In SourceWeft
- Open Templated in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/email.templated%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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"templated": {
"type": "http",
"url": "https://app.templated.email/api/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
60% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
