Backlog MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Backlog MCP Server?

Backlog MCP Server is an implementation that integrates the Backlog API, allowing users to manage projects, issues, and wikis effectively.

How to use Backlog MCP Server?

To use the Backlog MCP Server, you need to sign up for a Backlog account, generate an API key, and configure the server with your API key and space ID. You can run it using NPX or Docker.

Key features of Backlog MCP Server?

  • Project management through the Backlog API
  • Issue tracking and management
  • Wiki creation and management
  • Easy integration with existing workflows

Use cases of Backlog MCP Server?

  1. Managing software development projects with issue tracking.
  2. Collaborating on documentation through wikis.
  3. Automating project updates and issue management.

FAQ from Backlog MCP Server?

  • How do I get an API key?

Sign up for a Backlog account and generate your API key from the individual settings.

  • Can I run this server using Docker?

Yes! You can run the server using Docker with the provided configuration.

  • Is there a free plan available?

Yes! Backlog offers a free plan for users.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago