# Getting Help
replicant-mcp is an open-source project maintained on a best-effort basis. Here's how to get help.
## Reporting Bugs
File a [GitHub Issue](https://github.com/thecombatwombat/replicant-mcp/issues) for bugs and defects. Include the following information to help us diagnose the problem:
### Bug Report Checklist
- [ ] **OS and version** (e.g., macOS 15.1, Ubuntu 24.04)
- [ ] **Node.js version** (`node --version`)
- [ ] **replicant-mcp version** (`npx replicant-mcp --version`)
- [ ] **`replicant-mcp doctor` output** (run `npx replicant-mcp doctor` and paste the result)
- [ ] **Steps to reproduce** (minimal sequence to trigger the issue)
- [ ] **Expected vs. actual behavior**
- [ ] **Relevant logs or error messages**
### Tips for Good Bug Reports
- Search existing issues first to avoid duplicates.
- Use a clear, descriptive title.
- Include the exact command or tool call that triggered the issue.
- If the issue involves UI automation, include the output of `ui dump` when relevant.
## Response Times
This is a community-maintained open-source project. We do our best to respond to issues, but there are no guaranteed response times or SLAs. If your issue is blocking, consider submitting a pull request with a fix.
## Security Issues
If you discover a security vulnerability, please do **not** open a public issue. Instead, use [GitHub's private vulnerability reporting](https://github.com/thecombatwombat/replicant-mcp/security/advisories/new) to report it responsibly.
