[Mistral Vibe CLI] How I got it working with Mistral's Vibe CLI

[akashskypatel]

What problem does this solve?

This MCP does not currently work with Mistral's Vibe CLI. Add MCP config to default installation process so that this MCP works with Mistral Vibe CLI.

I got it working however by doing the following:

Proposed solution

Add to .vibe/config.toml

skill_paths = [
    "vibe/skills",
]
enabled_skills = [
    "codebase-memory-mcp",
]
[[mcp_servers]]
name = "codebase-memory-mcp"
transport = "stdio"
command = "path/to/codebase-memory-mcp"
args = []

Add skill to ./vibe/skills/codebase-memory-mcp

---
name: codebase-memory-mcp
description: Codebase Knowledge Graph skill for codebase-memory-mcp.
license: MIT
user-invocable: true
---

# Codebase Knowledge Graph skill (codebase-memory-mcp)

This project uses codebase-memory-mcp to maintain a knowledge graph of the codebase.
ALWAYS prefer MCP graph tools over grep/glob/file-search for code discovery.

## Install location

The codebase-memory-mcp tool is installed at: `C:\Users\Akash\.local\bin\codebase-memory-mcp.exe`

## Available tools
- `index_repository` — Index a repository into the graph. Auto-sync keeps it fresh after that.
- `list_projects` — List all indexed projects with node/edge counts.
- `delete_project` — Remove a project and all its graph data.
- `index_status` — Check indexing status of a project.
- `search_graph` — Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.
- `trace_path` — BFS traversal — who calls a function and what it calls (alias: trace_call_path). Depth 1-5.
- `detect_changes` — Map git diff to affected symbols + blast radius with risk classification.
- `query_graph` — Execute Cypher-like graph queries (read-only).
- `get_graph_schema` — Node/edge counts, relationship patterns, property definitions per label. Run this first.
- `get_code_snippet` — Read source code for a function by qualified name.
- `get_architecture` — Codebase overview: languages, packages, routes, hotspots, clusters, ADR.
- `search_code` — Grep-like text search within indexed project files.
- `manage_adr` — CRUD for Architecture Decision Records.
- `ingest_traces` — Ingest runtime traces to validate HTTP_CALLS edges.

## Usage priority
1. `search_graph` — find functions, classes, routes, variables by pattern
2. `trace_path` — trace who calls a function or what it calls
3. `get_code_snippet` — read specific function/class source code
4. `query_graph` — run Cypher queries for complex patterns
5. `get_architecture` — high-level project summary

## When to fall back to grep/glob
- Searching for string literals, error messages, config values
- Searching non-code files (Dockerfiles, shell scripts, configs)
- When MCP tools return insufficient results

## Examples
- Index repository: `index_repository(path="/path/to/repo")`
- Find a handler: `search_graph(name_pattern=".*OrderHandler.*")`
- Who calls it: `trace_path(function_name="OrderHandler", direction="inbound")`
- Read source: `get_code_snippet(qualified_name="pkg/orders.OrderHandler")`

## CLI Mode
For CLI usage, use the `codebase-memory-mcp` command directly:

codebase-memory-mcp cli index_repository '{"repo_path": "/path/to/repo"}'
codebase-memory-mcp cli search_graph '{"name_pattern": ".*Handler.*", "label": "Function"}'
codebase-memory-mcp cli trace_path '{"function_name": "Search", "direction": "both"}'
codebase-memory-mcp cli query_graph '{"query": "MATCH (f:Function) RETURN f.name LIMIT 5"}'
codebase-memory-mcp cli list_projects
codebase-memory-mcp cli --raw search_graph '{"label": "Function"}' | jq '.results[].name'

Alternatives considered

No response

Confirmations

• I searched existing issues and this is not a duplicate.