glam-mcp

Retrieve current session context including git state, preferences, and recent operations. Use this when you need to understand the current working context or check user preferences.

Set a user preference in the current session. Use this to store user-specific settings like preferred commit message format, auto-commit behavior, or UI preferences.

Retrieve recent git operations from the session history. Use this to understand what actions have been performed recently or to check operation history.

Clear all user preferences from the current session. Use this to reset preferences to defaults.

Add a new operation to the session history. This is typically called automatically by other tools but can be used manually for custom operations.

Generate comprehensive project documentation including README, API reference, examples, and more. Use this to create or update project documentation.

Generate detailed documentation for a specific tool. Use this to create or update individual tool documentation.

Extract and update documentation from source code, including JSDoc comments and type definitions. Use this to keep docs in sync with code.

Generate interactive HTML documentation with search, playground, and tutorials. Use this to create user-friendly documentation.

Check documentation coverage and identify missing documentation. Use this to ensure all tools and features are documented.

Analyze the risk level of a Git operation before execution. Use this to assess potential dangers of operations like force push, large merges, or operations on protected branches.

Check for potential merge conflicts and branch divergence. Use this before merge or rebase operations to identify conflicts early.

Validate that all preconditions are met before executing a Git operation. Use this to ensure operations will succeed and are safe to perform.

Assess the criticality of files being modified. Use this to identify operations affecting important system files, configurations, or dependencies.

Check recent team activity including commits, branches, and pull requests. Use this to understand what your team is working on and identify potential conflicts or collaboration opportunities.

Find work related to specific files or the current branch. Use this to discover related pull requests, commits, and potential conflicts before starting work.

Suggest appropriate code reviewers based on file expertise and workload. Use this when creating a pull request to find the best reviewers.

Get insights about team collaboration patterns, knowledge clusters, and communication networks. Use this to understand team dynamics and improve collaboration.