Backlog MCP サーバー

Created By
tmhr1850a year ago
Overview

what is Backlog MCP Server?

Backlog MCP Server is an API server that provides access to the Backlog API, enabling project management, issue tracking, and file operations.

how to use Backlog MCP Server?

To use the Backlog MCP Server, you need to obtain an API key from Backlog, set up your environment variables, and run the server locally or through a command line interface.

key features of Backlog MCP Server?

  • Project Management: Retrieve project lists and view details.
  • Issue Management: Create, update, search, and comment on issues.
  • User Management: Access user information.
  • File Operations: Manage attached files.
  • Commenting: Add comments to issues.
  • Search Functionality: Search for issues and projects.

use cases of Backlog MCP Server?

  1. Managing project tasks and tracking progress.
  2. Collaborating on issues with team members.
  3. Automating project management workflows through API calls.

FAQ from Backlog MCP Server?

  • How do I obtain an API key?

Log in to Backlog, go to personal settings, and generate an API key.

  • Is there a limit on the number of issues I can create?

No, but the API has a maximum return limit of 100 issues per request.

  • What programming language is used for this project?

The project is developed in TypeScript.

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

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago