VibeGit MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VibeGit MCP Servershow me the latest conversation logs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VibeGit MCP Server
A Model Context Protocol (MCP) server for logging and analyzing AI assistant conversations.
Prerequisites
You need only two steps to get started:
Step 1: Installation
pip install vibegit-mcpStep 2: Configuration
Once installed, you can configure the MCP configuration file to enable the VibeGit MCP server. Assuming you are using VSCode, you can add a mcp.json file in the .vscode/ directory of your project with the following content:
{
"servers": {
"vibegit": {
"type": "stdio",
"command": "vibegit-mcp"
}
}
}Related MCP server: Memory MCP
Usage
After configuring the MCP server, you can start your AI Coding Agent in VSCode. The VibeGit MCP server will automatically log all conversation rounds to the .vibe/ directory in your project root.
Features
Log complete conversation rounds between users and AI assistants
Track file operations and tool usage
All the logs and data are stored in the .vibe/ directory under the project root. The directory structure is as follows:
.vibe/
├── rounds/
│ ├── 2023-03/
│ │ ├── round-1.json
│ │ ├── round-2.json
│ ├── 2023-04/
│ │ ├── round-3.json
│ │ ├── round-4.json
├── index.jsonl
├── sessions/
│ ├── session-1.json
│ ├── session-2.jsonEach round-*.json file contains detailed information about a single conversation round, including user inputs, AI responses, and any file operations and tool usage performed. The index.jsonl file provides a quick reference to all rounds, and the sessions/ directory contains session metadata. Each session contains the consecutive rounds of conversations.
Building and Publishing (For Maintainers)
This package uses modern Python packaging with pyproject.toml.
Prerequisites
Install build tools:
pip install build twineSet up PyPI credentials in ~/.pypirc:
[distutils]
index-servers =
pypi
testpypi
[pypi]
repository = https://upload.pypi.org/legacy/
username = __token__
password = # your PyPI API token (pypi-...)
[testpypi]
repository = https://test.pypi.org/legacy/
username = __token__
password = # your TestPyPI API token (pypi-...)Release Process
Update version in
pyproject.toml:version = "x.y.z" # Increment as neededClean previous builds:
rm -rf dist/ build/ *.egg-infoBuild the package:
python -m buildTest upload to TestPyPI (optional but recommended):
python -m twine upload --repository testpypi dist/*Test installation from TestPyPI:
pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ vibegit-mcp==x.y.zUpload to PyPI:
python -m twine upload dist/*
Notes
Always test with TestPyPI first before publishing to PyPI
Make sure to increment the version number for each release
The package uses
pyproject.tomlfor modern Python packaging standardsClean the
dist/directory before building new releases
License
MIT License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to automatically log and manage conversation history with developers in structured markdown format. Provides powerful search and context suggestions to help AI understand project history and maintain continuity across sessions.41
- AlicenseAqualityBmaintenanceProvides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.8MIT
- Alicense-qualityBmaintenanceRecord debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.81MIT
- Flicense-qualityCmaintenancePermanent, timestamped audit log for every AI conversation, stored locally in SQLite, owned by you.
Related MCP Connectors
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
Persistent memory for AI agents — verbatim conversations, searchable by meaning.
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gixia-org/VibeGit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server