Claude integration · Lüdenscheid, NRW
Your systems. Connected to Claude.
AI agents and MCP integrations for the software you already run.
ERP, industry software, legacy systems, internal tools — we connect them to Anthropic Claude, including where no API exists yet. Built for production, with validation at every step.
Currently accepting new projects
/ 01 · Services
Three problems we solve
- 01
Data is stuck
Your ERP, industry software or legacy system has no modern interface.
We analyse formats and protocols and build the bridge — as an MCP server Claude can use directly.
- 02
Routine work eats time
Reports, tickets, reconciliations, data extraction — the same steps every day.
Claude agents take over, with validation and human checkpoints instead of blind automation.
- 03
No safe AI access
Internal data ends up pasted into chat tools — or AI gets no access to internal systems at all.
MCP servers with explicit permissions, audit logging and approval steps — Claude sees only what it is allowed to see.
/ 02 · Process
How a project runs
Four steps from first call to a system in production. Each step ends with something you can test.
- 01
Understand the system
Analysis before change: what exists, which data flows, where the limits are.
- 02
Connect
An MCP server or integration that opens your system to Claude — with clearly defined permissions.
- 03
Automate
Claude agents for the actual workflow, with schema validation, logging and human checkpoints.
- 04
Operate
Deployed, monitored and documented. You keep full control over code and data.
/ 03 · Claude engineering
Agents that do actual work
We build AI systems around workflows, not chat windows.
Claude is embedded into your software — connected to systems, tools and data via the Model Context Protocol (MCP), with validation around every step. The model is one component of the system, not the product itself.
- 01MCP servers for existing systems
- 02Tool-using Claude agents
- 03Structured data extraction
- 04Process automation
Our focus is Anthropic Claude and the Model Context Protocol. Where a project requires it, we integrate other models as well.
- 01Input
- 02Orchestration
- 03Claude
- 04MCP / APIs
- 05Validation
- 06Output
Every production system adds logging, retries and human checkpoints to this pattern.
/ 04 · AI-orchestrated operations
Software operating software
Deployments, tests, dependency updates and incident analysis produce a steady stream of operational work.
We build systems where Claude coordinates that work — while deterministic tooling remains responsible for execution and validation. The model plans and reviews; the tooling acts.
- 01CI/CD automation
- 02Deployment orchestration
- 03Incident analysis
- 04Observability
- L3AI orchestration
decides what runs, reads results, adjusts the plan
- L2Deterministic tooling
builds, tests, deploys and validates — reproducibly
- L1Production systems
auditable, reversible changes only
/ 05 · Projects
What we're building
/ Own products and open source — built and operated
- 01
ghidra-mcp-extended
Open-source bridge between the Ghidra analysis suite and MCP-compatible AI clients such as Claude — extended with import, findings export, analysis status and function comparison.
MCP / AI toolingGitHub ↗ - 02
cs2monitor
Real-time platform that continuously polls, validates and filters thousands of public servers — only verified entries, with player and map history.
Web platform / Data validationcs2monitor.com ↗
/ 06 · Why vdit.nrw
Founder-led engineering
vdit.nrw is founded and led by Marius Rex in Lüdenscheid.
The founder designs and builds every system — no account managers, no subcontractors, no handover loss between sales and engineering.
Focused on Claude, MCP and integration of existing systems. Founded in 2024 in NRW.
- Founded
- 2024
- Location
- Lüdenscheid, NRW
- Focus
- Claude / MCP
- Contact
- Marius Rex
One contact from first call to production.
/ 07 · Contact
Which system should Claude work with?
Send a short description of the system and the task. We read every message and reply with a direct technical assessment.
From a first assessment to a maintained production system.
info@vdit.nrwUseful in a first message
- 01What should be automated
- 02Which systems are involved
- 03Constraints: deadlines, compliance, existing infrastructure