{"id":"safx-backlog-mcp-server-rust","name":"backlog-mcp-server-rust","homepage":null,"repo_url":"https://github.com/safx/backlog-mcp-server-rust","category":"automation","subcategories":[],"tags":["mcp","backlog","project-management","automation","rust","api-integration"],"what_it_does":"Backlog MCP server that exposes Backlog (project management) functionality as an MCP server with tools for reading and, optionally, writing to issues, PRs/comments, wiki pages, documents, shared files, and listing users/status/custom fields.","use_cases":["Automate issue research and summarization from a Backlog space","Create/update issues and comments with AI-assisted workflows","Manage wiki content and attachments via MCP-enabled agents","Browse PRs and add PR comments using an AI agent","Download and analyze attachments/documents from Backlog"],"not_for":["Public multi-tenant deployment without careful credential handling","Use cases requiring fine-grained role-based authorization beyond the Backlog API key permissions","Environments that require a documented SLA/status or detailed operational guarantees"],"best_when":"You want an MCP-compatible agent workflow for Backlog that can be constrained to specific projects and optionally limited to read-only by building without writable features.","avoid_when":"You cannot securely supply/store BACKLOG_API_KEY or you need clear documented guarantees about rate limiting, retries, and error semantics from the MCP server.","alternatives":["Backlog API directly (custom integration)","Backlog CLI tool (blg) for human or scripted automation","Other MCP servers (if available) for project management/work-item platforms"],"af_score":63.0,"security_score":61.2,"reliability_score":31.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:38:28.102406+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":["API key via BACKLOG_API_KEY environment variable"],"oauth":false,"scopes":false,"notes":"Authentication is handled by Backlog API key supplied to the MCP server via environment variable. No OAuth flows or documented fine-grained scopes at the MCP layer are described."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing is not described for the MCP server itself; Backlog API usage is dependent on your Backlog plan."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":63.0,"security_score":61.2,"reliability_score":31.2,"mcp_server_quality":85.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":20.0,"tls_enforcement":90.0,"auth_strength":65.0,"scope_granularity":35.0,"dependency_hygiene":40.0,"secret_handling":70.0,"security_notes":"Uses BACKLOG_API_KEY via environment variables as the primary credential mechanism. README does not describe MCP-level logging/redaction, nor TLS/HTTP details for outbound calls (assumed HTTPS to Backlog base URL). Authorization appears coarse (single API key) with optional project allowlisting via BACKLOG_PROJECTS; no fine-grained per-tool scopes are described. Dependency hygiene and vulnerability status are not evidenced in the provided content.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":45.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guarantees or guidance for retrying write operations are documented. Some tools perform updates/creates/deletes, which may not be safe to retry without application-level safeguards.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Write operations are controlled via Cargo feature flags (issue_writable, git_writable, wiki_writable, document_writable); deploying a server without the intended features may cause missing-tool behavior.","Tool name prefix can be changed via BACKLOG_PREFIX; agents relying on exact tool names should confirm effective prefix configuration.","Tool set includes both read and write tools; agents should be configured/allowed with least-privilege tool lists to avoid unintended changes."]}}