MCP Atlassian
by omkar9854
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | The URL of your Jira instance (e.g., https://your-company.atlassian.net). | |
| JIRA_USERNAME | No | Your Jira username or email address (required for Cloud). | |
| CONFLUENCE_URL | No | The URL of your Confluence instance (e.g., https://your-company.atlassian.net/wiki). | |
| JIRA_API_TOKEN | No | Your Jira API token (required for Cloud). | |
| JIRA_CLIENT_KEY | No | Path to the client key for Jira authentication. | |
| JIRA_SSL_VERIFY | No | Set to 'false' to disable SSL certificate verification for Jira. | |
| JIRA_CLIENT_CERT | No | Path to the client certificate for Jira authentication. | |
| CONFLUENCE_USERNAME | No | Your Confluence username or email address (required for Cloud). | |
| JIRA_PERSONAL_TOKEN | No | Personal Access Token for Jira Server/Data Center (replaces username/API token). | |
| CONFLUENCE_API_TOKEN | No | Your Confluence API token (required for Cloud). | |
| CONFLUENCE_CLIENT_KEY | No | Path to the client key for Confluence authentication. | |
| CONFLUENCE_SSL_VERIFY | No | Set to 'false' to disable SSL certificate verification for Confluence. | |
| CONFLUENCE_CLIENT_CERT | No | Path to the client certificate for Confluence authentication. | |
| CONFLUENCE_PERSONAL_TOKEN | No | Personal Access Token for Confluence Server/Data Center (replaces username/API token). |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
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
- 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/omkar9854/mcp-atlassian-onpremdc'
If you have feedback or need assistance with the MCP directory API, please join our Discord server