Ejento AI
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. MCP Tools Setup
  • How to Setup Ejento on Azure
  • Prerequisites
  • Deployment on Azure
  • Setup After Deployment
    • Custom Domain Set Up
    • Microsoft SSO Authentication
    • Okta SSO Authentication
    • SharePoint Connection Set Up
    • Developer API Set Up
    • SSO and SharePoint App Set Up (for Developers)
  • MCP Tools Setup
    • Slack
    • Jira
  • Overview
    • Azure Resources
  1. MCP Tools Setup

Jira

Jira MCP Server Configuration Guide#

This guide provides step-by-step instructions for configuring the Jira MCP Server, including required environment variables and their detailed explanations.

1. Required Environment Variables#

To configure and run the Jira MCP Server successfully, the following environment variables must be set.

1.1 JIRA_URL#

Description:
The base URL of your Jira instance.
Format:
https://<your-domain>.atlassian.net/
Note: Always include the trailing slash / at the end of the URL.
Examples:
Cloud: https://yourcompany.atlassian.net/
Server/Data Center: https://jira.yourcompany.com/

1.2 JIRA_USERNAME#

Description:
The email address associated with your Jira account.
Format:
user@company.com
How to Find:
1.
Log in to your Jira account.
2.
Click your profile icon (top-right corner).
3.
Click Profile.
4.
Your email address will be displayed under your name.

1.3 JIRA_API_TOKEN#

Description:
An API token used for authentication with Jira.
How to Obtain:
1.
Go to Atlassian API Tokens
2.
Click Create API token.
3.
Enter a descriptive label (e.g., MCP Server Token).
4.
Click Create.
5.
Copy the generated token immediately (it will not be shown again).
6.
Store it securely.
Jira1.png
Security Note:
API tokens inherit all permissions of your Jira user account. For production environments, it is recommended to use a service account with restricted permissions.
Token Format Example:
ATATT3xFfGF0...

1.4 ENABLED_TOOLS#

Description:
A comma-separated list of Jira operations (tools) that the MCP server can use.
Example Value
Here is a possible value you can use for this environment variable that enables all important tools:
"jira_search,jira_get_issue,jira_get_all_projects,jira_get_project_issues,jira_get_worklog,jira_get_transitions,jira_search_fields,jira_get_agile_boards,jira_get_board_issues,jira_get_sprints_from_board,jira_get_sprint_issues,jira_get_issue_link_types,jira_get_user_profile,jira_download_attachments,jira_get_project_versions,jira_create_issue,jira_update_issue,jira_delete_issue,jira_batch_create_issues,jira_add_comment,jira_transition_issue,jira_add_worklog,jira_link_to_epic,jira_create_sprint,jira_update_sprint,jira_create_issue_link,jira_remove_issue_link,jira_create_version,jira_batch_create_versions"

Available Tools#

Read Operations:
jira_search
jira_get_issue
jira_get_all_projects
jira_get_project_issues
jira_get_worklog
jira_get_transitions
jira_search_fields
jira_get_agile_boards
jira_get_board_issues
jira_get_sprints_from_board
jira_get_sprint_issues
jira_get_issue_link_types
jira_get_user_profile
jira_download_attachments
jira_get_project_versions
Write Operations:
jira_create_issue
jira_update_issue
jira_delete_issue
jira_batch_create_issues
jira_add_comment
jira_transition_issue
jira_add_worklog
jira_link_to_epic
jira_create_sprint
jira_update_sprint
jira_create_issue_link
jira_remove_issue_link
jira_create_version
jira_batch_create_versions

Configuration Options#

Enable all tools for full functionality.
Remove write operations for read-only access.
Customize based on your organization’s security policies and user roles.

1.5 READ_ONLY_MODE#

Description:
When enabled, this variable disables all write operations, regardless of the ENABLED_TOOLS setting.
Values:
false → Allow write operations (if included in ENABLED_TOOLS)
true → Block all write operations
Use Case:
Enable this option to safely test your integration without making any changes to Jira data.

2. Summary of Environment Variables#

Environment VariableDescriptionExample / Recommended Value
JIRA_URLJira base URLhttps://yourcompany.atlassian.net/
JIRA_USERNAMEJira account emailadmin@yourcompany.com
JIRA_API_TOKENJira authentication tokenATATT3xFfGF0...
ENABLED_TOOLSEnabled Jira operationsAll tools (recommended)
READ_ONLY_MODEDisable write actionsfalse (or true for testing)

3. Tips & Best Practices#

Always use environment variables rather than hardcoding sensitive data.
Rotate API tokens regularly and revoke unused ones.
Use read-only mode in staging or test environments.

4. Troubleshooting#

Jira Authentication Issues#

Verify the URL includes protocol and trailing slash (e.g., https://yourcompany.atlassian.net/)
Confirm the email matches your Jira account

Azure Deployment Issues#

Check Application Insights logs for runtime errors
Verify all environment variables are set correctly
Confirm container registry credentials are configured properly
Review App Service logs for startup issues

5. Support Resources#

For additional assistance:
Jira API Documentation
Azure App Service Documentation
Previous
Slack
Next
Azure Resources