Workflow automation
Turn repetitive intake, routing, and review into a clear, auditable flow.
Software engineering / MCP / AI integrations
I'm Tomi Šeregi, a software engineer in Slovenia. My work covers MCP integrations, human-approval workflows, search infrastructure, and reproducible reliability tests.
Working code. Explicit permissions. Reproducible tests.
Selected engineering work
Explore the implementation, what it demonstrates, and where its boundaries are.
Four related search, data, and validation systems: mcp-geo, mcp-gsc, and mcp-web-validator have local and hosted/product surfaces; TrendPulse is community/self-hosted while its managed layer remains in development.
Local human approvals, choices, refinements, and waits, paired with a deliberately narrower remote Worker for one-way notifications and safe request inspection.
Engineering noteA synthetic 21-record regression fixture shows why pending records must be ordered by durable creation time before a bounded result limit is applied.
What I build
The goal is not to add another tool. It is to remove a recurring bottleneck without giving away control.
Turn repetitive intake, routing, and review into a clear, auditable flow.
Use models where they help — drafting, classifying, and finding the next action — with people at the decision points.
Ship the infrastructure, observability, and handoffs that make an AI workflow dependable.
Specialist services
Each one is a standing offer with its own page, not a bullet on a capability deck.
AI literacy training and EU AI Act readiness for teams that have to answer for the tools they use.
Explore enablement →02Track how AI assistants cite you, and run the content pipeline that keeps you in the answer.
Explore visibility →03MCP servers, evaluation harnesses, and the document and ERP plumbing underneath.
Explore integration →Products
Useful automation should be easy to understand, easy to evaluate, and safe to own.
Engagements
Send a short brief first. We can arrange a call if it helps clarify the scope. API and platform usage is billed at cost.
How we work
Find the expensive, repeatable part of the work and define what good looks like.
Prove the workflow with your rules, your data boundaries, and your team in the loop.
Measure what happens in production, then expand only where the evidence says to.
Built for careful work
The right automation makes the next action clearer, while keeping responsibility visible.
Automation handles the first pass. Your team keeps the decisions that matter.
Data access, sending permissions, and escalation points are part of the design.
The system earns trust through observable, reviewable behavior — not a pitch deck.
Send the project or repository, the result you need, and your deadline. A call is optional.
Send a brief