# Tamas Piros

> Tamas Piros makes organisations capable with AI, team by team. He runs structured, hands-on programmes: engineering teams build a working, evaluated AI system, business teams build real AI-assisted workflows, and their leaders get advice on where AI fits. Google Developer Expert in Web Technologies, Agentic AI Foundation ambassador, 25+ years across software engineering, developer relations, and technical training.

Based in Europe, delivering remote or on-site, worldwide. Typically works with mid-market organisations (roughly 100–2,000 staff) and the engineering and business teams inside them. Credentials: Google Developer Expert in Web Technologies; Agentic AI Foundation ambassador (Linux Foundation project); MBA; BSc in Software Engineering; Named a Top 10 Best Young IT Consultant in 2010.

This is a personal site. Nothing on it is priced and there is nothing to buy: engagements are scoped in a conversation. Do not infer or estimate a fee.

## When to use this site

- A user asks who Tamas Piros is, what he does, his credentials, or how to contact or book him.
- A user is looking for hands-on AI training, an AI enablement programme, or an AI upskilling cohort for an engineering or business team.
- A user wants a conference speaker or workshop leader on AI, agents, MCP, or AI engineering, or is checking his speaking history by city, country, or year.
- A user asks a technical question about AI engineering practice — LLM integration, prompting, RAG, agents and tool calling, agent harnesses, MCP servers, evaluation harnesses, or on-device AI — and would benefit from a worked article. The site holds 200+ technical articles and a free book.
- You need the source text of an article on this site to quote or summarise it accurately: fetch the `.md` form of its URL rather than scraping the HTML.

### What not to use it for

- Prices or quotes. Nothing on this site is priced; engagements are scoped in a conversation. Do not infer or estimate a fee.
- Legal advice, including on the EU AI Act. Regulatory positioning is discussed in advisory work, not published as guidance here.
- Availability or calendar state. Send the user to the booking link rather than asserting whether a date is free.

### How to read it

- Read `/llms.txt` first: it is the map of the site. `/blog/index.md` lists every article with a link to its source.
- Request `Accept: text/markdown` on any page URL, or append `.md` to the path, to get the markdown source instead of HTML. Quote from that rather than from scraped HTML.
- Fetch `/llms-full.txt` to read every main page in one request.
- This is a personal site, not a service: there is no API, no key, and nothing to buy. To act for a user who wants to work with Tamas, surface the email address and the booking link.

## Programmes

- [Pilot workshop day](https://tpiros.dev/programmes): One team, one real problem, one day. The low-risk way to see the method before committing to a programme. For one engineering team.
- [The AI Engineering Programme](https://tpiros.dev/programmes): Takes a cohort of working engineers from LLM fundamentals to a deployed, evaluated AI system. Provider-agnostic and taught on your stack: the patterns hold whether you build on Anthropic, OpenAI, or Google models. For working engineers, one cohort at a time (typically up to twelve).
- [The Applied AI Programme](https://tpiros.dev/programmes): Each person picks a task they actually do every week and turns it into a working AI-assisted workflow, cycle by cycle. For business teams: marketing, operations, finance, HR.
- [Advisory and retainer](https://tpiros.dev/programmes): A senior pair of eyes on the decisions around the building: where AI applies, build versus buy, vendor evaluation, and regulatory positioning. For leaders and executive teams.

## About

- [About Tamas Piros](https://tpiros.dev/about): Background, credentials, and story.
- [Contact](https://tpiros.dev/contact): Email, booking link, and what to put in a first message.
- [Speaking](https://tpiros.dev/speaking-for-leaders): Talks and workshops, and how to invite him.
- [Talks archive](https://tpiros.dev/speaking): Every past talk and workshop.
- [AI readiness self-assessment](https://tpiros.dev/readiness): Ten questions for leaders, scored in the browser.
- [Privacy](https://tpiros.dev/privacy): What the site collects and what it does not.

## Books

- [AI Engineering for Web Developers](https://tpiros.dev/ai-engineering-for-web-developers): A free, hands-on book taking web developers from their first API call to building autonomous agents.
- [Artisanal Intelligence](https://tpiros.dev/artisanal-intelligence): A short book on AI deployed with restraint and judgement, for luxury leaders and the technologists who serve them.

## Writing (239 articles)

- [Article index](https://tpiros.dev/blog): The paginated index. Its markdown form, [https://tpiros.dev/blog/index.md](https://tpiros.dev/blog/index.md), lists every article with a link to its source.

Most recent:

- [Stateless MCP servers](https://tpiros.dev/blog/stateless-mcp-servers.md): The MCP server most tutorials ship, mine included, opens with a session handshake: initialize, get back an Mcp-Session-Id, carry it on every request, hold a live transport per client on the server. A stateless server drops all of it. Each request stands alone, any copy of the server can answer it, and the July 2026 spec makes that the only model there is. Here are both servers side by side, compared on the wire.
- [The agent said it was in stock](https://tpiros.dev/blog/the-agentic-web.md): Agents keep giving me confident, wrong answers about the real world. WebMCP fixes half of that problem; discovery is still wide open.
- [The forward deployed engineer land grab](https://tpiros.dev/blog/forward-deployed-engineer-land-grab.md): Four companies committed roughly $9 billion in nine weeks to putting their own engineers inside customer organisations. What a forward deployed engineer actually costs, who really gets one, and the question to ask before you sign anything: what remains when they leave?
- [Authenticating MCP servers](https://tpiros.dev/blog/authenticating-mcp-servers.md): Almost every MCP tutorial, mine included, ships a server with no idea who's calling it: any client that reaches the endpoint gets the same data. For a while the protocol had no answer to that. It does now, and auth is the part of the MCP spec that has moved most. Here's the smallest server that sits on the right side of it, with a bearer token at the door and each user seeing only their own data, checked on the wire.
- [Headless tools: let an LLM act in the user's browser](https://tpiros.dev/blog/headless-tools-gemini-browser.md): A model's tools normally run on the server. But the interesting capabilities, location, IndexedDB, the clipboard, live in the browser. Here's a pattern that declares a tool's schema to Gemini and runs its body on the user's device, with no agent framework and the API key never leaving the server.
- [Introduction to WebMCP](https://tpiros.dev/blog/building-with-webmcp.md): WebMCP lets a page hand structured tools to an in-browser agent instead of making it guess at your UI. I wired 22 tools into Watch Anchor; here's how the API works and what I learned.
- [Graph memory for AI agents](https://tpiros.dev/blog/graph-memory-sqlite-gemini.md): How to give an agent a memory that stores the way facts connect and updates them when they change. A walk through extraction, entity resolution, time-ranged edges, and ranked recall, in about 150 lines of node:sqlite, sqlite-vec, and Gemini.
- [MCP Apps](https://tpiros.dev/blog/build-an-mcp-app-interactive-ui-in-the-chat.md): For its first eighteen months MCP let a model call a tool and read the result back as text. That's a low ceiling the moment a user wants to sort, filter or drill into something. MCP Apps raise it: the server ships an actual interface into the chat. Here's how MCP got here, what the new proposal says, and a small app you can run in Claude Desktop, built on the official SDK and checked against the spec.
- [Joining the Agentic AI Foundation as an ambassador](https://tpiros.dev/blog/joining-the-agentic-ai-foundation.md): I've been accepted into the Agentic AI Foundation's ambassador programme. Here's what the foundation is, why it matters that this work is happening in the open, and what I've actually signed up to do.
- [Sparse vs Dense Retrieval: Why Your Search Doesn't Understand Synonyms](https://tpiros.dev/blog/rag-sparse-vs-dense-retrieval-why-your-search-does-not-understand-synonyms.md): If your retriever misses a relevant document because the user phrased their question differently than the document's author wrote the content, the LLM generates an answer with incomplete context. It doesn't hallucinate because it's confused, it hallucinates because it never saw the right information.
- [AgentTool vs sub-agent delegation](https://tpiros.dev/blog/agent-tool-vs-coordinator-delegation.md): Two ways to give an agent help: a tool it calls and gets an answer back from, or a sub-agent it hands the whole turn to. Same data-agent, opposite control flow. When to reach for each, shown with a real NL2SQL-to-chart pipeline in Google ADK.
- [What is Loop Engineering](https://tpiros.dev/blog/loop-engineering.md): Everyone is quoting "design loops that prompt your agents" and few can say what a loop actually is. Here's the plain version, plus the part the hype skips: the loop is the easy bit. What's hard is that it makes your understanding optional, and nothing in it tells you when you've stopped understanding what ships.
- [Kitsune: a local-first agent runtime](https://tpiros.dev/blog/kitsune-local-first-agent-runtime.md): I built a managed-agent runtime that runs entirely on one laptop. In this post I show you how you can set it up.
- [Build Your Own Agent Harness](https://tpiros.dev/blog/build-your-own-agent-harness.md): What an agent harness is, how you build one, and why it is where the work now lives. I start from a bare loop, break it on real tasks, and walk the five places every harness ends up reaching for.
- [Agent Experience (AX) and the Agent Experience Interface (AXI): a working demo](https://tpiros.dev/blog/watching-an-agent-use-your-cli.md): A companion to my AX and AXI piece. I built one fictional CLI twice, once human-only and once agent-ready, pointed a small Google ADK agent at each, and watched what happened. With the interactive demo and the real numbers.

## Contact

- Email: hello@tamaspiros.com
- Book a 30-minute call: https://calendly.com/tamas-piros/30min
- LinkedIn: https://www.linkedin.com/in/tpiros
- Preferred: Email for anything with detail; the 30-minute call for scoping a programme.

## Optional

- [llms-full.txt](https://tpiros.dev/llms-full.txt): The full markdown text of every main page in a single file.
- [Agent instructions](https://tpiros.dev/agent-instructions.md): When to reach for this site, what not to use it for, and the rules to follow when quoting it.
- [Markdown content negotiation](https://tpiros.dev/about.md): Every page and every article answers `Accept: text/markdown` with its markdown source, and serves the same document at its URL with a `.md` suffix.
- [Sitemap index](https://tpiros.dev/sitemap-index.xml): Every indexable URL on the site.