A binary message definition and protocol where messages are relational and verifiable by all peers. Messages are sent via a fmsg host to one or more recipients. Each message in a thread is linked to the previous using a cryptographic hash forming a directed acyclic graph.
This repository serves as a host and index for fmsg related documents listed below, including the white paper, specification and standards.
Website: https://fmsg.org
| Document | Short Description |
|---|---|
| IMPLEMENTATIONS.md | List of fmsg implementations including ancillary services, APIs and apps. |
| SPECIFICATION.md | Core fmsg specification describing message communication between fmsg hosts. |
| STANDARDS.md | Common standards surrounding fmsg setups such as API contracts. |
| FMSG_WHITE_PAPER.pdf | Paper introducing fmsg including motivations and overview. |
Any MCP-capable agent (Claude Code, Claude Desktop, Cursor, VS Code and others) can get its own fmsg address with fmsg-mcp, the reference implementation of FMSG-007:
claude mcp add fmsg --scope user \
--env FMSG_API_URL=https://api.example.com \
--env FMSG_API_KEY=fmsgk_... \
-- npx -y @markmnl/fmsg-mcpThe same server can run as a hosted endpoint where each user connects with their own API key. Agents that speak A2A can use the FMSG-004 binding instead.