Visit @nitrosend/mcpOptional stdio bridge to Nitrosend’s remote MCP server for clients without native HTTP transport.
About @nitrosend/mcp
This is an optional stdio bridge to Nitrosend's remote MCP server, for clients that cannot connect to a remote server directly. The README says Nitrosend is an email marketing platform and that most clients should connect to the remote server instead. It is published under the nitrosend organisation, and the details come from the README.
The README names tools for checking status, selecting an account or brand, editing a brand kit and uploading images. It describes wider capabilities such as composing emails and flows, managing contacts and segments, running spam checks and test sends, and viewing engagement insights. The bridge needs Node.js 18 or later and either an API key or an OAuth bearer token. Remote setup uses browser sign-in, and the README gives steps for several clients. The licence is MIT.
Key features
- Stdio bridge to remote server
- Account and brand selection
- Brand kit editing
- Email and flow composition
- Contacts and segments
More other MCP servers
- Other

Mcp Proxy
sparfenyuk
A bridge between Streamable HTTP and stdio MCP transports
2.8K GitHub starsPythonMIT - Other

Mcp Remote
punkpeye
Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server.
1.7K GitHub starsTypeScriptMIT - Other

Kanzo
emanuele-em
Self-hosted, sharable kanban for humans and agents. One 4.5 MB binary, 4.5 MB of RAM, 10 to 60 tokens per agent reply, starts in 2 ms, zero setup.
1.2K GitHub starsRustAGPL-3.0 - Other

mcptoon
activeing123
MCP tool discovery burns 71,929 tokens. mcptoon drops it to 581 (−99.2%, measured). Zero dependencies.
431 GitHub starsPythonApache-2.0 - Other

automcp
NapthaAI
Easily convert tool, agents and orchestrators from existing agent frameworks to MCP servers
303 GitHub starsPythonApache-2.0