Reported issues for mcp-server

Pod holds 13 of 13 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mcp-server.

Most discussed

Self-hosted Packmind on Kubernetes fails to reach api.github.com

Summary

Self-hosted Packmind on Kubernetes fails to reach api.github.com from the API pod (getaddrinfo ENOTFOUND), which breaks the GitHub App manifest callback (POST .../github/app/manifest-callback → UI: “Setup failed / Internal server error”).

nslookup api.github.com works from the same pod; getent hosts api.github.com fails. Node uses libc getaddrinfo (same path as getent), so the app cannot resolve GitHub.

Environment

• Packmind: self-hosted via Helm (packmind-ai c

Read the thread · 2026-07-21 · closed · external user · 1 comment

Adding dark / light mode toggle

Description

Add a dark / light mode toggle to improve user experience and accessibility by allowing users to switch between light and dark themes based on their preference.

Use Case

Many users prefer dark mode for reduced eye strain, especially in low-light environments, while others prefer light mode for readability during daytime use.
Providing a theme toggle improves accessibility, personalization, and overall user satisfaction.

Proposed Solution

Implement a theme toggle butto

Read the thread · 2026-05-07 · open · external user · 1 comment

Update UI and documentation to use the word "Command" instead of "Recipe"

• Web app
• MCP
• cli
• Documentation
• OSS readme
• Update commit message to use "Commands" instead of "Recipes"

Read the thread · 2026-01-05 · closed · outside contributor · 3 comments

Drop "Recipes usage tracking"

We'll drop the tracking of recipes usages by Agents.

• Remove mcp tool notify_recipe_usage
• Drop rendering of "Recipes usage tracking"

Read the thread · 2025-12-04 · closed · outside contributor · 3 comments

[packmind-cli] install command improperly renders "Recipes usage tracking" section

Description

When deploying a package using packmind-cli install <my_package>, the "Recipes usage tracking" has incorrect properties:

## Recipe Usage Tracking:
When you DO use or apply a relevant Packmind recipe from .packmind/recipes/, you MUST call the 'packmind_notify_recipe_usage' MCP tool with:
* Recipe slugs array (e.g., ["recipe-name"] from "recipe-name.md")
* aiAgent: "Claude Code"
* gitRepo: "repository"
* target: "/"

Expected Behavior

When running the co

Read the thread · 2025-12-03 · closed · outside contributor · 1 comment

US: Add MCP to agent via packmind CLI

I want to setup the MCP for Claude, Cursor or Copilot with a single command line.

Read the thread · 2025-12-02 · closed · outside contributor · 3 comments

EPIC: provide linter based on standards' rules

Description

Given the non-deterministic nature of AI, generating code complying with a project syntax rules can be challenging. The goal here is to provide a custom linter based on rules listed in Packmind standards in both coding agent and continuous integration quality gates. Violations found can then easily fixed by AI or human developers.

Scope

• Add lint command in CLI
• Configure a rule to be detected
• Add MCP tool to help AI knows more about a rule violation and how to fi

Read the thread · 2025-11-28 · closed · outside contributor · 1 comment

Wrong token with Visual Studio Code extension

Description

I have an on premise Packmind that I'm trying to connect to my VSC with the API key. However the API key is received as invalid. Everything is setup on a private network and is allowed to contact each other through it.

Steps to Reproduce

1. Create a self hosted packmind
2. Connect packmind to self hosted Gitlab using projet token
3. Install packmind VSC extension
4. Generate API key in profile menu
5. Enter API key in VSC Packmind extension parameters (User and Workspace)

Read the thread · 2025-11-27 · closed · external user · 2 comments

Most recent

Skill authors can't declare three documented frontmatter fields when targeting Claude Code, Cursor, and GitHub Copilot

Some YAML frontmatter fields that the supported coding agents document on their public pages are silently dropped when Packmind renders a skill. Skill authors who write those fields see no error and no warning — the field is just missing in the deployed SKILL.md, which removes a feature their skill was relying on.

The three needs

1. A skill targeting Claude Code can declare its positional arguments. Today the autocomplete hint is supported, but the argument list itself (used to fill

Read the thread · 2026-05-22 · closed · outside contributor · 0 comments

EPIC: enable playbook (standards & recipes) distribution without Git configuration (aka "pull mode")

Description

As configuring access to Git providers can be challenging in some organizations for obvious security reasons, we want to provide an easier, less intrusive and more developer-friendly way to distribute Packmind artifacts. The idea is to provide tooling to allow local fetching of artifacts from a terminal or a coding agent through a CLI or MCP tool.

Scope

• The CLI exposes an install command, that fetch artifacts belonging to a Packmind package and render them as files usabl

Read the thread · 2025-11-28 · closed · outside contributor · 1 comment

Improve rule content generated through MCP tools

Description

The structure of the rule's content raised by AI Agents and MCP has room for improvement.

Current Behavior

Rules can have a quite long form and be difficult to read. Examples:

• Structure page layouts using a consistent PageLayout wrapper component with standardized padding and max-width constraints, while organizing header sections with the PageHeader component that includes title, description, and optional toolbar props.
• `Create centralized color and theme constants i

Read the thread · 2025-11-26 · closed · outside contributor · 0 comments

Feature request: Package and distribute Packmind standards and recipes

Description

Enable “packages” that group multiple Packmind standards and recipes for easy versioned distribution through the CLI, manageable from the UI, and supported by MCP commands during creation flows

Use Case

Today, distributing a curated set of standards and recipes across teams/org is manual and error-prone. There’s no unit to deploy, pull, and keep in sync. This slows adoption and increases divergence.

Proposed Solution

• I can manage packages of standards and recipes in t

Read the thread · 2025-11-13 · closed · outside contributor · 1 comment

Support GitHub app in addition to GitHub token

Description

The purpose is to authenticate Packmind to GitHub using a GitHub app, in addition to the existing PAT mode.

Motivation

In some companies, PAT is not possible, so setting up a GitHub app would be more useful.

Proposed Solution

To be discussed

Read the thread · 2025-11-10 · open · outside contributor · 0 comments

The remaining reports are on the project's issue tracker.