Coding Agents and MCP: The Future of EN 18031 and CRA Compliance
Much of what EN 18031 and the Cyber Resilience Act ask about your product is answered in your source code, not in a document. RedComply's MCP server lets the coding agent your developers already use answer the standard's questions straight from the repository. Today, in pilot, it drafts technical documentation tables. The direction is orchestration: the compliance of every product you ship, kept current release after release.

Compliance That Keeps Pace With Your Code
A compliance file is a snapshot. Firmware is not. The authentication module gets a new lockout rule, the update client moves to a new signature library, a debug interface is closed in the release build. Each change can alter what the technical documentation of a radio product says under EN 18031, and under the Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) the technical documentation must be "continuously updated, where appropriate, at least during the support period" (Article 31(2)).
Until now, keeping that file current meant a person reading code, asking developers, and copying answers into tables. Coding agents change the economics. They already read your repository, understand your build and run your tools. Connected to RedComply through the Model Context Protocol (MCP), they become the evidence collectors of your compliance process, while RedComply's own compliance agent keeps doing the regulatory work and a person keeps the final word.
Key takeaways
RedComply's MCP server connects coding agents such as Claude Code, Codex or Cursor to a RedComply project. RedComply asks the standard's questions; your agent answers from the code with file references and short quotes.
Your repository never leaves your machine. RedComply has no tool that opens a file; it only receives answers, references (path, lines, commit) and quotes of at most 500 characters.
RedComply writes the tables, an agent never does, and each row's outcome is computed by the requirement's decision tree. Every drafted table waits for a person's review before it counts for a declaration of conformity.
Today, in pilot: technical documentation tables for EN 18031 and the CRA, up to three in parallel per project.
The direction: test plan automation, full CRA support, orchestration across many products and compliance stages in CI/CD pipelines, so each new version updates its own documentation.
What Is RedComply's MCP Server for Coding Agents?
RedComply's MCP server is the connection between the coding agent on your machine and RedComply's compliance agent. MCP is an open protocol that lets an AI agent use the tools of another system. RedComply exposes a small, fixed set of tools: list the technical documentation tables of a project, read one, start a drafting job, read its questions, send answers, confirm or reject a draft, and cancel a job. Through this connection the agent can do nothing else in your account.
The division of labour is the point. RedComply's compliance agent knows the standards and the templates, so it asks precise questions about your product. Your coding agent knows your code, so it searches the repository and your local documents and answers each question with evidence. What it cannot find, it asks you. The animation below follows one question through that loop.
What crosses the line, and what never does
Stays on your machine: the repository and source files, build files, configuration and credential files, the documents you keep locally, and the search itself.
Reaches RedComply: the answers your agent gives, file references (path, lines, commit), short quotes of the cited lines, and what you state yourself, recorded as a user statement.
Is refused: references to credential files and text containing a private key or a token in a known format. Your agent is also instructed never to send keys, passwords or credential contents.
Stays under your control: each connection key opens one project, lasts 30 days at most, is shown once, is stored only as a hash and can be revoked at any time.
Any coding agent that supports MCP and can reach a remote MCP server can connect. RedComply shows the setup for Claude Code, Codex and Cursor in the dashboard; the integration is in pilot and has not been tested with every agent or version.
How a Pilot Session Works Today, Step by Step

Connect once per project. In RedComply, open Connected agents, create a connection key and add RedComply's MCP server to your coding agent's configuration.
Ask in one sentence. For example: "Fill the technical documentation tables that are ready." Your agent lists the tables with their state and starts a drafting job for each one whose upstream tables are filled, up to three in parallel.
RedComply asks, your agent answers from the code. Each job runs up to three rounds of up to ten questions. Your agent answers with a reference and a short quote, or asks you when the code is silent. A round waits 20 minutes for answers.
RedComply drafts, your agent checks. The compliance agent writes rows and justifications; the outcome of each row is computed with the requirement's decision tree, the same calculation as in the table editor. Your agent compares the draft with the code and confirms it or sends it back with a note.
A person reviews. The table is saved as "Drafted via MCP, not yet reviewed". Someone on your team marks it as reviewed or reverts it, and only then does it count for the declaration of conformity.
Drafting by hand, in the chat, or with your coding agent
| By hand | RedComply assistant (browser) | Coding agent via MCP | |
|---|---|---|---|
Where the facts come from | Interviews, wikis, memory | Documents uploaded to the Knowledge Base | The repository and local documents, read on your machine |
Who answers the questions | The engineer filling the table | You, in the chat | Your coding agent, with file references and quotes; you for what the code does not say |
Who writes the table | The engineer | RedComply's compliance agent | RedComply's compliance agent; your agent never writes a table |
How outcomes are decided | Manual judgement per row | Decision trees | Decision trees, the same calculation |
Tables in progress | One | The table you have open | Up to three, without switching |
Review | Peer review, if any | You confirm each proposal | A person reviews every drafted table in RedComply |
The browser and the coding agent work on the same project and the same tables. Use the browser for what lives in documents, such as policies and supplier statements, and the coding agent for what lives in code: authentication, update verification, cryptography, logging, network services.
The Direction: Orchestrating Compliance Across Every Product
Drafting one table from one repository is the first step. The direction we are building toward is orchestration: one instruction, many agents, many products. A manufacturer rarely ships a single device. A smart home range can hold a thermostat, a router, a camera and a gateway, each with its own firmware, its own EN 18031 parts and its own CRA obligations, often sharing the same update client or TLS stack.

In the orchestrated model, an orchestrator agent takes the goal ("bring every product to its next release") and dispatches the work: one agent per product repository, each running its own drafting jobs against RedComply, all at once. RedComply remains the system of record: it holds the tables, computes the outcomes and knows which requirement depends on which. The people on your team see one review queue instead of four spreadsheets.
What orchestration changes for a compliance team
Parallel products, not a queue of projects. Four product files progress in the time one used to take, because the evidence gathering runs concurrently.
Evidence reused across shared components. When five products share the same OTA library, one verified answer about its signature check can back five tables, each still reviewed per product.
One portfolio view. Which products are ready for their declaration, which wait for review, which have open questions only a person can answer.
People where judgement matters. Engineers stop copying facts between tools and spend their time on the decisions the standards reserve for the manufacturer.
Continuous Compliance in CI/CD Pipelines
The natural place for orchestration is the release pipeline. Your CI already builds, tests and signs every firmware version. In the near future it can also keep the compliance file in step: when a release tag is pushed, a compliance stage generates the SBOM, scans it for known vulnerabilities, works out which requirements the changes since the last release touch, and asks the agents to update only those tables and test records.
This is where the regulations point anyway. The CRA requires the cybersecurity risk assessment to be "documented and updated as appropriate during a support period" (Article 13(3)) and the technical documentation to be continuously updated (Article 31(2)). Under the RED, the technical file supporting your EN 18031 claim must describe the product you actually place on the market. Our guide to software updates and RED compliance explains when a new version needs a fresh look.

What a compliance stage could look like
The snippet below is a concept, not a product you can install today. It shows the shape: the pipeline holds a connection key as a secret, and a coding agent running headless in CI talks to RedComply's MCP server exactly as it does on a developer's laptop.
# Concept, not available todayon: push: tags: ['v*']jobs: compliance: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - run: make sbom # CycloneDX SBOM of the release build - run: | coding-agent run --mcp redcomply \ "Update the compliance file for $GITHUB_REF_NAME: re-open only the requirements touched since the last release, answer RedComply's questions from the code, attach the test reports of this build." env: REDCOMPLY_MCP_KEY: ${{ secrets.REDCOMPLY_MCP_KEY }}Rules a compliance stage should keep
The pipeline drafts, a person approves. A release can wait on a review the way it waits on a code review; nothing becomes part of a declaration unreviewed.
Only touched requirements are re-opened. A change to the update client re-opens the secure update requirements, not the whole file.
Failures are visible, not silent. A new FAIL outcome or a known exploitable vulnerability stops the stage and names the requirement, so the decision to ship stays with you.
Every version leaves a trail. Documentation, SBOM, scan report and test evidence are versioned with the firmware they describe.
What Comes Next: Test Plans, Full CRA Support and Beyond
The pilot starts with technical documentation because that is where code holds the most answers. The same connection is planned to carry the rest of the compliance workflow, step by step, with the same rule throughout: RedComply writes the compliance content, your agent brings the evidence, a person reviews.
Full test plan automation
EN 18031 assessment runs in three phases, and each one suits an agent differently. The conceptual assessment already aggregates the decision-tree results of the technical documentation, so it comes first. The functional completeness assessment asks whether every documented mechanism is actually present in the product: an agent can compare the documentation with the build configuration, the enabled services and the release flags. The functional sufficiency assessment needs real tests, such as fuzzing, penetration tests and cryptographic checks: here an agent can prepare test cases from the device's threat model, run the tools your team already uses and attach the reports as evidence. In a Module A self-assessment the manufacturer remains the evaluator, and the evaluator's judgement stays with a person.
Full CRA support, beyond the technical documentation
Today the pilot already covers the CRA requirement tables of the technical documentation. Next on the same connection: the cybersecurity risk assessment of Article 13, with architecture and design facts taken from the repository, and the risk register, so countermeasure tasks sit next to the code that implements them. After that, the lifecycle the CRA expects for the whole support period: an SBOM per release (see our ESP32 firmware SBOM guide), vulnerability handling, drafts of the Article 14 notifications when an actively exploited vulnerability appears (applicable since 11 September 2026), and a new version of the EU declaration of conformity when the product changes.
| Capability | Today (pilot) | Direction |
|---|---|---|
EN 18031 technical documentation tables | Available | Re-opened automatically when the code they describe changes |
CRA requirement tables | Available | Part of a full CRA file per release |
Test plan assessments | Not yet | Conceptual first, then completeness and sufficiency with attached test reports |
CRA risk assessment and risk register | Not yet | Facts from the repository; tasks next to the code |
SBOM, vulnerabilities, Article 14 | In the RedComply dashboard | Driven from the pipeline on every release |
Several products at once | Up to 3 tables per project in parallel | Orchestration across the whole portfolio |
What automation will not replace
Review by a person. A table drafted through MCP counts for a declaration only after someone on your team reviews it.
Your responsibility as manufacturer. RedComply supports your self-assessment; it does not certify the product, and the declaration remains yours to sign. See Module A and documented procedures.
Notified bodies where they are required. When EN 18031 is applied with a restriction or only in part, Module B+C with a notified body still applies.
Real testing. An agent can prepare and run tests, but sufficiency evidence comes from tests performed on the product, not from text.
Frequently Asked Questions
Does RedComply read my source code?
No. RedComply never reads the repository and has no tool that opens a file on your machine. Your coding agent reads the files locally and sends only its answers, file references and quotes of at most 500 characters from the lines it cites. So a few lines can reach RedComply as a quote; the files do not.
Which coding agents can connect to RedComply's MCP server?
Agents that support the Model Context Protocol and can connect to a remote MCP server. Claude Code, Codex and Cursor are examples, and the dashboard shows the setup for those three. The integration is in pilot and has not been tested with every agent or version; RedComply is not affiliated with their vendors.
Can the MCP server fill EN 18031 test plans today?
Not yet. The pilot covers the technical documentation tables for EN 18031 and the CRA. Test plan assessments are planned on the same connection, starting with the conceptual assessment.
Does a table drafted through MCP count for the declaration of conformity?
Only after a person reviews it. A drafted table is marked "Drafted via MCP, not yet reviewed", and RedComply's declaration generation refuses to proceed while an applicable table carries that mark. Revert restores the version the draft replaced.
Will RedComply integrate with CI/CD pipelines?
That is the direction: a compliance stage that runs on each release, re-opens only the requirements a change touches and asks for a person's review before the declaration. It is not available today; the pilot works with a coding agent run by a person.
How do I get access to the pilot?
The integration is open to a limited number of manufacturers. Request early access from the coding agents page with your product, the regulations that apply and the coding agent your team uses.
Conclusion
Coding agents automate EN 18031 and CRA compliance by doing the part that used to be slowest: finding the facts in the code. Through RedComply's MCP server, your agent answers the standard's questions from the repository with references and quotes, RedComply drafts the tables and computes the outcomes with the decision trees, and a person reviews every result. The repository never leaves your machine.
The pilot does this today for technical documentation tables. The road ahead is orchestration: test plans and the full CRA lifecycle on the same connection, many products in parallel, and a compliance stage in every release pipeline. Compliance stops being a project you finish before launch and becomes a property of each version you ship.
RedComply: We Are by Your Side
RedComply guides manufacturers through EN 18031 and the Cyber Resilience Act, from the technical documentation and test plans to the risk assessment, the SBOM and the declaration of conformity. With the MCP server, the coding agent your team already uses becomes part of that workflow.
Connect your coding agent and draft technical documentation tables from your code: see how it works.
Keep a person in control: every drafted table is reviewed before it counts for a declaration.
Grow with the roadmap: test plans, full CRA support and orchestration on the same connection.
Visit redcomply.com to start, or request early access to the coding agent integration.
