mcp-backlog-server

Created By
katsuhirohondaa year ago
Overview

What is MCP Backlog Server?

MCP Backlog Server is a TypeScript-based server that integrates Backlog with the Model Context Protocol (MCP). It implements key concepts of MCP to facilitate project management and data analysis.

How to use MCP Backlog Server?

To use the MCP Backlog Server, you need to set up the server with your Backlog API key and space URL, and then access it through the provided URIs and tools for managing Backlog projects.

Key features of MCP Backlog Server?

  • Access to Backlog projects via structured URIs.
  • Tools for retrieving user information, project issues, and wiki pages.
  • Prompts for summarizing projects and analyzing usage patterns.

Use cases of MCP Backlog Server?

  1. Managing and analyzing Backlog projects.
  2. Accessing and updating project issues and wiki pages.
  3. Generating summaries and usage reports for project management.

FAQ from MCP Backlog Server?

  • What are the requirements to use MCP Backlog Server?

You need a Backlog account with API access and specific environment variables set up.

  • How do I install MCP Backlog Server?

Install dependencies using npm, build the server, and configure it in your application settings.

  • Is there a debugging tool available?

Yes, you can use the MCP Inspector for debugging, which provides a URL for accessing debugging tools in the browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
katsuhirohonda
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
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)

a day ago