Skip to main content
Glama
MUSE-CODE-SPACE

Vibe Coding Documentation MCP (MUSE)

muse_git

Check git repository status, view commit history and diffs, manage branches, capture full context snapshots, and extract design decisions from commit messages. Links git context to coding sessions for documentation.

Instructions

Git integration for vibe coding sessions. Get repository status, commit history, diffs, branch info. Capture git snapshots for sessions and extract design decisions from commit messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction: status (repo state), log (commit history), diff (changes), branch (branch info), snapshot (full context), extractDecisions (from commits), linkToSession (attach to session)
repoPathNoPath to git repository. Defaults to current working directory.
includeUntrackedNoInclude untracked files in status (default: true)
limitNoMax commits to return for log/extractDecisions (default: 20, max: 500)
authorNoFilter commits by author name or email
sinceNoFilter commits after date (e.g., "2024-01-01", "1 week ago")
untilNoFilter commits before date
grepNoSearch commit messages for keyword
onelineNoCompact log format (default: false)
diffTypeNoDiff type: staged, unstaged, or all changes (default: all)
fromRefNoSource commit/branch/tag for diff
toRefNoTarget commit/branch/tag for diff
pathNoFilter by file or directory path
contextLinesNoLines of context around changes (default: 3)
statNoInclude stat summary in diff (default: true)
includeRemoteNoInclude remote branches (default: true)
verboseNoInclude last commit info per branch (default: false)
includeDiffNoInclude current diff in snapshot (default: true)
includeLogNoInclude recent commits in snapshot (default: true)
logLimitNoCommits to include in snapshot (default: 10)
includeStashNoInclude stash list in snapshot (default: false)
patternsNoCustom regex patterns for detecting design decisions
languageNoLanguage for analysis (default: auto-detect)
sessionIdNoSession ID to link git context to (required for linkToSession)
snapshotTypeNoDetail level when linking to session (default: minimal)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention whether actions are read-only or destructive, any side effects (e.g., linking to a session may modify data), authentication requirements, or rate limits. This is a significant gap for a multi-action tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences) and front-loaded with the tool's purpose. It lists key capabilities without unnecessary detail, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a high parameter count (25) and multiple actions, the description is too brief to provide complete guidance. It does not explain how actions relate to parameters, what each action returns, or how to combine parameters effectively. With no output schema or annotations, the description should offer more context to compensate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 25 parameters adequately. The description adds overall context (e.g., listing actions) but does not enhance understanding of individual parameters beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a 'Git integration for vibe coding sessions' and lists specific capabilities: getting repository status, commit history, diffs, branch info, capturing snapshots, and extracting design decisions. This distinguishes it from sibling tools that focus on analysis, tagging, or session management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for Git-related tasks within coding sessions but does not explicitly guide when to use this tool versus alternatives like muse_summarize_design_decisions. There is no mention of prerequisites, when not to use it, or comparison with siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/MUSE-CODE-SPACE/vibe-coding-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server