fix-protocol-mcp
fix-protocol-mcp
MCP server for parsing, validating, building, and explaining FIX protocol messages - the tag=value format used for orders and executions across equities, FX, and fixed-income trading.
Runs fully offline. Parsing, validation (BodyLength/CheckSum included), message construction, and the bundled FIX 4.4 field dictionary are all self-contained, no external API or network calls.
Tools
Tool | What it does |
| Decode a raw FIX string into tag, field name, value, and enum meaning. Accepts SOH-, |
| Check field ordering, the standard header, BodyLength(9) and CheckSum(10) against computed values, and required/conditional fields per message type. Returns |
| Construct a valid FIX message from field inputs. Accepts tag numbers or field names, and enum codes or labels ( |
| Look up a tag's field name, data type, and enumerated values. |
Related MCP server: jPOS MCP Server
Install
pip install .This installs the fix-protocol-mcp console script (stdio MCP server).
MCP client config
{
"mcpServers": {
"fix-protocol": {
"command": "fix-protocol-mcp"
}
}
}Running from source instead of installing:
{
"mcpServers": {
"fix-protocol": {
"command": "python",
"args": ["-m", "fix_protocol_mcp.server"],
"env": { "PYTHONPATH": "src" }
}
}
}Examples
Parse a Logon message:
parse_fix_message("8=FIX.4.2|9=65|35=A|...|98=0|108=30|10=062|")
-> msg_type "A" (Logon), 10 fields, each decoded to name + value + enum meaningValidate, catching a bad checksum:
validate_fix_message("8=FIX.4.2|9=65|35=A|...|10=000|")
-> { "valid": false, "checksum": {"present":"000","computed":"062","ok":false},
"errors": ["CheckSum(10)=000 does not match computed checksum 062."] }Build an order from field names:
build_fix_message(
msg_type="NewOrderSingle",
fields={"Symbol":"AAPL","Side":"Buy","OrderQty":100,
"OrdType":"Limit","Price":"150.25","ClOrdID":"A1"})
-> 8=FIX.4.4|9=113|35=D|49=SENDER|56=TARGET|34=1|52=...|11=A1|38=100|
40=2|44=150.25|54=1|55=AAPL|60=...|10=061| (valid: true)Explain a tag:
explain_fix_tag(40)
-> { "name": "OrdType", "type": "CHAR",
"values": [{"value":"1","meaning":"Market"}, {"value":"2","meaning":"Limit"}, ...] }Coverage
The dictionary covers session-level messages and the order/execution workflow (Logon, Heartbeat, TestRequest, ResendRequest, Reject, SequenceReset, Logout, NewOrderSingle, OrderCancelRequest, OrderCancelReplaceRequest, ExecutionReport, OrderCancelReject), which accounts for most real FIX traffic. It's a curated subset rather than the full FIX repository - unrecognised tags and enum values surface as warnings, not hard failures.
Development
pip install -e ".[dev]"
pytestserver.py is a thin MCP wrapper around the core modules (parser,
validator, builder, dictionary, wire), which have no dependency on
the MCP SDK and can be used as a plain library:
from fix_protocol_mcp import parse, validate, build, describe_tagLicense
MIT - see LICENSE.
Available Tools
4 toolsbuild_fix_messageB
Build a FIX message from field names/values (e.g. Side='Buy'). BodyLength and CheckSum are computed.
Inputs: msg_type (required), fields, msg_seq_num, begin_string, +3 more.
explain_fix_tagA
Look up a FIX tag's field name, data type, and enumerated values.
Inputs: tag (required).
parse_fix_messageA
Decode a raw FIX message (SOH, '|', or '^' delimited) into tag/name/value/meaning fields.
Inputs: message (required).
validate_fix_messageB
Validate a FIX message: field order, header, BodyLength/CheckSum, and required fields per MsgType.
Inputs: message (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct FIX operation: building, explaining tags, parsing, and validating. No functional overlap exists.
All tool names follow a clear verb_noun pattern with underscores (build_fix_message, explain_fix_tag, etc.), ensuring predictability.
Four tools is well-scoped for a FIX protocol assistant, covering core tasks without excess or deficiency.
The set covers the full lifecycle of FIX message handling: construction, parsing, validation, and tag lookup. No obvious gaps for the intended purpose.
Maintenance
Related MCP Connectors
MCP compatibility and transport verification server.
MCP compatibility and transport verification server.
MCP compatibility and transport verification server.
MCP compatibility and transport verification server.
Related MCP Servers
- AlicenseBqualityCmaintenanceA production-grade MCP server for FIX protocol trading operations that enables order management, session repair, and algorithmic execution. It provides specialized tools for monitoring session health, managing ticker reference data, and executing complex trading scenarios.22MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives AI agents deterministic, verified access to ISO 8583 field specs, MTI decoding, jPOS packager XML generation, deploy descriptor validation, message building, and jPOS documentation search.724 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for validating JSON against JSON Schema and repairing malformed/invalid JSON.8 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for ISO 20022 acmt.001 Account Opening (and companion acmt.* messages): message-type discovery, required-field lookup, JSON Schema introspection, IBAN/BIC/LEI validation, flat-record validation, and validated acmt XML generation.7131 PyPI1Apache 2.0