Token导航 LogoToken导航

MCP Server · 开发工具

AIBacklogV4 MCP 1

一个可组合的通用代理平台,通过角色定义能力和权限,MCP服务器提供专用工具,实现智能任务编排,适用于Jira项目管理等多种场景。

stdio官方级别未说明来源级核验工具 6
ShellClaude开发工具Cursor

快速开始

作者 / 组织
wabpietersz
提供方
wabpietersz
运行时
Python

工具数量

6

来源目录标注

资源数量

0

来源目录标注

提示词数量

0

来源目录标注

GitHub Star

0

仓库热度

收录来源

1 个

MCP World

选型结论

AIBacklogV4 MCP 1 属于开发工具类 MCP Server,公开资料标注 6 个工具,通过stdio 本地进程接入,适配 Claude、Cursor,有可以直接复制的安装命令;接入前要先准备 OAuth 授权。

分类

开发工具

传输方式

stdio

认证方式

OAuth 授权

部署方式

公开资料未说明

安装与配置

安装命令

python -m venv .venv

公开命令不是通用的启动方式,拼不出可靠配置示例;请在客户端 MCP 配置里按官方文档填写 command 和 args。

上手步骤

  1. 1

    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2

    安装服务

    复制下面的安装命令执行;命令里带占位符的位置换成自己的密钥或路径。

  3. 3

    写入客户端配置

    在客户端的 MCP 配置里填启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4

    验证是否可用

    连接成功后客户端会列出 6 个工具,随便调一个只读工具确认能返回结果。

接入前确认

不要直接授予不必要的文件、网络或账号权限;先核对安装命令和配置内容。

详细介绍

Generic Agentic Platform (Jira Use Case)

Build once, reuse everywhere - A generic, composable agentic platform where agents orchestrate based on requirements, personas define capabilities, and MCP servers provide specialized tools.

First Use Case: Jira project management with persona-based agents (General User & Admin)

🎯 Project Vision

The Platform

Build a reusable foundation for agentic solutions:

  • Generic foundation layer - Reusable across any use case
  • Persona-based agents - Define capabilities and permissions
  • MCP server ecosystem - Specialized tools as services
  • Intelligent orchestration - Route tasks to appropriate agents
  • Unified frontend - Works with any agent

First Implementation: Jira Assistant

Two persona-based agents for Jira:

  • General User Agent: Read info, create basic items, manage own issues
  • Admin Agent: Full project management capabilities

🏗️ Current Status

Phase 1: Backend (Week 1 of 4)

Building the foundation layer for ANY agentic solution

🚀 Quick Start (Phase 1)

Prerequisites

  • Python 3.10+
  • Azure account
  • Jira Cloud or Server instance
  • Jira API token or Personal Access Token

Setup

# 1. Clone and setup
git clone 
cd Chat-MCP-Jira-V1
python -m venv .venv
source .venv/bin/activate  # Windows: .venv\Scripts\activate

# 2. Install dependencies
pip install -e ".[dev]"

# 3. Configure environment
cp .env.example .env
# Edit .env with your Jira credentials

# 4. Run locally
python -m jira_mcp --transport stdio -v

Test with MCP Inspector

npx @modelcontextprotocol/inspector python -m jira_mcp

📋 Development Phases

Phase 1: Backend (4 weeks) ← YOU ARE HERE

Build the generic foundation + Jira implementation:

Week 1: Foundation Layer (Generic & Reusable)

  • ✅ BaseAgent, Persona, AgentResponse
  • ✅ MCPClientManager (connect to multiple MCP servers)
  • ✅ ToolRegistry (discover and filter tools)
  • ✅ Permission system

Week 2: Jira MCP Server

  • ✅ 12 Jira tools (search, CRUD, sprints, etc.)
  • ✅ Deployed to Azure Container Apps
  • ✅ Integrated with foundation

Week 3: Persona Agents

  • ✅ General User Agent (limited permissions)
  • ✅ Admin Agent (full access)
  • ✅ Permission enforcement

Week 4: Orchestrator

  • ✅ Route to appropriate persona agent
  • ✅ FastAPI backend
  • ✅ /execute and /personas endpoints

Deliverable: Backend API that can be reused for ANY use case

See: AGENT_IMPLEMENTATION_PLAN.md ⭐ START HERE

Phase 2: Frontend (3 weeks) - FUTURE

Build persona-aware chat UI:

  • Week 5: Persona selector + Next.js setup
  • Week 6: Chat interface with LLM
  • Week 7: Polish and deploy

Deliverable: Chat UI that works with any persona/use case

See: AGENT_ARCHITECTURE.md for frontend design

🏗️ Architecture

5-Layer Agent-Centric Design

Layer 5: Frontend (Persona-Aware UI)
   ↓
Layer 4: Orchestrator (Routes to persona agents)
   ↓
Layer 3: Persona Agents (General User | Admin)
   ↓
Layer 2: MCP Servers (Jira | Graph | Azure AI)
   ↓
Layer 1: Foundation (Generic & Reusable)

See: AGENT_ARCHITECTURE.md for detailed architecture

Example: General User vs Admin

# General User - Limited permissions
general_user_persona = Persona(
    name="general_user",
    permissions=[
        Permission("jira", "read", "*"),      # Read all
        Permission("jira", "write", "own"),   # Write own only
    ],
    allowed_tools=[
        "jira_search",
        "jira_get_issue",
        "jira_create_issue",
        "jira_update_issue",  # Filtered to own issues
    ]
)

# Admin - Full permissions
admin_persona = Persona(
    name="admin",
    permissions=[
        Permission("jira", "*", "*"),  # All permissions
    ],
    allowed_tools=[
        "jira_search",
        "jira_delete_issue",
        "jira_create_sprint",
        "jira_bulk_update",
        # ... all tools
    ]
)

🔑 Authentication

Supports multiple authentication methods:

Priority 1: Per-Request Token

# OAuth (Cloud)
curl -H "Authorization: Bearer " \
     https://jira-mcp-server.azurecontainerapps.io/mcp

# PAT (Server/DC)
curl -H "Authorization: Token 
" \
     https://jira-mcp-server.azurecontainerapps.io/mcp

Priority 2: Server-Level Config

# Environment variables
JIRA_URL=https://your-domain.atlassian.net
JIRA_USERNAME=sa.jira.mscopilot.uat@ifs.com
JIRA_API_TOKEN=

Priority 3: Azure AD (Future)

AZURE_CLIENT_ID=
AZURE_TENANT_ID=
AZURE_USE_MANAGED_IDENTITY=true

🛠️ Tools (Phase 1)

Core Tools (Priority 0)

  • jira_search - Search issues using JQL
  • jira_get_issue - Get issue details
  • jira_create_issue - Create new issue
  • jira_update_issue - Update existing issue
  • jira_add_comment - Add comment to issue
  • jira_transition_issue - Change issue status

Advanced Tools (Priority 1 - Future)

  • Sprint/board management
  • Worklog tracking
  • Issue linking
  • Batch operations

🧪 Testing

# Run all tests
pytest

# Run with coverage
pytest --cov=src/jira_mcp --cov-report=html

# Run integration tests
pytest tests/integration/ -v

🚢 Deployment

Docker

# Build
docker build -t jira-mcp-server:latest .

# Run locally
docker run --env-file .env -p 8000:8000 jira-mcp-server:latest

# Health check
curl http://localhost:8000/healthz

Azure Container Apps

# Build and push to ACR
az acr login --name 
docker tag jira-mcp-server:latest .azurecr.io/jira-mcp-server:latest
docker push .azurecr.io/jira-mcp-server:latest

# Deploy
az containerapp create \
  --name jira-mcp-server \
  --resource-group jira-mcp-rg \
  --environment jira-mcp-env \
  --image .azurecr.io/jira-mcp-server:latest \
  --target-port 8000 \
  --ingress external \
  --min-replicas 1 \
  --max-replicas 5

See PHASE1_IMPLEMENTATION.md Week 5 for complete deployment guide.

🤖 Microsoft Agent Framework Integration

Python Agent

from mcp.client.streamable_http import streamablehttp_client
from mcp import ClientSession

async with streamablehttp_client(
    "https://jira-mcp-server.azurecontainerapps.io/mcp",
    headers={"Authorization": f"Bearer {token}"}
) as (read, write, _):
    async with ClientSession(read, write) as session:
        await session.initialize()
        result = await session.call_tool(
            "jira_search",
            {"jql": "project = JB AND status = Open"}
        )

.NET Agent

using Microsoft.Agents.AI;
using Microsoft.Agents.MCP;

var agent = new Agent("JiraAgent")
    .WithMCPServer("https://jira-mcp-server.azurecontainerapps.io/mcp")
    .WithAzureAD();

var result = await agent.RunAsync("Find all P0 bugs in project JB");

🎓 Why This Architecture?

Reusability

Each layer is independent and reusable:

  • Foundation works for any use case (HR, support, sales, etc.)
  • MCP servers are composable services
  • Personas apply to any domain
  • Frontend works with any agents

Example: Add HR Use Case

To add HR onboarding, just add:

  1. HR MCP Server - Employee DB, benefits tools
  2. Personas: New Employee, HR Admin
  3. Agents: NewEmployeeAgent, HRAdminAgent
  4. Done - Same foundation, same frontend

Security

  • Permissions enforced at agent layer
  • Tools filtered per persona
  • JQL auto-filtered for scope
  • Azure AD authentication
  • Full audit trail

📚 Documentation

DocumentPurpose
README.mdThis file - project overview
AGENT_ARCHITECTURE.mdAgent-centric architecture - Read this first!
AGENT_IMPLEMENTATION_PLAN.md⭐ START CODING HERE - Week-by-week guide
PHASED_APPROACH.mdOriginal two-phase approach
PHASE1_IMPLEMENTATION.mdOriginal MCP server plan
ARCHITECTURE.mdOriginal hybrid architecture
CLAUDE.mdDevelopment guide for Claude Code

🎓 Reference Implementations

This project leverages proven patterns from:

- Cloned to /tmp/mcp-atlassian for reference

🏃 Getting Started

🎯 Start Here: Week 1 - Foundation Layer

Build the generic, reusable foundation that works for ANY use case:

Day 1-2: Project structure + Persona system

mkdir -p src/{foundation,agents,orchestration,mcp_servers}
# Create BaseAgent, Persona, Permission classes

Day 2-3: Agent framework

# Create BaseAgent with execute() method
# Create AgentResponse standardized format

Day 3-4: MCP Client Manager

# MCPClientManager - connect to multiple MCP servers
# ToolRegistry - discover and filter tools

Day 4-5: Permission system

# PermissionChecker - validate tool usage
# JQL filtering for personas

Follow: AGENT_IMPLEMENTATION_PLAN.md ⭐ START CODING HERE

Key Files (Week 1)

src/foundation/
├── agents/
│   ├── base_agent.py        # BaseAgent abstract class
│   ├── persona.py           # Persona + Permission
│   └── agent_response.py    # Standardized response
├── mcp/
│   ├── client_manager.py    # MCPClientManager
│   └── tool_registry.py     # ToolRegistry
└── auth/
    └── permission_checker.py

🤝 Contributing

This is a platform, not just a Jira tool. Contributions should maintain the generic, reusable nature of the foundation layer.

📝 License

[Add your license here]

🙋 Support

For questions:



🎯 Ready to Start?

👉 START HERE: Complete Organization Guide 👈

The START_HERE.md document provides:

  • Complete reading order for all documentation
  • Pre-flight checklist for tomorrow
  • Quick decision tree
  • Success metrics
  • Cursor prompt template

Everything is organized and ready for you to start building tomorrow!

Quick Links


Good luck building the platform! 🚀

工具与能力

工具数量

6

资源数量

0

提示词数量

0

能力标签

Shell本地部署代理平台任务编排角色代理Jira集成MCP服务器

支持客户端

ClaudeCursor

数量来自来源目录的标注,具体工具清单以官方文档为准。

典型使用场景

让助手直接读代码

把仓库、提交记录和 issue 交给模型检索,补全和重构时不用来回复制文件。

在对话里跑命令

触发构建、测试和脚本,执行结果直接回到上下文,省去切终端。

接进开发流程

把 PR、CI 状态和代码审查接进助手,减少在几个工具之间跳。

选择建议

值得选的地方

  • 只提供 6 个工具,职责集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已经适配 Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好 Python,换机器要重新装一遍。
  • 需要自备OAuth 授权,没有凭据没法直接试。
  • 第三方目录整理,版本更新和行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 暂时拿不到OAuth 授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

5 个同类
MCP Server工具数传输方式安装命令收录来源最后核验
AIBacklogV4 MCP 1

MCP World · 本页

6stdio有1 个2026-05-17
Git 838e2ec1

MCP World

12stdio有2 个2026-05-17
Markitdown MCP 2c653a5f

MCP World

1stdio有1 个2026-05-17
Context7 MCP C671e75a

MCP World

0stdio有1 个2026-05-17
Context7 831acf40

MCP World

0stdio有1 个2026-05-17

按同分类和工具数量挑出最接近的几条,字段以各自详情页为准。

常见问题

5 条

AIBacklogV4 MCP 1 怎么安装?

公开资料给出的安装命令是 python -m venv .venv,运行环境为 Python。装完后按客户端要求写进 MCP 配置,重启客户端生效。

AIBacklogV4 MCP 1 怎么在 Claude Desktop、Cursor 里配置?

它是stdio 本地进程,客户端配置里要写启动命令和参数,运行环境是 Python;保存后完全退出客户端再打开,配置才会生效。

AIBacklogV4 MCP 1 收费吗?

本站只整理公开资料,不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

AIBacklogV4 MCP 1 需要 API Key 吗?

公开资料标注的认证方式是OAuth 授权,也就是要先拿到凭据才能连上;凭据只填在自己本地的配置里,不要写进公开仓库。

AIBacklogV4 MCP 1 支持哪些客户端?

公开资料标注支持 Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

来源信息

继续浏览同类 MCP