RFix

Create RF signal projects from prompts, inspect graphs, and export IQ data.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
68%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~882Tokens (tool definitions)
~724 BTypical response size
Moderate attention impact (0.69% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.rfix.ai/mcp"
    }
  }
}

Remote endpoints

https://mcp.rfix.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢rfix_plan_scenario(description, prefer_simple, reasoning_mode)

ALWAYS call this first for any RF scenario request. Returns block schemas, composition rules, constraints, and a reference example payload. YOU must compose your own graph/project using this guidance, then call rfix_export_rfix_project. Do NOT search the filesystem for blocks or examples — this tool returns everything needed.

Input Schema

{
  "type": "object",
  "properties": {
    "description": {
      "title": "Description",
      "type": "string"
    },
    "prefer_simple": {
      "default": true,
      "title": "Prefer Simple",
      "type": "boolean"
    },
    "reasoning_mode": {
      "default": "auto",
      "title": "Reasoning Mode",
      "type": "string"
    }
  },
  "required": [
    "description"
  ],
  "title": "rfix_plan_scenarioArguments"
}
🟢rfix_list_blocks(query, limit)

Search the shipped RFIX block catalog by keyword. Use this when you need to find specific block types not already returned by rfix_plan_scenario. Queries like radar, ship, aircraft, communication, 3d, doppler, dmr, or wifi return relevant blocks with parameter schemas. Includes parameter schemas inline.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Query"
    },
    "limit": {
      "default": 20,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "rfix_list_blocksArguments"
}
🟢rfix_list_capabilities(query, limit)

List high-level RFIX capability families for planning without flooding context. Use this before block search when the request is broad, then call rfix_search_block_catalog for likely concrete node types.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Query"
    },
    "limit": {
      "default": 10,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "rfix_list_capabilitiesArguments"
}
🟢rfix_search_block_catalog(query, limit)

Search concrete RFIX node types by natural-language keywords without returning full parameter schemas. Use this before constructing add_node actions, then call rfix_get_block_details for the selected nodeTypes.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Query"
    },
    "limit": {
      "default": 12,
      "title": "Limit",
      "type": "integer"
    }
  },
  "title": "rfix_search_block_catalogArguments"
}
🟢rfix_get_block_details(nodeTypes, limit)

Return full parameter schemas and add-node templates for a small selected set of RFIX nodeTypes. Call this only after rfix_search_block_catalog has narrowed the relevant blocks.

Input Schema

{
  "type": "object",
  "properties": {
    "nodeTypes": {
      "items": {
        "type": "string"
      },
      "title": "Nodetypes",
      "type": "array"
    },
    "limit": {
      "default": 8,
      "title": "Limit",
      "type": "integer"
    }
  },
  "required": [
    "nodeTypes"
  ],
  "title": "rfix_get_block_detailsArguments"
}
⚪rfix_export_rfix_project(payload, artifact_name)

Convert RFIX JSON input into an importable `.rfix.gz` project file. `payload` may be an RFIX backend payload, GCF prompt graph output, exported graph data, or editor/.rfix-style project JSON. Project-shaped input is preserved where possible; backend payload input is reverse-transformed into a legacy flat project. In server-side mode this also publishes launch URLs for desktop and web.

Input Schema

{
  "type": "object",
  "properties": {
    "payload": {
      "additionalProperties": true,
      "title": "Payload",
      "type": "object"
    },
    "artifact_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Artifact Name"
    }
  },
  "required": [
    "payload"
  ],
  "title": "rfix_export_rfix_projectArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools