Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ATLASSIAN_TOKENNoYour Atlassian API token for authentication with Jira and Confluence

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

Save an Atlassian connection. Validates by calling /myself.

For security, prefer passing token as ${ENV_VAR} reference (e.g., "${ATLASSIAN_TOKEN}") rather than a literal value. The variable is expanded at runtime, never stored resolved.

logoutC

Remove a saved connection.

list_connectionsC

List saved connections (no secrets shown).

jira_get_issueC

Get a Jira issue by key. Returns full issue data including fields and status.

jira_searchC

Search Jira issues using JQL. Returns list of matching issues.

jira_get_commentsC

Get all comments for a Jira issue.

jira_get_transitionsC

Get available transitions for a Jira issue.

jira_add_commentB

Add a comment to a Jira issue. Uses wiki markup (API v2).

jira_edit_commentC

Edit an existing comment on a Jira issue. Uses wiki markup (API v2).

jira_transition_issueA

Transition a Jira issue to a new status. Use jira_get_transitions to discover available transitions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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/agentic-eng/a2atlassian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server