Each example here is a whole server: several files, the tools, resources, jobs or agents it needs, and tests that check it works. It runs in the Playground, like every example on this site, so you can open it, call its tools, change the code and run the tests without installing anything.
Every example page starts with the server, then walks through it file by file, with links to the lessons that explain each part. To learn FrontMCP from the beginning, start with the Quick Start instead.
A workflow that collects yesterday's tickets, works out which ones broke their SLA, and writes a report, with a job per step, started in the background by a tool.
An agent that reads a new ticket and its customer, looks for related tickets, then sets the priority and the team with its own private tools. A skill tells the client's model how to triage the whole queue.
An agent that answers a hard support question from knowledge-base articles and closed tickets, with every claim citing the ids it came from. It hands the searching to another agent, drops ids that don't exist, and refuses a claim that cites a source it wasn't given. The articles and tickets are also resources, so a client can open whatever an answer cites.
A help desk tool that answers a support agent's "where's my order?" with the order and its shipping timeline as data, and as a widget with buttons that call more tools through the host. Their answers update the page, refusals included.
A dashboard of what support spent in a month on refunds, credits and goodwill, as a static widget: one page, served once, that draws each result. Its month and team filters call the tool again, and outputSchema keeps the internal notes out.
A help desk CRM with 47 tools, put behind the CodeCall plugin. A model searches for the tools it needs, reads their schemas, and answers "which enterprise customers have a stale high-priority ticket, and who manages them" with one script on the server. Destructive tools stay out of the script's reach.
A help desk server that wraps the classic Swagger Petstore with the OpenAPI adapter, then makes it fit for a model: clear tool names and descriptions, the API's keys sent by the server, writes left out, errors with a next step, and a search tool of its own.