Schema | jira-issue-context-mcp

jira-issue-context-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`JIRA_EMAIL`	No	Email address for Atlassian Cloud API token authentication
`JIRA_BASE_URL`	Yes	Base URL of your Jira instance, e.g. https://your-domain.atlassian.net
`JIRA_API_TOKEN`	No	API token for Atlassian Cloud authentication
`JIRA_ISSUE_KEY`	No	Fallback issue key if not provided in tool call
`JIRA_COOKIE_NAME`	No	Name of the session cookie (default is tenant.session.token)
`JIRA_BEARER_TOKEN`	No	Bearer token for authentication
`JIRA_MAX_IMAGE_MB`	No	Maximum image size in MB for attachments (default 8)
`JIRA_SESSION_TOKEN`	No	Session cookie value for cookie-based authentication

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
jira_issue_contextA	Devuelve contexto read-only de una issue concreta: titulo, descripcion, comentarios y adjuntos de imagen. Cuando el usuario escriba una clave Jira en el chat, pasala como issueKey.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/formonkey/jira-issue-context-mcp'

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