Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"gouqi-mcp-server": {
"args": [
"-y",
"@modelcontextprotocol/inspector"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An AI-friendly JIRA integration server using the Model Context Protocol (MCP). This server provides semantic tools for searching, retrieving, and interacting with JIRA issues without requiring knowledge of JQL or JIRA internals.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@modelcontextprotocol/inspector' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server
An XSS flaw exists in the MCP Inspector local development tool when it renders a redirect URL returned by a remote MCP server. If the Inspector connects to an untrusted server, a crafted redirect can inject script into the Inspector context and, via the built-in proxy, be leveraged to trigger arbitrary command execution on the developer machine. Version 0.16.6 hardens URL handling/validation and prevents script execution. > Thank you to the following researchers for their reports and contributi
MCP Inspector proxy server lacks authentication between the Inspector client and proxy
Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities. Credit: Rémy Marot <bughunters@tenable.com>
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP Security Weekly
Get CVE alerts and security updates for Gouqi Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An AI-friendly JIRA integration server using the Model Context Protocol (MCP). This server provides semantic tools for searching, retrieving, and interacting with JIRA issues without requiring knowledge of JQL or JIRA internals.
Set up your JIRA connection using environment variables:
# Required: JIRA instance URL
export JIRA_URL="https://your-company.atlassian.net"
# Required: Authentication
export JIRA_AUTH_TYPE="pat" # or "basic", "bearer", "anonymous"
export JIRA_TOKEN="your_personal_access_token"
# Optional: Advanced settings
export JIRA_CACHE_TTL="300" # Cache TTL in seconds (default: 300)
export JIRA_MAX_RESULTS="50" # Max search results (default: 50, max: 200)
export JIRA_REQUEST_TIMEOUT="30" # Request timeout in seconds (default: 30)
# Clone and build
git clone https://github.com/yourusername/gouqi-mcp-server.git
cd gouqi-mcp-server
cargo build --release
# Run the server
./target/release/jira-mcp-server
# Test tools
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | ./target/debug/jira-mcp-server
# Test connection
echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"test_connection","arguments":{}}}' | ./target/debug/jira-mcp-server
search_issuesSearch for JIRA issues using AI-friendly semantic parameters.
Example Usage:
{
"issue_types": ["story", "bug"],
"assigned_to": "me",
"status": ["open", "in_progress"],
"project_key": "PROJ",
"created_after": "7 days ago",
"limit": 25
}
get_issue_detailsGet detailed information about a specific JIRA issue.
Example Usage:
{
"issue_key": "PROJ-123",
"include_comments": true,
"include_attachments": true
}
get_user_issuesGet issues assigned to a specific user with filtering options.
Example Usage:
{
"username": "me",
"status_filter": ["open", "in_progress"],
"issue_types": ["story", "bug"],
"due_date_filter": "overdue"
}
get_server_statusGet server status and JIRA connection information.
test_connectionTest JIRA connection and authentication.
clear_cacheClear all cached metadata.
jira-mcp-server/
├── Cargo.toml # Package configuration
├── src/
│ ├── main.rs # Server entry point
│ ├── lib.rs # Main server implementation
│ ├── config.rs # Configuration management
│ ├── cache.rs # Metadata caching
│ ├── jira_client.rs # JIRA API wrapper
│ ├── semantic_mapping.rs # AI-friendly parameter mapping
│ ├── error.rs # Error types and handling
│ └── tools/ # MCP tool implementations
│ ├── mod.rs
│ ├── search_issues.rs
│ ├── issue_details.rs
│ └── user_issues.rs
├── config/
│ └── jira-mcp-config.toml.example # Configuration example
└── README.md
# Required
JIRA_URL="https://your-instance.atlassian.net"
JIRA_AUTH_TYPE="pat" # "pat", "basic", "bearer", "anonymous"
JIRA_TOKEN="your_token"
# For Basic Auth
JIRA_USERNAME="your_username"
JIRA_PASSWORD="your_password" # pragma: allowlist secret
# Optional
JIR
... [View full README on GitHub](https://github.com/wunderfrucht/gouqi-mcp-server#readme)