could-have-been-email
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
mcp-could-have-been-email
could-have-been-email MCP — wraps StupidAPIs (keyless — no credential needed)
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
Tool | Description |
| 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. |
Related MCP server: mcp-meeting-analyzer
Quick Start
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"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/could-have-been-email/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/could_have_been_email_analyze \
-H 'Content-Type: application/json' \
-d '{"transcript":"Team standup: John reported completion of API integration. Sarah discussed Q4 roadmap priorities. Mike raised concern about database performance. Action: John to share API docs by Friday.","duration":15,"attendee_count":5,"recurring":true}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/could_have_been_email_analyze. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"could-have-been-email": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-could-have-been-email"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-could-have-been-emailIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Could Have Been Email data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Meeting transcripts & AI minutes for your agent: search, read, send meeting bots, import.
Google Meet meeting transcripts, summaries, and action items, plus a notetaker bot you can send.
Paste a transcript or document and get a structured summary with action items, plus slides and repor
Meeting transcripts for AI agents: search calls, read who said what, transcribe files and links.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA multi-agent system that analyzes meeting transcripts to generate summaries, extract key points, and identify actionable tasks through an easy-to-use web interface.-
- AlicenseNot gradedqualityDmaintenanceEnables efficient analysis of recorded meetings by transcribing audio, extracting only non-people frames (e.g., slides), and associating them with timestamps for compact LLM input.MIT
- AlicenseNot gradedqualityCmaintenanceEvaluates whether a meeting is worth attending, heavily weighted toward no, and provides time cost analysis, productivity impact, email viability score, and a polite decline template.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to analyze multi-speaker meeting transcripts from Tencent Meeting, Zoom, and Teams, extract explicit commitments, deadlines, and assignees, prioritize them using an Eisenhower urgency-importance matrix, and generate WeChat Work collaborative task cards.7MIT