Jira & Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBOSE | No | Enable debug logging (set to 'true') | |
| JIRA_URL | No | Override Jira URL (overrides ATLASSIAN_URL for Jira) | |
| MCP_PORT | No | Port for the MCP server (default: 9339) | 9339 |
| ATLASSIAN_URL | Yes | Your Atlassian instance URL (e.g., https://your-org.atlassian.net) | |
| CONFLUENCE_URL | No | Override Confluence URL (overrides ATLASSIAN_URL for Confluence) | |
| JIRA_API_TOKEN | No | Override Jira API token (overrides ATLASSIAN_API_TOKEN for Jira) | |
| ATLASSIAN_EMAIL | Yes | Your email address for Atlassian API authentication | |
| JIRA_PROJECT_KEY | No | Restrict Jira operations to a specific project key | |
| IGNORE_TLS_ERRORS | No | Set to 'true' to ignore TLS errors (useful in corporate networks) | false |
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian API token (get from https://id.atlassian.com/manage-profile/security/api-tokens) | |
| CONFLUENCE_API_TOKEN | No | Override Confluence API token (overrides ATLASSIAN_API_TOKEN for Confluence) | |
| CONFLUENCE_SPACE_KEY | No | Restrict Confluence operations to a specific space key |
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
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/thamaraiselvam/mcp-jira-confluence'
If you have feedback or need assistance with the MCP directory API, please join our Discord server