Expertise

AI engineer for MCP servers, RAG and coding agents

I build the tooling that lets AI agents work inside real codebases, ticket systems and CI – and tests, static analysis and human review still decide what ships.

Open to new roles · from 1 December

What I bring

  • MCP servers

    My own Jira MCP server gives coding agents 20 tools – search, create and transition issues, comments, attachments and Zephyr test runs – so they work straight from the team’s tickets.

  • Ticket-to-PR agent pipelines

    Agent skills that reproduce a production bug from synced data, prove the root cause, create the Jira ticket, fix it with unit and Playwright tests and open the pull request.

  • LLM integration & RAG

    LLM features wired into existing products: retrieval-augmented generation, embeddings and vector search, tool calling and structured outputs – with evals and guardrails instead of black boxes.

  • Agent-ready websites

    This site talks to AI agents: WebMCP tools in the browser, llms.txt and every page as Markdown – generated from the same build as the HTML.

Projects that prove it

Real projects, real numbers – the full list is on the references page.

  • 2026

    Messerle Shop

    Ticket-to-PR agent pipeline

    Agent skills that take a bug from report to pull request: reproduce it from synced data, prove the root cause, create the Jira ticket, fix it with unit + Playwright E2E tests and pass the PHPUnit/PHPStan gate.

    • Claude Code
    • OpenCode
    • Agent skills
    • Playwright
    • PHPUnit
    • GitHub API
    Internal project
  • 2026

    Jira × coding agents

    Jira MCP server

    A Model Context Protocol server with 20 tools – issues, transitions, comments, attachments and Zephyr test runs – that lets coding agents work straight from the team's Jira.

    • MCP
    • Node.js
    • Jira REST API
    • Zephyr
    Internal project

Toolbox

  • Agentic engineering
  • MCP servers (Model Context Protocol)
  • RAG (retrieval-augmented generation)
  • Embeddings & vector search
  • Tool calling & structured outputs
  • Multi-agent orchestration
  • Claude Code & agent skills
  • OpenCode · Codex
  • LLM API integration (Anthropic, OpenAI)
  • Prompt & context engineering
  • LLM evals & guardrails
  • Agent guardrails: tests & CI gates
  • WebMCP · llms.txt
  • AI-assisted code review

Frequently asked questions

What is an MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI assistants and coding agents use tools and data from other systems. An MCP server wraps a system – Jira, for example – in well-described tools, so an agent can search issues or log test runs without custom glue code.

Can AI agents work safely in an existing codebase?

Yes, if the guardrails are real. In my pipelines unit and end-to-end tests, static analysis and CI gates decide what ships – and every change still goes through human review.

Which AI tools and models do you work with?

Claude Code and agent skills, OpenCode and Codex day to day, and the Anthropic and OpenAI APIs for LLM features inside products.

Where are you based – and do you work remotely?

In Voitsberg, west of Graz in Styria, Austria. Available from 1 December – remote from Voitsberg (AT) or hybrid.

Are you available?

Open to new roles · from 1 December. The quickest way to reach me is e-mail or LinkedIn.

Which languages do you work in?

English, German and Hungarian.

Sounds like what you need?

Tell me about your project or role – I’d love to hear from you.