hive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | Base URL of your Jira instance (on-premise Server/Data Center) | |
| JIRA_API_TOKEN | Yes | Personal Access Token for Jira API authentication | |
| SOURCEGRAPH_URL | Yes | URL of your Sourcegraph instance | |
| SOURCEGRAPH_TOKEN | Yes | Access token for Sourcegraph API |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_issueA | Get detailed information about a Jira issue by its key or ID (e.g., PROJ-123). IMPORTANT: Use the fields parameter to control response size and avoid token limits. Default fields provide essential info (summary, status, priority, assignee, reporter, created, updated, issuetype) without bloating response. |
| jira_get_commentsA | Get comments from a Jira issue with pagination support. Returns comment history with authors, timestamps, and content. Use pagination parameters to control response size and avoid token limits. |
| jira_add_commentA | Add a comment to a Jira issue |
| jira_list_attachmentsA | List all attachments for a Jira issue. Returns attachment metadata including IDs, filenames, sizes, and mime types. |
| jira_read_attachmentA | Read a specific Jira attachment by ID. Returns the attachment content (images as blob, other files as base64). Files larger than 500KB will return metadata only. |
| sourcegraph_search_codeB | Search code across repositories using Sourcegraph. Supports various search operators like repo:, file:, lang:, count:, patterntype:, etc. |
| sourcegraph_deep_searchA | AI-powered Deep Search that understands natural language questions about your codebase. Ask questions like "How does authentication work?" or "Where are API endpoints defined?". This uses Sourcegraph's agentic search (REST API v6.7+) and may take 10-60 seconds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jira Issue Attachments List | List all attachments for a Jira issue. Replace {issueKey} with actual issue key (e.g., PROJ-123) |
| Jira Attachment Content | Read specific attachment content. Replace {attachmentId} with actual attachment ID (e.g., 10041) |
TDQS
Scored across 7 tools
The Jira and Sourcegraph tools are cleanly separated by prefix and purpose. Each Jira tool targets a distinct resource (issue, comments, attachments), and the two Sourcegraph tools are clearly differentiated by search mode.
All tool names follow a consistent snake_case pattern with a service prefix (jira_ or sourcegraph_) followed by a clear verb_noun structure (e.g., get_issue, add_comment, search_code). No mixed conventions.
The 7-tool count is within the ideal range, but the server spans two distinct domains (Jira and Sourcegraph), which slightly dilutes focus. Still, each tool earns its place for basic workflows.
The Jira coverage lacks core operations like create_issue, update_issue, or delete_issue, limiting workflow completion. Sourcegraph only offers search and deep search, with no direct file retrieval or repository browsing, leaving notable gaps for a development tool.