Jira Insights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_MODE | No | Logging mode configuration | strict |
| JIRA_HOST | Yes | Your Jira instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_EMAIL | Yes | Your email address associated with Jira | |
| JIRA_API_TOKEN | Yes | Your Jira API token with appropriate permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_jira_insight_schemaC | Manage Jira Insights object schemas with CRUD operations |
| manage_jira_insight_object_typeC | Manage Jira Insights object types with CRUD operations |
| manage_jira_insight_objectC | Manage Jira Insights objects with CRUD operations and AQL queries |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jira Insights Instance Summary | High-level statistics about the Jira Insights instance |
| AQL Syntax Guide | Comprehensive guide to Assets Query Language (AQL) syntax with examples |
| Imports Schema and Mapping Definition (Full Schema) | Complete JSON schema definition for Imports Schema and Mapping (large reference document) |
| Imports Schema and Mapping Documentation | User-friendly documentation of the Imports Schema with examples and explanations |
| All Jira Insights Schemas | Complete list of all schemas with their object types |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose targeting different Jira Insights components: objects, object types, and schemas. The descriptions specify unique domains (objects, object types, schemas) with no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern with 'manage_jira_insight_' prefix followed by the specific component (object, object_type, schema). This predictable naming convention enhances readability and usability across the tool set.
With only 3 tools, the count feels thin for a server named 'Jira Insights MCP', which might imply broader functionality. However, it covers core management areas adequately, though it could benefit from additional tools for querying or reporting to be more comprehensive.
The tools provide CRUD operations for key Jira Insights components (objects, types, schemas), covering essential management tasks. A minor gap exists in lacking dedicated query or analysis tools beyond AQL mentioned in one description, but core workflows are well-supported.