A Model Context Protocol server for Jira Insights (JSM) schemas
A Model Context Protocol server for Jira Insights (JSM) schemas. That is what the jira insights mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This MCP server provides tools for interacting with Jira Insights (JSM) asset schemas through the Model Context Protocol. It allows you to manage object schemas, object types, and objects in Jira Insights.
The server publishes 4 tools. What each one is for:
manage_jira_insight_schema — The manage_jira_insight_schema tool exposed by this servermanage_jira_insight_object_type — The manage_jira_insight_object_type tool exposed by this servermanage_jira_insight_object — Manage Jira Insights objects with CRUD operations and AQL queriesScripts — The Scripts tool exposed by this serverConfiguration is passed through the environment: JIRA_API_TOKEN, JIRA_EMAIL, JIRA_HOST, LOG_MODE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jira Insights MCP's toolset — manage_jira_insight_schema, manage_jira_insight_object_type, manage_jira_insight_object and 1 more — is a fair guide to whether it matches your workflow. It is maintained by aaronsb; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Jira Insights MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| manage_jira_insight_schema | The manage_jira_insight_schema tool exposed by this server. |
| manage_jira_insight_object_type | The manage_jira_insight_object_type tool exposed by this server. |
| manage_jira_insight_object | Manage Jira Insights objects with CRUD operations and AQL queries. |
| Scripts | The Scripts tool exposed by this server. |
{
"mcpServers": {
"jira-insights": {
"command": "node",
"args": ["/path/to/jira-insights-mcp/build/index.js"],
"env": {
"JIRA_API_TOKEN": "your-api-token",
"JIRA_EMAIL": "your-email@example.com",
"JIRA_HOST": "https://your-domain.atlassian.net",
"LOG_MODE": "strict"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_EMAIL | Configuration value read at startup. | Optional |
| JIRA_HOST | Endpoint or connection string the server talks to. | Optional |
| LOG_MODE | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.