GitMir Vibe

Connect once.
Your agent does the rest.

GitMir as one MCP server in your editor. Add it to Claude Code, Cursor, VS Code or Codex, and your agent signs you in, connects the repository through GitHub, starts reading it and asks the product model from then on — no dashboard needed.

Install

One line.
The same address everywhere.

Your editor keeps the sign-in. There is no key to copy and nothing to paste into settings.

Claude Code
claude mcp add --transport http gitmir-vibe https://vibe.gitmir.com/mcp

THEN TYPE /MCP IN CLAUDE CODE AND SIGN IN

Codex
codex mcp add gitmir-vibe --url https://vibe.gitmir.com/mcp

THEN RUN CODEX MCP LOGIN GITMIR-VIBE

Any other MCP client
https://vibe.gitmir.com/mcp
How it works

From one line in the editor
to answers about your product.

You say yes twice — once to GitMir, once to GitHub. Everything else is your agent’s job.

01

Add the server

One line in Claude Code or Codex, one click in Cursor or VS Code. The address is the same everywhere.

02

Sign in once

Your editor opens GitMir in the browser. Sign in or create an account and press Allow — the editor keeps the sign-in, and there is no key to copy.

03

Choose the repository on GitHub

Your agent takes the repository of the folder you work in and gives you a link. GitHub asks which repositories GitMir can read, and reading starts when you come back.

04

Keep working in the editor

Your agent follows the reading until the model is ready, then asks GitMir what a change touches before it writes. New commits pushed? It reads them when you ask.

What your agent gets

Setup tools.
And the whole of Intelligence.

Four tools get the repository connected and read. The rest answer about the product itself.

vibe_status

Where the repository is — not connected, reading or ready — and the one next step

vibe_connect

Connects the repository of this folder, and sends you to GitHub only when GitMir cannot read it yet

vibe_refresh

Reads the commits pushed since the model was built, and says what that takes first

vibe_project_files

Files that keep the repository connected for everyone who opens it

gitmir_context and the rest

The questions GitMir Intelligence answers: what something is, what depends on it, what a change reaches

In GitMir

Stay in the editor.
Or open GitMir.

What your editor connects is in GitMir too — for the moments you want to see it, share it or turn it off.

Access

The editor gets its own sign-in, never a key. Disconnect it in GitMir and its access ends

GitHub

GitMir reads only the repositories you choose on GitHub, through its GitHub App

Links

A link your agent gives you works for 30 minutes, and only for your account

Projects

Shown in GitMir with everything else, marked via Vibe

Team

People you invite see the same projects, with the access you give them

Pricing

Free to start.
$29 per person when you need more.

Start with the credits of a new account and one repository. GitMir Vibe lifts the repository limit for the people on it and adds credits every month. Asking is free, and nothing is read without the number said first.

Free to start

3,000 credits with a new account, and one repository on the Free plan

$29 per person / month

That person connects repositories with no limit from the plan — from the editor and in GitMir

Credits for the team

Each person on GitMir Vibe adds 3,000 credits a month to your team’s shared credits

Who adds it

A team owner, in GitMir. When a limit is reached, your agent gives you the link — it never pays for you

Asking is free

Questions to the model use no credits, and your agent says what a reading takes before it starts

Start from your editor

Add one server.
Ask your agent to connect the repository.

That is the whole setup. Everything after it happens in your editor — and in GitMir, when you want to look.