Claude Code can read your code
Give it your product
Add GitMir Vibe to Claude Code as one MCP server. Claude Code signs you in, connects the repository through GitHub and starts reading it — and from then on it can ask what the product does and what a change reaches before it writes.
KEEP YOUR EXISTING WORKFLOW.
GitMir Vibe Connected directly through GitMir Vibe: one MCP server added to this client. The agent signs in, connects the repository through GitHub and asks the product model from inside the client.
What Claude Code already does well
Claude Code
Claude Code- Explores a repository and reads files in place
- Edits code, runs tools and runs commands
- Follows the instructions a project checks in
- Connects to external systems through MCP
Keep all of that. Add a reusable representation of the product it is working on.
One line in Claude Code
The same address for every coding tool. Claude Code keeps the sign-in; there is no key to copy and nothing to paste into settings.
claude mcp add --transport http gitmir-vibe https://vibe.gitmir.com/mcpTHEN TYPE /MCP IN CLAUDE CODE AND SIGN IN
https://vibe.gitmir.com/mcpWhat happens in Claude Code after that
- You ask“Connect this repository to GitMir.”
- vibe_statusWhere the repository is — not connected, reading or ready — and the one next step.
- vibe_connectConnects the repository of this folder. Only if GitMir cannot read it yet, it gives you a GitHub link that works for 30 minutes and only for your account.
- vibe_statusReading, after saying what the reading takes. Then ready.
- gitmir_contextBefore a change: what something is, what depends on it and what the change reaches.
- vibe_refreshReads the commits pushed since the model was built, when you ask.
What GitMir adds
- A compact model of what the product does and how it behaves
- The things the product works with — areas, records, actions, screens
- The customer paths a change would touch, and how states change along them
- Incoming requirements, and the development tasks they turn into
- Product-level change across analyzed commits
- One product context that people and agents read the same way
Spend less of the task reconstructing what already exists
Claude Code today
- Task
- Repository and the context tools you have
- Retrieve implementation evidence
- Reconstruct the behavior involved
- Reason
- Implement
Claude Code + GitMir Vibe
- Task
- gitmir_context: what the change reaches
- Compare current behavior with intended behavior
- Open the exact files
- Implement every place the change touches
Neither path is the wrong one. The second starts from a representation that already exists instead of rebuilding it for every task.
Ask a real product the question you would hand the agent
The Supabase model on this site is a real GitMir model of a real repository, built by the engine described here. Ask it what an AI agent must know before changing billing: the answer comes from the model, and the files it stands on come with it.
What must an AI agent know before changing billing?
An example, so you can see the answer without uploading anything of yours.
- Areas it reachesBilling & Subscription · Organization · Usage · Partner Onboarding · Project Settings
- RecordsSubscription · Invoice · PaymentMethod · CustomerProfile · Entitlement · ProjectAddon
- Actions · 33updateOrgSubscription · topUpCredits · redeemCode
- Endpoints · 27PUT /platform/organizations/{slug}/billing/subscription · POST .../billing/credits/top-up
- Screens · 33payment methods · organization billing and usage
- Customer pathsChange an organization's plan
One run, published in full
The one measurement GitMir has published is a 50-question run over a single repository, Supabase. It compared context systems answering the same questions, graded blind against repository evidence.
It did not measure Claude Code with GitMir against Claude Code without it. That comparison has not been run, and this page claims no result for it.
Give Claude the product history, not only the Git history
GitMir keeps product-level change across analyzed commits, so the agent can see when a behavior appeared, how it changed, and what changed around it before it decides what to do next.
What changes, and what does not
Is GitMir a replacement for Claude Code?
No. Claude Code stays the agent that reads, edits and runs your repository. GitMir changes what it can start from.
How does Claude Code connect to GitMir?
Through GitMir Vibe, one MCP server at https://vibe.gitmir.com/mcp. Run the line above, type /mcp in Claude Code and sign in — Claude Code keeps the sign-in, and there is no key to copy. Then ask it to connect the repository.
Add one server. Keep Claude Code
Run the line above, sign in once and ask Claude Code to connect the repository. It works from the product model from then on.
10,000 STARTING CREDITS INCLUDED · YOU SEE THE ESTIMATE BEFORE A BUILD STARTS · PROCESSING STOPS WITH YOUR BALANCE AND RESUMES AFTER A TOP-UP