MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
RFix is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Create RF signal projects from prompts, inspect graphs, and export IQ data.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http rfix-mcp https://mcp.rfix.ai/mcp
# 2 — ask your agent for something these tools do
# rfix_plan_scenario, rfix_list_blocks, rfix_list_capabilities and 3 more
RFix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http rfix-mcp https://mcp.rfix.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | — |
| prefer_simple | boolean | no | — |
| reasoning_mode | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | — | |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | — | |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | — | |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nodeTypes | array | yes | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payload | object | yes | — |
| artifact_name | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RFix or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.27.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish RFix can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.