# Contact

GitHub is the real channel. Everything about MCP Manager happens in the open on the repository, so a public issue gets a faster answer than anything else and leaves an answer behind for the next person with the same problem.

## Something is broken

Open an issue: [github.com/31Carlton7/mcp-manager/issues](https://github.com/31Carlton7/mcp-manager/issues)

Please include your macOS version, the MCP Manager version, which client you were syncing to, and what the config file looked like before and after. A bad config file is usually the whole story, and having it means the fix takes minutes instead of a week of back and forth.

## You want it to do something it does not do

Same place, open an issue and say what you were trying to get done. Feature requests that describe the actual workflow are much easier to act on than ones that describe a button.

## You found a security problem

Do not open a public issue for it. Report it privately through GitHub security advisories: [github.com/31Carlton7/mcp-manager/security/advisories/new](https://github.com/31Carlton7/mcp-manager/security/advisories/new). That opens a private thread with the maintainer, and it stays private until there is a fix to ship.

## You want to send a patch

Fork it, branch it, open a pull request. The repository is MIT licensed, and the README covers the layout and how to build it.

## No support inbox

There is no support email address and no contact form. One person maintains this app, and email would just become a slower, less searchable version of the issue tracker. If your question is not something you can post in public, say so in an issue and it can move somewhere private from there.

## Links

- [Issues](https://github.com/31Carlton7/mcp-manager/issues)
- [Security advisories](https://github.com/31Carlton7/mcp-manager/security/advisories/new)
- [Source on GitHub](https://github.com/31Carlton7/mcp-manager)
- [About](https://mcpmanager.space/about)