jira-worklog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_BASE_URL | Yes | Your Jira site URL, e.g. https://your-site.atlassian.net | |
| JIRA_API_TOKEN | Yes | Your Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_worklogA | Log work against a Jira issue (POST worklog). issue_key is the ticket (e.g. LEGLINK-142), time_spent_seconds is the duration, started defaults to now (RFC3339; normalized to Jira's required format), and comment is optional. Jira records time at minute granularity (minimum 60s). |
| list_worklogsA | List the worklogs on a Jira issue (id, author, time, started, comment). Useful to verify what was logged or to check for duplicates before adding more. |
| whoamiA | Return the authenticated Jira user (display name, accountId, email). Use to confirm credentials. |
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/MikeAtPinnacle/jira-worklog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server