mcp-jira-tempo
by huginnnx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging by setting to 'true'. | |
| TEMPO_API_TOKEN | No | API token for Tempo Cloud. Required to enable Tempo tools. | |
| TEMPO_API_BASE_URL | No | Base URL for Tempo API (default: https://api.tempo.io/4). | https://api.tempo.io/4 |
| ATLASSIAN_API_TOKEN | No | Jira API token for authentication in legacy single-site mode. | |
| ATLASSIAN_SITE_NAME | No | Jira site name (e.g., 'mycompany' for mycompany.atlassian.net). Used in legacy single-site mode. | |
| ATLASSIAN_USER_EMAIL | No | Email for Jira authentication in legacy single-site mode. | |
| ATLASSIAN_PROFILES_FILE | No | Path to a JSON file containing named Jira profiles with siteName, userEmail, apiToken. | |
| ATLASSIAN_DEFAULT_PROFILE | No | Overrides the default profile name from the profiles file. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- 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/huginnnx/mcp-jira-tempo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server