Wraps the StupidAPIs "Could Have Been Email" endpoint to analyze meeting transcripts and determine if they were a waste of everyone's time. Exposes a single tool that takes your transcript, counts filler words, extracts any actual decisions or action items, and generates a suggested email that could have replaced the whole thing. Requires an X-API-Key for authentication. Part of the Pipeworx gateway ecosystem, so you can either use it standalone or access it through their unified gateway alongside 673+ other data sources. Useful when you want to quantify meeting inefficiency or auto-generate post-meeting summaries that highlight how little actually happened.
could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 673+ live data sources.
| Tool | Description |
|---|---|
could_have_been_email_analyze | Check if a meeting transcript could have been an email instead. Returns filler word count, decisions made, action items, and a suggested email that would've replaced the meeting. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"could-have-been-email": {
"url": "https://gateway.pipeworx.io/could-have-been-email/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 673+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about Could Have Been Email data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
io.github.mindstone/mcp-server-microsoft-teams
com.mintmcp/outlook-email
helbertparanhos/resend-email-mcp
marlinjai/email-mcp
io.github.mindstone/mcp-server-email-imap
io.github.osamahassouna/email-playbook-mcp