RFIX MCP
MCP server by RFix · mcp
RFIX MCP server-side mode helps agents plan RF scenarios, search the RFIX block catalog, and export launchable .rfix.gz projects. It does NOT generate IQ data and does NOT talk to rfix-api or rfix_python. WORKFLOW (follow this order): 1. Call rfix_plan_scenario(description=...) — returns block schemas, composition rules, constraints, and a reference ReactFlow/editor-project example. 2. COMPOSE YOUR OWN GRAPH: Use the reference graph as inspiration, but adapt it to the user's request. Add/remove nodes, adjust parameters, and change edges. 3. Call rfix_export_rfix_project(payload=<your composed graph/project>) — writes a .rfix.gz project and returns launch metadata for desktop and web. That is the happy path for server-side launch flows. Do NOT search the filesystem for RFIX examples. ACCEPTED EXPORT INPUT SHAPES: - GCF/LLM output: {reactFlowNodes, reactFlowEdges, gridGlobalSettings} - Exported graph: {nodes, connections, globalSettings} - Editor/.rfix-style project JSON -…
Endpoint: https://mcp.rfix.ai/mcp
Verification: observed. Source: crawl.
Capabilities (12)
- rfix_plan_scenario
- rfix_list_blocks
- rfix_list_capabilities
- rfix_search_block_catalog
- rfix_get_block_details
- rfix_export_rfix_project