GitHub Kanban MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is GitHub Kanban MCP Server?

GitHub Kanban MCP Server is a server designed to manage GitHub issues in a kanban board format, enhancing task management through the Model Context Protocol (MCP) for large language models (LLMs).

How to use GitHub Kanban MCP Server?

To use the server, install it via npm, authenticate with GitHub CLI, and configure the MCP settings to integrate with your GitHub repository.

Key features of GitHub Kanban MCP Server?

  • Manage GitHub issues in a kanban format
  • Automated task management using LLMs
  • Visualize project progress
  • Full integration with GitHub
  • Commenting functionality on tasks

Use cases of GitHub Kanban MCP Server?

  1. Organizing and tracking GitHub issues visually.
  2. Automating task assignments and updates.
  3. Enhancing team collaboration through comments and progress tracking.

FAQ from GitHub Kanban MCP Server?

  • Can I use this server for any GitHub repository?

Yes! It can be integrated with any GitHub repository that you have access to.

  • Is there a cost associated with using this server?

No, it is open-source and free to use under the MIT License.

  • What are the prerequisites for installation?

You need Node.js 18.x or higher, npm 9.x or higher, and GitHub CLI.

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

Recommend Servers

View All
Payai X402 Tools

6 hours ago
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.

a day ago