mcp-server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-server — a TypeScript Model Context Protocol server
An MCP server that gives AI assistants a safe, standard way to use an internal service. It exposes a ticket domain as tools (with Zod-validated inputs) and a resource, served over stdio — plus a demo MCP client that drives it.
ℹ️ An original reference implementation. No proprietary code or data.
What it is
The Model Context Protocol lets AI assistants call tools and read resources through one standard interface. This server puts that boundary in front of an internal "tickets" service: the assistant can list/search/create tickets and change their status, but every argument is validated by a Zod schema before it touches the domain.
flowchart LR
AI[AI assistant / MCP client] -- stdio --> S[MCP server]
S --> V[Zod input validation]
V --> T[Ticket service]
S -. resource: tickets://all .-> TRelated MCP server: support-triage-agent
Tools
Tool | Input (Zod-validated) | Does |
| — | list all tickets |
|
| fetch one (errors if missing) |
|
| create a ticket |
|
| full-text search title/body |
|
| transition status |
Plus a tickets://all resource exposing the collection as JSON.
Run it
npm install
npm start # serve over stdio (for an MCP client / AI assistant)
npx tsx src/client.ts # demo client: launches the server, lists tools, calls onePoint a real assistant at it by configuring an MCP server that runs
npx tsx src/index.ts (stdio transport).
Tests
npm run typecheck # tsc --noEmit
npm test # vitestCover the ticket store (CRUD + search + status), the tool handlers (including the not-found error), and the Zod schemas (accepts valid, rejects bad status / empty fields). The domain and tool logic are framework-free, so they test without spinning up a transport.
Design decisions
Tools are thin wrappers over plain functions — the service logic is unit-tested directly; the MCP layer only validates and serializes.
Zod at the boundary — an assistant's arguments are untrusted input; schemas reject malformed calls before they reach internal code.
stdio transport — the standard local-tool transport; the same server also fits Streamable HTTP without touching the tool definitions.
An original reference implementation. No proprietary code or data is included.
This server cannot be deployed
Maintenance
Related MCP Connectors
Work your Help tickets with your AI: read them, reply or leave notes, and set up forms and sites.
File, find and update AoTwin tickets from your AI assistant, and hand one to AoTwin when you ask.
Helpdesk tickets from your AI: find, reply, take, hold, complete — within your own role. OAuth.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables managing support tickets from Claude, Cursor, and other AI tools, including listing, creating, updating, and replying to tickets.6275 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables ticket management and AI triage through Mistral-compatible models, with tools for creating, listing, retrieving, triaging, and updating support tickets.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to list, fetch, and create tickets through a ticket-tracking backend that can be swapped between an in-memory store and a REST API. Inputs are schema-validated, results include both text summaries and structured content, and failures return actionable messages the model can recover from.33 npm1MIT