Support

Every project is maintained in the mcp-tool-shop-org GitHub organization. Issues on the relevant repository are the primary support channel, and every repository accepts them.

Reporting a bug

Open an issue on the repository for the tool. Reports that include the following get resolved fastest:

  1. What you expected to happen.
  2. What actually happened, including the full error message.
  3. Steps to reproduce the problem, or the exact command you ran.
  4. Environment: operating system, runtime version (Python, Node, or .NET), and the tool version.
  5. Logs, with any secrets redacted.

Most tools print a structured error with a code and a hint. Include that code in the issue title.

Feature requests

Open an issue with the enhancement label. Describe the use case rather than only the proposed solution; knowing why you need something helps us design the right thing.

Security

If you find a security vulnerability, do not open a public issue. Use GitHub's private vulnerability reporting on the affected repository. The organization-wide policy is in SECURITY.md.

Questions

For usage questions and ideas that are not bug reports, start a thread in GitHub Discussions.

Response expectations

This is a small open-source studio. We read every issue, and clear, reproducible reports are handled first. There is no paid support tier and no service-level agreement.

Problems with this site

Broken links, stale catalog data, or incorrect install commands belong in the site repository's issues.