Skip to main content
Glama
vamsi-desu

Git RAG MCP Server

by vamsi-desu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENYesYour GitHub token used by the GitHub server for authenticated GitHub API requests.

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
create_test_caseC

Create a standardized MCP test case.

Args: name: Short name of the test.

tool_name:
    MCP tool being tested.

input_data:
    Input that should be passed to the tool.

expected_result:
    Expected behavior/result.
validate_github_resultB

Perform basic validation of a GitHub MCP tool result.

Args: operation: GitHub operation being tested.

result:
    Result returned by the GitHub MCP server.
validate_rag_resultC

Perform basic validation of a RAG MCP tool result.

Args: operation: RAG operation being tested.

result:
    Result returned by the RAG MCP server.

Prompts

Interactive templates invoked by user choice

NameDescription
generate_mcp_test_plan Generate a reusable prompt for testing a component of the MCP project.

Resources

Contextual data attached and managed by the client

NameDescription
mcp_test_checklist Reusable QA checklist for the GitHub and RAG MCP servers.
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

B3.2/5.0

Scored across 3 tools

Disambiguation4/5

Create_test_case is distinct in purpose from the two validate_* tools. The two validators are parallel and could be momentarily confused, but their names clearly indicate the GitHub vs RAG domain, so boundaries are mostly clear.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: create_test_case, validate_github_result, validate_rag_result. The convention is predictable and uniform.

Tool Count4/5

Three tools is a small but reasonable set for a focused testing utility. It is slightly on the low side, but each tool has a clear role and the count does not feel excessive or arbitrarily inflated.

Completeness2/5

The domain is a testing harness for MCP tools, yet there is no tool to run a test case, list/retrieve existing test cases, or update/delete them. Validation covers only GitHub and RAG results, leaving other potential MCP results unsupported, which creates significant gaps for realistic workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources