Model Context Protocol specialists
Deep skills without product context tend to produce fragile integrations. The specialist work has to connect to real user flows.
We prototype the risky integration first, then sort out auth, data contracts, evaluation, and monitoring before spending time on polish.
We work best with teams adopting agentic AI tooling who want a partner that ships. Custom MCP servers that connect AI agents to your tools, data, and workflows.
What you get
- Custom MCP server development
- Tool-calling integrations
- Secure agent access patterns
- Cursor and Claude-ready tooling
- One studio accountable for the result
- Design and engineering on the same schedule
- Support available after launch
How engagement works
As your MCP developer, we run a shared backlog, design reviews, and engineering sprints, and you keep one point of contact throughout.
- 01
Discover
Goals, constraints, data sources, and success metrics, all settled before we touch architecture or prompts. You see progress on the critical path every week.
- 02
Design
System design, AI/tool boundaries, interface direction, and interaction prototypes. Nothing here waits on a handover between separate teams.
- 03
Build
Modern stack, clean architecture, evaluated AI behavior, and iterative demos you can react to. On MCP development projects we favour practical architecture over trendy defaults.
- 04
Launch
Ship, monitor, harden, and keep improving models, tools, and product after go-live. The work for teams in Germany stays tied to the outcome you asked for.
How we build it, and why
The stack is chosen per project, not applied from a template. For MCP developer work these are the defaults, and the reason each one is on the list.
- MCP
- the Model Context Protocol, so your tools plug into Claude, Cursor, and other agent clients without a custom adapter for each
- TypeScript
- types across the whole stack, which catches the class of bug that only shows up in production
- Node.js
- one language across the stack, so context does not get lost at the boundary
- Claude
- long-context reasoning and reliable tool calling for agent work
- OpenAI
- a second model provider, so a single vendor's outage or price change is not your problem
What the first weeks look like
- Week 1
Spike the risky part
We build the thinnest possible version of custom mcp server development against your real data. If it is going to be a problem, it is better to know in week one than week six.
- Weeks 2-3
Harden the integration
Auth, rate limits, error paths, and the data contract. This is the work that separates a demo from something you can leave running.
- Weeks 4-6
Wire it into the product
The MCP development stops being a standalone service and becomes a feature people use, with the interface and permissions that implies.
- Ongoing
Evaluate and tune
Behaviour gets measured against cases you care about, and we tune from that rather than from impressions.
Weighing up your options
There are three realistic ways to get this built. Each is the right answer for someone.
A solo freelancer
Cheapest per hour and fine for a contained task. The risk on MCP development is breadth — one person covering design, backend, infrastructure, and launch usually means one of them is weak, and there is no cover when they are unavailable.
A local agency in Germany
Same timezone and a face to meet, which genuinely matters for some teams. You are also paying German teams emphasizing quality, privacy, and maintainable systems. rates for the whole team including the layers that never touch your MCP development, and a local shortlist is a small shortlist.
Arcode
A small senior team. The people who scope the MCP development write the code, you get weekly demos instead of status decks, and the engagement ends when the thing is live and handed over.
Work we have shipped
Note Assist
AI product · Next.js · Speech
AI meeting assistant with live speech-to-text, ChatGPT chat, and Firebase auth for transcription workflows.
Freelance AI product built with Next.js, Firebase, AssemblyAI, and ChatGPT for live meeting transcription and realtime chat around the transcript.
- · Live speech-to-text transcription
- · Realtime chat over meeting notes
- · Firebase authentication
- · AI-assisted follow-up on transcripts
Next.js · Firebase · AssemblyAI · ChatGPT · TypeScript
Agile IT Blog
Frontend · Astro
Performance-minded blog maintained in Astro with Markdown, Tailwind, and modular content integrations.
Stellar Stack content site where I improved performance and scalability across modular Astro components and data integrations.
- · Astro static content pipeline
- · Markdown-driven posts
- · Modular component structure
- · Performance and scalability pass
Astro · Markdown · Tailwind · SCSS
Brain Blog
Frontend · Gatsby · Strapi
Custom Gatsby blog with Strapi CMS, built for fast content publishing and a clean reading experience.
Freelance content product pairing Gatsby performance with Tailwind styling and a Strapi-powered editorial workflow.
- · Gatsby static generation
- · Strapi blog integration
- · Tailwind-driven layout
- · Fast content browsing
Gatsby · Tailwind · Strapi
Working with teams in Germany
German teams emphasizing quality, privacy, and maintainable systems. Work is remote-first (CET/CEST), with written updates you can read in your own time. We usually collaborate in German/English.
How we work with Germany teams
Germany is three to four hours behind us, which means a full shared afternoon. German teams generally prefer a written scope agreed before work starts, and we work that way by default: spec in writing, then build against it.
What Germany clients usually need
German work skews towards maintainable systems rather than throwaway MVPs — B2B platforms, industrial and logistics tooling, and AI features that have to be explainable to a non-technical stakeholder before they ship.
Contracts, data, and compliance
GDPR is the starting point, not an afterthought. We default to EU-hosted data stores, keep a record of processing activities, and provide a DPA without being asked. Invoicing is in EUR, with reverse-charge VAT for registered businesses.
