Skip to main content
Glama
kongyo2

GitHub URL MCP Server

by kongyo2

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
github/build_urlA

Converts GitHub owner and repository name into a properly formatted GitHub URL with validation

github/parse_urlA

Parses a GitHub URL to extract owner, repository name, and additional path information with validation

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Server Information

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct and complementary purposes: one builds URLs from components, the other parses URLs into components. There is no overlap in functionality, and an agent would easily differentiate between them based on their input/output needs.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (build_url, parse_url) under the same 'github/' namespace. The naming is predictable and aligned, making it easy for agents to understand their roles without confusion.

Tool Count3/5

With only 2 tools, the server feels thin for a GitHub-related purpose, as typical GitHub MCP servers offer more comprehensive operations (e.g., managing repos, issues, PRs). However, for the narrow scope of URL handling, it is minimally functional but limited in broader utility.

Completeness4/5

For the specific domain of GitHub URL manipulation, the tools provide complete coverage: building and parsing URLs. A minor gap might be the lack of tools for validating URLs without parsing or building, but the core operations are well-covered for this focused task.

Maintenance

ActivityInactive
ResponsivenessNo issues