Skip to main content
Glama
lucidopus

codeglance-mcp

by lucidopus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_FILE_SIZENoMax characters per file to analyze5000
GEMINI_API_KEYYesYour Google Gemini API key
TIMEOUT_SECONDSNoAPI request timeout120
CACHE_TTL_SECONDSNoIn-memory cache TTL3600
MAX_FILES_PER_ANALYSISNoMax files to include in analysis50
MAX_CONCURRENT_REQUESTSNoConcurrent Gemini API calls3

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_repositoryA

Execute comprehensive code analysis workflow on a GitHub repository.

Clones the repository, analyzes it with Gemini AI, and generates 6 documentation
files covering overview, structure, file insights, architecture, quick-start, and
a master analysis.

Args:
    repo_url: GitHub repository URL to analyze
    working_directory: Directory where to create analysis folder (default: current directory)
get_repository_infoA

Get information about a repository and whether it's already cloned locally.

Args:
    repo_url: GitHub repository URL
    working_directory: Directory where analysis folder should be located
list_generated_guidesA

List all generated guide files in the codeglance-analysis/guide directory.

Args:
    working_directory: Directory where codeglance-analysis folder should be located

Prompts

Interactive templates invoked by user choice

NameDescription
comprehensive_analysisComplete repository analysis workflow with all documentation types.
quick_overviewFast repository overview for quick understanding.
architecture_reviewArchitecture-focused analysis for system design understanding.
security_auditSecurity-focused repository review.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: analyzing a repository, checking its status, and listing output guides. No overlap in functionality.

Naming Consistency5/5

All tools use a consistent verb_noun snake_case pattern (analyze_repository, get_repository_info, list_generated_guides) making predictions easy.

Tool Count4/5

Three tools are slightly on the lower end for a code analysis server, but they cover the essential workflow without being excessive. The count is reasonable.

Completeness3/5

The tools cover the core analysis and listing workflow, but lack retrieval of individual guide content, deletion, or configuration options, which are notable gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources