MCP & AI Integration
Connect AI assistants to Pomavo through the Model Context Protocol server: search, create, and manage work with natural language.
Overview
Pomavo ships an MCP server, short for Model Context Protocol, that lets AI assistants work with your Pomavo organization directly. Instead of copy-pasting between an AI chat and Pomavo, the assistant can read templates and projects, search and create tickets, manage comments and links, and even run bulk query mutations, all through a well-defined set of tools.
The MCP server is a standalone process that talks to the Pomavo API on your behalf, authenticated with an API key scoped to a machine identity.
Authentication
The server authenticates every call with:
X-API-Key: an API key issued to an integration machine identityX-Org-Short-Name: the organization the assistant should act in
Because it uses a machine identity, everything the assistant does is attributed to that identity and governed by the same permissions as any other API client. Grant it only the access it needs.
The assistant acts as the integration's identity, so its actions appear in activity feeds and history under that identity, giving you a full audit trail of what the AI did.
What the Assistant Can Do
The server exposes a focused toolset covering the core of Pomavo:
Read structure
List and inspect templates, projects, and iterations to understand your setup.
Search & read tickets
Run full DSL queries, fetch a ticket with comments, links, history, and attachments, or pull a sprint's tickets.
Create & update
Create tickets from templates, update fields, set the iteration, and move tickets through their workflow.
Collaborate
Add, edit, delete, and list comments; create and remove links between tickets.
Attachments
Upload, download, and delete ticket attachments.
Permissions
Check its own permissions and, when allowed, grant or revoke access.
Tool Categories
The server provides tools grouped by area:
| Area | Capabilities |
|---|---|
| Templates | List templates, get a template by name or id |
| Projects | List projects, get a project by slug or id |
| Iterations | List iterations, get the active iteration for a project |
| Tickets | Get, search, get sprint tickets, create, update, set iteration, list transitions, transition |
| Comments | Add, edit, delete, list |
| Links | List links, list link types, link, unlink |
| Attachments | Download, upload, delete |
| Permissions | Get my permissions, grant, revoke, check, get user permissions, list all grants, list available |
| Queries | Run a DSL query, including bulk mutations |
| Automations | List, get, create, and read the automation query syntax |
Working with the DSL
The execute_query tool gives the assistant the full query language, including bulk mutations such as SET, CREATE, LINK, UNLINK, and COMMENT. This lets an assistant do things like "close every done ticket missing a resolution" in a single, auditable operation.
Because the assistant can run mutations, scope its machine identity's permissions carefully and review what it does. Mutations apply to every ticket a query matches.