go-mcp-smtp
AGENTS.md0 starsChanged 3 months agoMITView on GitHub
This document describes the MCP server agents provided by the go-mcp-smtp project. go-mcp-smtp is an MCP (Model Context Protocol) server that enables sending email messages via the SMTP Submission protocol. It provides agents that can be integrated into AI systems to send emails programmatically. Purpose: Check connectivity and availability of the SMTP submission server. Output: - message: Status message indicating server availability Example Usage: Possible Responses: - Success: {"message": "smtp submission server is cooperating"} - Error: {"message": "error checking smtp…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Purpose: Check connectivity and availability of the SMTP submission server.
- Distinctive: line 110
Purpose: Run linting on the Go codebase and automatically fix any issues found.
- Distinctive: line 113
Verify required tools are available (go, gopls, staticcheck)
- Very specific: line 114
Run make lint to identify issues
- Distinctive: line 116
Verify fixes resolved all issues
- Very specific: line 129
Ensure required tools are available (make tools)
- Very specific: line 130
Ensure dependencies are downloaded (make deps)
- Very specific: line 131
Run vulnerability scan (make vuln)
- Very specific: line 133
Update vulnerable modules using go get
- Distinctive: line 143
Purpose: Run unit tests for the project.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
go-mcp-smtp Agents
This document describes the MCP server agents provided by the go-mcp-smtp project.
Overview
go-mcp-smtp is an MCP (Model Context Protocol) server that enables sending email messages via the SMTP Submission protocol. It provides agents that can be integrated into AI systems to send emails programmatically.
Available Agents
Ping
Purpose: Check connectivity and availability of the SMTP submission server.
Input: None
Output:
message: Status message indicating server availability
Example Usage:
{
"tool": "ping",
"input": {}
}Possible Responses:
- Success:
{"message": "smtp submission server is cooperating"} - Error:
{"message": "error checking smtp submission server: <error details>"}
SendRawEmail
Purpose: Send a raw email message through the SMTP submission server.
Input:
recipients: List of recipients in format "Name email@domain.com" (comma-separated)subject: Subject of the email message (8bit ANSI encoding)body: Message body in plain text without any formatting
Output:
message: Status message indicating message acceptance
Example Usage:
{
"tool": "sendRawEmail",
"input": {
"recipients": "John Doe <john@example.com>, Jane Smith <jane@example.com>",
"subject": "Test Message",
"body": "This is a test email sent via go-mcp-smtp."
}
}Possible Responses:
- Success:
{"message": "message is accepted by submission server"} - Error:
{"message": "error sending message: <error details>"}
SendMarkDownWithAttachmentsEmail
Purpose: Send a markdown email message through the SMTP submission server with content rendered from markdown and optional attachments.
Input:
recipients: List of recipients in RFC 5322 format like "John Doe john.doe@example.com"subject: Subject of the email message (8bit ANSI encoding)markdown: Message body in GitHub flavored markdown formatattachments: List of absolute file paths to attachment files (optional)
Output:
message: Status message indicating message acceptance
Example Usage:
{
"tool": "sendMarkDownWithAttachmentsEmail",
"input": {
"recipients": "John Doe <john.doe@example.com>",
"subject": "Hello from Markdown",
"markdown": "**Hello World!**\n\nThis is a test of markdown rendering.",
"attachments": ["/path/to/file.pdf"]
}
}Possible Responses:
- Success:
{"message": "message is accepted by submission server"} - Error:
{"message": "error sending message: <error details>"}
Configuration
The MCP server requires configuration via command-line arguments when starting:
--network: Network type (tcp, unix, etc.)--address: SMTP server address with port (e.g., smtp.example.org:587)--host: SMTP server hostname--helo: HELO/EHLO hostname--username: SMTP authentication username--password: SMTP authentication password--from: Default sender email address--start_tls: Whether to use STARTTLS (true/false)--verbose: Use verbose mode
See the README.md for a complete configuration example.
Available Skills
lint
Purpose: Run linting on the Go codebase and automatically fix any issues found.
Usage:
- Verify required tools are available (go, gopls, staticcheck)
- Run
make lintto identify issues - Analyze lint output and apply fixes
- Verify fixes resolved all issues
Dependencies:
- Go compiler (go)
- Go language server (gopls)
- Staticcheck tool
- Make build system
vuln-scan
Purpose: Scan the codebase for known vulnerabilities using govulncheck.
Usage:
- Ensure required tools are available (
make tools) - Ensure dependencies are downloaded (
make deps) - Run vulnerability scan (
make vuln) - Identify vulnerable modules from the report
- Update vulnerable modules using
go get - Re-run
make depsandmake vulnto verify resolution
Dependencies:
govulnchecktool- Go 1.26+
- Internet access to fetch vulnerability database
run-tests
Purpose: Run unit tests for the project.
Usage:
make test: Run all tests with verbose outputmake cover: Run tests with coverage reportingmake check: Run linting before tests
Prerequisites:
- Required tools:
make tools - Dependencies:
make deps
Additional Options:
make cover: Generate test coverage reportmake check: Run linting before executing tests
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

