# How to Get Support for DeusData codebase-memory-mcp: GitHub Issues, Security Reports, and Enterprise Options

> Get support for DeusData codebase-memory-mcp via GitHub Issues for bugs and questions or email support@deusdata.com for enterprise solutions. Report security vulnerabilities through our dedicated policy.

- Repository: [Martin Vogel/codebase-memory-mcp](https://github.com/DeusData/codebase-memory-mcp)
- Tags: getting-started
- Published: 2026-07-19

---

**You can get support for DeusData codebase-memory-mcp through GitHub Issues for public bugs and questions, the [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md) policy for confidential vulnerabilities, or by emailing `support@deusdata.com` for commercial assistance.**

DeusData codebase-memory-mcp is an open-source Model Context Protocol (MCP) server that provides 15 tools for repository indexing and code navigation. When you encounter installation errors, unexpected behavior, or need integration guidance, the project offers structured support channels ranging from public issue trackers to private security reporting. This guide explains how to use each channel effectively based on the actual project structure and policies defined in the repository.

## Public Support via GitHub Issues

For general bugs, feature requests, and usage questions, the project uses the standard GitHub Issues workflow.

### Reporting Bugs and Feature Requests

Navigate to the repository's issue tracker at `DeusData/codebase-memory-mcp/issues` and select the appropriate template. When filing an issue, include:

- The exact version obtained by running `codebase-memory-mcp --version`
- Your operating system and environment details
- A minimal reproducible example or the specific CLI command that failed
- Relevant logs (set `CBM_LOG_LEVEL=debug` before running)

Maintainers monitor this channel for community discussion and resolution tracking.

## Security Support and Vulnerability Reporting

The project handles security issues separately from public bugs to enable coordinated disclosure. According to the [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md) file in the repository root, you should never disclose vulnerabilities in public issues.

### Reporting Security Vulnerabilities

For confidential vulnerability reports, use one of two methods:

1. Click the **"Report a security vulnerability"** button on the GitHub repository page
2. Email `security@deusdata.com` directly with the details

This triggers a private handling process that results in patched releases without premature public exposure. The policy explicitly forbids including API keys or credentials in any support communication.

## Documentation and Community Resources

Before opening a ticket, consult the self-service resources located in the repository's documentation tree.

The `docs/` folder contains detailed user guides covering installation, configuration, and documentation for all 15 MCP tools. For npm-specific installation issues, reference [`pkg/npm/README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/pkg/npm/README.md), which notes supported client surfaces and distribution-specific troubleshooting.

For peer-to-peer help and informal announcements, check the GitHub Discussions page linked from the repository.

## Enterprise and Commercial Support

Organizations requiring SLA-backed response times or custom integration assistance should use the dedicated commercial channel. Email `support@deusdata.com` directly for:

- Commercial licensing inquiries
- Custom integration support
- Personalized assistance with guaranteed response times

This channel bypasses the volunteer-driven public issue tracker for priority handling.

## Preparing Diagnostic Information

Effective support requests require specific diagnostic data. Gather this information before contacting any channel.

### Capturing Version and Environment Data

Always start by confirming your installation version:

```bash
codebase-memory-mcp --version

```

For runtime issues, enable debug logging and diagnostics:

```bash
export CBM_LOG_LEVEL=debug
export CBM_DIAGNOSTICS=1
codebase-memory-mcp cli index_repository '{"repo_path":"/abs/path/to/repo"}'

```

After reproducing the problem, locate the diagnostic `.ndjson` file (typically in `/tmp`) and attach it to your GitHub Issue. When sharing logs, redact any API keys or credentials as required by the security policy.

### Testing CLI Commands

Verify basic functionality using built-in help before reporting command failures:

```bash
codebase-memory-mcp --help

```

If a specific command fails, capture the exact error output:

```bash
codebase-memory-mcp cli trace_path '{"project":"my-proj","function_name":"nonexistent"}' || \
  echo "Command failed - capturing output for issue report"

```

## Summary

- Use **GitHub Issues** for public bugs, feature requests, and usage questions with full diagnostic logs attached
- Report **security vulnerabilities** privately via [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md) or `security@deusdata.com` to enable coordinated disclosure
- Consult the **`docs/`** folder and root [`README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/README.md) for self-service troubleshooting and MCP tool documentation
- Contact **`support@deusdata.com`** for enterprise-grade commercial support and SLA-backed assistance
- Always include **version output**, **reproducible steps**, and **diagnostic logs** (via `CBM_DIAGNOSTICS=1`) while redacting credentials

## Frequently Asked Questions

### How do I report a security vulnerability in DeusData codebase-memory-mcp?

Do not use public GitHub Issues. Instead, follow the process outlined in the repository's [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md) file by either using the GitHub **"Report a security vulnerability"** button or emailing `security@deusdata.com` directly. This ensures private handling and coordinated disclosure without exposing the vulnerability prematurely.

### What information should I include in a GitHub Issue for codebase-memory-mcp?

Include the output of `codebase-memory-mcp --version`, your operating system, a minimal reproducible example or the exact CLI command used, and relevant logs captured with `CBM_LOG_LEVEL=debug`. If the issue involves crashes or memory leaks, also attach the diagnostic `.ndjson` file generated after setting `CBM_DIAGNOSTICS=1`.

### Where can I find documentation for the 15 MCP tools provided by codebase-memory-mcp?

The `docs/` folder in the repository contains detailed guides covering all 15 MCP tools, configuration options, and language support tables. The root [`README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/README.md) provides a quick-start section and basic troubleshooting steps, while [`pkg/npm/README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/pkg/npm/README.md) covers npm-specific installation and client integration details.

### Is commercial support available for DeusData codebase-memory-mcp?

Yes. For SLA-backed response times, custom integrations, or licensing inquiries, email `support@deusdata.com`. This enterprise channel provides personalized assistance distinct from the community-driven GitHub Issues support.