Claude MarketplacesSubmit
pipeworx-io avatar

Could Have Been Email

pipeworx-io/mcp-could-have-been-email

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.

tool
1
transport
HTTP
last updated
Oct 24, 2026
View on GitHub

Tools

1 tools

Public tool metadata for what this MCP can expose to an agent.

could_have_been_email_analyzeCheck 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.

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.

No parameter schema in public metadata yet.

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Readme

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

ToolDescription
could_have_been_email_analyzeCheck 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.

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

View the full README on GitHub

Details

Repository
github.com/pipeworx-io/mcp-could-have-been-email
Website
pipeworx.io/packs/could-have-been-email
Category
Communication & Messaging
Transport
HTTP
Registry
MCP registry, active

More from pipeworx-io

Related Communication & Messaging MCP servers

View all
1pipeworx-io avatarOutlook Contactspipeworx-io/mcp-outlook-contactsOutlook Contacts (Microsoft 365) MCP Pack0stars
2pipeworx-io avatarSlack_connectpipeworx-io/mcp-slack_connectSlack MCP Pack0stars
3kay0k1 avatarTelegram Devkay0k1/telegram-devCurrent official Telegram and TON docs: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk0stars
4mambalabsdev avatarMcp Youtube Channel Email Findermambalabsdev/mcp-youtube-channel-email-finderEmails YouTube channels publish in plain text, with the source of each address0stars
5mifactory-bot avatarMifactory Emailmifactory-bot/mifactory-emailSend transactional emails for AI agents via SMTP. Templates included.0stars
6openses-email avatarMcp Serveropenses-email/mcp-serverOpenSES email on your own Amazon SES: shared inbox, sending, delivery status, contacts, sequences.0stars