manage_jira_insight_schemaLABSCO SUMMARY
Three tools instead of twelve, because the model does not need CRUD spelled out.
Collapsing each level to one tool with an operation argument keeps the tool list short, which matters when the interesting work is AQL anyway. The AQL syntax guide shipped as a resource is the detail that makes it usable — the model can read the query language before writing a query rather than guessing and getting a validation error back.
What it is
A server for Jira Insights, the asset and configuration database inside Jira Service Management. Three tools cover the three levels of the model — schema, object type, object — each taking an operation rather than splitting create, read, update and delete into separate tools.
What you get
- manage_jira_insight_schema — list, read, create, update and delete object schemas
- manage_jira_insight_object_type — the same operations against the object types inside a schema
- manage_jira_insight_object — objects themselves, plus a query operation that takes AQL
- jira-insights://instance/summary — top-level statistics about the instance
- jira-insights://aql-syntax — an AQL reference with examples, readable by the model before it writes a query
- jira-insights://schemas/all and per-schema resources for the full definition, overview and statistics
- jira-insights://object-types/{objectTypeId}/overview for one object type's attributes and counts
Requirements
JIRA_HOST, JIRA_EMAIL and JIRA_API_TOKEN, with a Jira Insights instance the token can reach and permissions matching what you intend to do. Node.js 20 or later, or the published container image, which is the easier path for most people.
Setup effort
One command plus a key — docker run --rm -i -e JIRA_API_TOKEN -e JIRA_EMAIL -e JIRA_HOST ghcr.io/aaronsb/jira-insights-mcp:latest
USE CASES
01
Finding out what is actually in the CMDB
Read the instance summary and list the schemas with their object types before asking anything specific.
02
Answering a question that needs a real query
Read the AQL guide, then run the query and get the matching objects back.
03
Understanding an object type before you write to it
Pull its attributes and statistics so the fields you set exist and are the right type.
04
Adding assets without opening Jira
Create objects against an existing object type in bulk from whatever source you already have.
05
Reshaping a schema that has drifted
Add or amend object types in place rather than editing them one screen at a time.
3 tools
Listed in project docs. Your client may show a different list.
manage_jira_insight_object_typemanage_jira_insight_objectBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- docker on PATH
- Node.js 20 or later
- JIRA_API_TOKEN in your environment
- JIRA_EMAIL in your environment
- JIRA_HOST in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
docker run --rm -i -e JIRA_API_TOKEN -e JIRA_EMAIL -e JIRA_HOST ghcr.io/aaronsb/jira-insights-mcp:latestMCP Clients
Any MCP client — Docker
ANY MCP CLIENT — DOCKER · JSON
{
"mcpServers": {
"jira-insights": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"JIRA_API_TOKEN",
"-e",
"JIRA_EMAIL",
"-e",
"JIRA_HOST",
"ghcr.io/aaronsb/jira-insights-mcp:latest"
],
"env": {
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"JIRA_EMAIL": "<YOUR_JIRA_EMAIL>",
"JIRA_HOST": "https://<YOUR_DOMAIN>.atlassian.net"
}
}
}
}
