mcp-could-have-been-email

could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)

Part of Pipeworx — an MCP gateway connecting AI agents to 1394+ live data sources.

Tools

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.

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"
    }
  }
}

Or connect to the full Pipeworx gateway for access to all 1394+ data sources:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Using with ask_pipeworx

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.

More

• Docs and guides
• pipeworx.io

License

MIT