What prerequisites are needed to run the server?
Node.js v16 or higher, npm or yarn, and a Jira account with API access.
@MaximilianoGarciaRoe
Basic information
No overview available yet
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
An MCP server that enables interaction with Jira’s API, allowing users to retrieve issue information. It is intended for developers using Codeium’s MCP framework.
Install dependencies with npm, then configure the server in your Codeium MCP config file (~/.codeium/windsurf/mcp_config.json) by specifying the command npx -y tsx /path/to/jira_mcp/main.ts and setting the environment variables JIRA_USERNAME, JIRA_API_KEY, and JIRA_BASE_URL. The server is started automatically by Codeium when needed. Available commands include get_issue.
Node.js v16 or higher, npm or yarn, and a Jira account with API access.
Provide a valid Jira username, API key, and base URL as environment variables (`JIRA_USERNAME`, `JIRA_API_KEY`, `JIRA_BASE_URL`) in the MCP config file.
The server is started via command line using `npx` and `tsx`; details of the transport protocol are not specified in the README.
The README only documents one command (`get_issue`); no other capabilities or limits are mentioned.
a private MCP server for accessing Linear
A GitHub MCP Server extension for Zed
Put an end to code hallucinations! GitMCP is a free, open-source, remote MCP server for any GitHub project

Model Context Protocol Servers
🚀 All-in-one MCP server with AI search, RAG, and multi-service integrations (GitLab/Jira/Confluence/YouTube) for AI-enhanced development workflows. Folk from https://github.com/nguyenvanduocit/all-in-one-model-context-protocol
Comments