Skip to main content
Glama
enesjakozh
kazuph

@kazuph/mcp-github-pera1

by kazuph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor MCP de GitHub para Pera1

Un servidor de Protocolo de Contexto de Modelo que conecta el código de GitHub con Claude.ai. Este servidor utiliza el servicio Pera1 para extraer código de los repositorios de GitHub y proporcionar un mejor contexto a Claude.

Configuración

Agregue lo siguiente a su archivo de configuración MCP ( ~/Library/Application Support/Claude/claude_desktop_config.json ):

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@kazuph/mcp-github-pera1"]
    }
  }
}

Ahora puedes preguntarle a Claude sobre los repositorios de código de GitHub.

Parámetros

  • url : URL del repositorio de GitHub (obligatorio)

  • dir : Filtrar archivos por rutas de directorio (separadas por comas)

  • ext : Filtrar archivos por extensiones (separadas por comas)

  • mode : modo de visualización (por ejemplo, tree muestra solo la estructura del directorio y los archivos README)

  • branch : especifica la rama desde la que se obtendrán los datos

  • file : especifique un solo archivo para recuperar

Ejemplos de uso

Puedes hacerle preguntas a Claude como:

Tell me about the implementation of GitHub repository https://github.com/username/repository

Para directorios específicos:

Explain the components in https://github.com/username/repository?dir=src/components

Para un archivo específico:

Show me the Button component from https://github.com/username/repository?file=src/components/Button.tsx

Solo para la estructura de directorio con archivos README:

Show me the structure of https://github.com/username/repository?mode=tree

Para una rama específica:

Analyze the develop branch of https://github.com/username/repository?branch=develop

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Autor

kazuph ( https://x.com/kazuph )

Available Tools

1 tool
github_get_codeA

Retrieves code from a GitHub repository URL and combines it into a single file. The URL must start with "https://".

Query Parameters:

  • dir: Filter files by directory paths (comma-separated) Example: ?dir=src/components,tests/unit

  • ext: Filter files by extensions (comma-separated) Example: ?ext=ts,tsx,js

  • mode: Display mode Example: ?mode=tree (Shows directory structure and README files only)

  • branch: Specify the branch to fetch from (optional) Example: ?branch=feature/new-feature

  • file: Specify a single file to retrieve (optional) Example: ?file=src/components/Button.tsx

Examples:

  1. For GitHub tree URLs with branch: https://github.com/kazuph/pera1/tree/feature/great-branch This URL will be automatically parsed to extract the branch information.

  2. For specific directory in a branch: url: https://github.com/modelcontextprotocol/servers dir: src/fetch branch: develop

  3. For a single file: url: https://github.com/username/repository file: src/components/Button.tsx

  4. For directory structure with README files only: url: https://github.com/username/repository mode: tree

The tool will correctly parse the repository structure and fetch the files from the specified branch.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
dirNo
extNo
modeNo
branchNo
fileNo

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses that the tool retrieves and combines code, parses repository structure, and auto-extracts branch from tree URLs. Given no annotations, it covers key behaviors but does not mention rate limits or error handling.

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

Conciseness4/5

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

The description is well-structured with sections for parameters and examples, and the first sentence clearly states the purpose. It is somewhat lengthy but all content is informative.

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

Completeness5/5

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

Given no annotations or output schema, the description covers all behaviors: parameter usage, URL parsing, combining files, and example scenarios. It is complete for a read-only code retrieval tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description thoroughly explains each parameter with formats (e.g., comma-separated for dir/ext) and examples. This fully compensates for the schema's lack of descriptions.

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 the tool's verb ('retrieves code') and resource ('GitHub repository URL'), and specifies that it combines content into a single file. There are no sibling tools, so no differentiation needed.

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

Usage Guidelines4/5

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

The description provides detailed query parameters and multiple examples covering different use cases (tree URLs, directories, single file, tree mode). However, it does not explicitly state when to use this tool versus alternatives, though no siblings exist.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedgithub_get_code
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no risk of confusion between tools.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern (github_get_code).

Tool Count2/5

A single tool for code retrieval is very minimal; users might expect additional GitHub operations, making the server feel incomplete.

Completeness4/5

For the stated purpose of retrieving code from a GitHub repository, the tool covers key needs with filtering by directory, extension, branch, and single file, as well as a tree mode. Minor gap: no support for private repos or authentication details in the description.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • GitHub MCP Server

    wulfitect
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    A Model Context Protocol server that provides comprehensive GitHub integration for Claude Desktop, allowing users to manage repositories, issues, and pull requests. It supports file operations, branch management, and repository searches through natural language commands.
    346 npm
    -

Appeared in Searches