Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
Run one of the commands below, then add the client config underneath.
npmnpx -y @markmnl/fmsg-mcpStreamable HTTPhttps://{oauth_mcp_endpoint}Streamable HTTPhttps://{api_key_mcp_endpoint}
Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.
mcpServers{
"mcpServers": {
"fmsg-mcp": {
"command": "npx",
"args": [
"-y",
"@markmnl/fmsg-mcp"
]
}
}
}
fmsg is listed in the Developer Tools category of the MCPNav directory. It is distributed as npm, Streamable HTTP and can be loaded by any client that speaks the Model Context Protocol.
Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.
fmsg is an MCP server by markmnl. Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
Install it with: npx -y @markmnl/fmsg-mcp. Then add the JSON config to your client's MCP settings and restart the client.
The MCP server itself is free to install. The source is public on https://github.com/markmnl/fmsg-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.
Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.