Schema | codeglance-mcp

codeglance-mcp

Overview Schema Related Servers Score Discussions

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MAX_FILE_SIZE`	No	Max characters per file to analyze	5000
`GEMINI_API_KEY`	Yes	Your Google Gemini API key
`TIMEOUT_SECONDS`	No	API request timeout	120
`CACHE_TTL_SECONDS`	No	In-memory cache TTL	3600
`MAX_FILES_PER_ANALYSIS`	No	Max files to include in analysis	50
`MAX_CONCURRENT_REQUESTS`	No	Concurrent Gemini API calls	3

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

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
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`

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

Name	Description
`comprehensive_analysis`	Complete repository analysis workflow with all documentation types.
`quick_overview`	Fast repository overview for quick understanding.
`architecture_review`	Architecture-focused analysis for system design understanding.
`security_audit`	Security-focused repository review.

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Server Configuration
Instructions
Capabilities
Tools
Prompts
Resources

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/lucidopus/codeglance-mcp'

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