jtk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Email for the API token | |
| JIRA_DOMAIN | Yes | Atlassian domain (e.g., acme for acme.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Atlassian API token | |
| JIRA_TOKEN_TYPE | No | classic or scoped (auto-detected if omitted) | |
| JIRA_DISABLED_TOOLS | No | Comma-separated tool names to hide |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_attachmentsB | Manage Jira issue attachments (list, download, upload, delete). Actions: 'list', 'download', 'upload', 'delete' |
| manage_boardsB | Manage Jira agile boards and sprints. Actions: 'list_boards', 'get_board', 'list_sprints', 'get_sprint_issues', 'get_backlog', 'get_active_sprint', 'search_sprints', 'create_sprint', 'move_to_sprint' |
| manage_devinfoC | Get development information (branches, PRs, commits) linked to a Jira issue. Actions: 'get_dev_info' |
| manage_issuesC | Unified tool for Jira issue operations. Actions: 'get', 'list_types', 'get_links', 'get_history', 'create', 'update', 'assign', 'transition', 'add_comment', 'edit_comment', 'list_comments', 'delete', 'link', 'list_link_types', 'get_watchers', 'add_watcher', 'remove_watcher', 'move' |
| manage_metricsA | Get issue lifecycle metrics for dashboards and visualizations. Actions: 'get_dates' (raw date info, status transitions, time-in-status), 'get_metrics' (computed cycle time, lead time, time in current status, status breakdown) |
| manage_projectsB | List and get Jira project details and statuses. Actions: 'list', 'get', 'list_statuses', 'create' |
| manage_searchA | Search Jira issues using JQL or quick text search. Actions: 'jql', 'quick' |
| manage_usersC | Search and get Jira users. Actions: 'get_current', 'search', 'get' |
| manage_versionsC | List and get project versions (releases/fixVersions). Actions: 'list', 'get' |
| manage_worklogsB | Manage time tracking worklogs on Jira issues. Actions: 'list', 'add' |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| dev_tree | Analyze development work (branches, PRs, commits) for an issue and its subtasks |
| release_notes | Generate release notes from a Jira version/release |
| sprint_status | Get current sprint status and progress |
| standup_report | Generate a standup report from recent Jira activity |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zach-snell/jtk'
If you have feedback or need assistance with the MCP directory API, please join our Discord server