Neosyn Fpga MCP server

C⏚ Agent Kit

<!-- mcp-name: io.neosyn/neosyn-fpga-mcp -->

Install neosyn-fpga-mcp. This project was called cg-agent-kit up to

1.0.0. "cg" is our shorthand for C⏚ and meant nothing to anyone searching for

an FPGA tool.

pip install cg-agent-kit does not work — that name has never been

published to PyPI, so every instruction pointing at it, including our own,

returned No matching distribution found. We intend to claim it as a shim

that pulls in this package; until then, neosyn-fpga-mcp is the only name

that installs.

Inside the package the old paths are intact:

python -m cgagentkit.cgmcpserver and the cg-mcp-server command both

still resolve, so an existing MCP host config keeps working once this package

is installed.

Make any LLM write C⏚ (Cg) instead of Verilog — without retraining the model. The kit has two parts that work together:

model's system prompt and it can write plausible C⏚: the mental model, types, ports, structs/enums/generics, the standard library, and the gotchas that otherwise sink first drafts.

1. cgcontext.md** — a paste-anywhere knowledge pack. Load it as the

checks, simulates, and generates Verilog against the real compiler and self-corrects. This is what makes the output actually correct despite the model having almost no C⏚ in its training data.

1. cgmcpserver.py — the Neosyn compiler exposed as MCP tools. The model

Knowledge gives a good first draft; the compiler-in-the-loop makes it right. Both are model-agnostic — any MCP-capable host (Claude Desktop/Code, Cursor, Cline, …) works, and the context pack works with any LLM at all.

Why this instead of fine-tuning

C⏚ is a niche language with little public code, and it gains features every release. A fine-tuned model is expensive and goes stale. In-context knowledge plus a verification loop costs nothing to retrain, tracks the language as the compiler evolves, and converges on correct code by running it rather than recalling it.

Tools the server exposes

13 tools. Every tool that takes source accepts source (a C⏚ string) and an optional extra_files map ({"Defs.cg": "..."}) for imported bundles/tasks.

These are the only names that exist, and the server says so rather than hoping you read this table: a call to a tool that does not exist comes back with the whole list and the closest real name (cgcompile → "did you mean cgcheck?"), cg_capabilities carries the list, and the first call of a session carries it once. The list is generated from the tool registry, so it cannot drift out of step with the table below — TestNoStaleToolNames and TestStaticRostersMatchTheRegistry fail if it does.

Shortened. The full README is on GitHub.