{"id":"bbak-mcs-mcp","name":"mcs-mcp","homepage":null,"repo_url":"https://github.com/bbak/mcs-mcp","category":"ai-ml","subcategories":[],"tags":["mcp","model-context-protocol","jira","forecasting","monte-carlo","flow-metrics","cycle-time","wip","analytics","go","observability","offline-caching"],"what_it_does":"An MCP server (Go binary) that ingests Atlassian Jira board issue transition history, reconstructs workflow semantics, and serves Monte-Carlo/flow diagnostics to AI agents (e.g., forecasting completion dates, capacity/bottleneck analysis, stability/predictability via control charts).","use_cases":["Monte-Carlo forecasting for work completion time or throughput","Backtesting/validating forecasts via walk-forward analysis","Diagnosing process stability and special-cause variation (cycle time/WIP/delivery cadence)","Bottleneck identification via semantic workflow mapping","Flow waste analysis (yield/abandonment)","WIP aging/residence-time analysis for stuck/neglected work","Capacity planning and stratified analytics by work item type (e.g., bug tax)","Retrospective analysis using historical time-travel reference dates"],"not_for":["Teams that require strict support for multiple Jira workflows mixed in one analysis (unless all share the same statuses/order)","Use cases needing a hosted SaaS API with centralized uptime/SLA and managed operations","Environments where storing any human-readable cache/logs on disk is unacceptable","Scenarios where customers need an official OpenAPI/REST interface rather than MCP tool calls"],"best_when":"You run an MCP-capable agent locally/privately and want offline-capable, board-scoped Jira flow analytics and forecasting based on event histories.","avoid_when":"You cannot guarantee consistent workflow status sets/order across analyzed issue types, or you require formal REST/GraphQL interfaces with standard cloud reliability guarantees.","alternatives":["Other MCP/Jira integration tools with analytics (if available internally)","Custom pipelines using Jira REST API + a forecasting/queuing model (e.g., Little’s Law/residence time approaches)","General-purpose Jira analytics platforms (for stability/throughput, but without MC simulation workflow semantics)"],"af_score":60.0,"security_score":56.2,"reliability_score":30.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:40:57.142730+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Jira API via Personal Access Token (PAT)","Jira API via Cloud API token + user email","Session cookies (fallback)"],"oauth":false,"scopes":false,"notes":"Authentication is configured via environment variables in .env. Cookie-based auth is explicitly described as a fallback and may expire or be blocked by Atlassian."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; appears to be a self-hosted open-source binary."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":60.0,"security_score":56.2,"reliability_score":30.0,"mcp_server_quality":82.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":65.0,"rate_limit_clarity":50.0,"tls_enforcement":60.0,"auth_strength":70.0,"scope_granularity":30.0,"dependency_hygiene":45.0,"secret_handling":70.0,"security_notes":"Self-hosted tool; authentication handled via env vars or cookies. README claims data minimization by dropping sensitive Jira fields (titles/descriptions/assignees) and persisting only analytical metadata (keys/types/status transitions/timestamps/resolution names). It also claims offline/local human-readable caches. TLS enforcement for the Jira/API communication is not explicitly stated; scope granularity is not described (PAT/API token likely broad). Beta nature does not directly imply security issues, but operational practices (permissions, disk protection, log sanitization) are important.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":35.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency/replay semantics described for MCP tools. Some caching exists, but operational idempotency guarantees are not documented.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Workflow discovery assumption: all work item types on a board share the same workflow and status order; mixed workflows may yield unpredictable analytics.","Server currently works on Boards and does not accept passing JQL; recommended workaround is creating a board using query as board-JQL.","Cookie-based Jira auth may break due to expiry/anti-bot measures; prefer PAT/API token modes for stability.","Beta warning: forecasting/math is not thoroughly verified; agent should treat forecasts as provisional and not as a hard decision basis.","Experimental mode requires both env gate (MCS_ALLOW_EXPERIMENTAL) and per-session tool activation; forgetting one step changes behavior."]}}