Schema | jira-mcp

jira-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`LOG_LEVEL`	No	Log level.	info
`JIRA_EMAIL`	Yes	The account email for the API token.
`JIRA_BASE_URL`	Yes	Your Jira site URL, e.g. https://your-org.atlassian.net, or the gateway URL for a scoped token.
`JIRA_MCP_HOST`	No	Public hostname, when behind a proxy.
`JIRA_MCP_PORT`	No	Host side of the published port.	8787
`JIRA_API_TOKEN`	Yes	API token from https://id.atlassian.com/manage-profile/security/api-tokens
`JIRA_MCP_TOKEN`	Yes	Shared secret clients present as bearer token.
`JIRA_MCP_LISTEN`	No	What the process itself binds; the image sets 0.0.0.0.	127.0.0.1
`JIRA_MCP_MEASURE`	No	Set to '1' to log per-call token counts.	off
`JIRA_DEFAULT_PROJECT`	No	Fallback project for create_issue.
`JIRA_MCP_BIND_ADDRESS`	No	Host side of the published port.	127.0.0.1
`JIRA_MCP_ALLOWED_HOSTS`	No	Extra Host values to accept, comma-separated.
`JIRA_MCP_STARTUP_CHECK`	No	Set to 'off' to skip the startup credential probe (CI, smoke tests).	on

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

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/jack-oval-traits/jira-mcp'

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