Skip to main content
Glama
Sign In
MCP Toolkit Pro

MCP Toolkit Pro

by DzAchref
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

MCP Toolkit Pro

Premium MCP Server for AI Agents — GitHub integration, code analysis, and project management.

What is this?

MCP Toolkit Pro is a Model Context Protocol (MCP) server that gives AI agents powerful tools to interact with GitHub, analyze code, and manage projects. It's the fastest way to add GitHub capabilities to any AI agent.

Related MCP server: GitHub MCP Server

Features

GitHub Integration

  • Search Repositories — Find repos by keyword, language, or topic

  • Read Files — Access any file in any public GitHub repository

  • List Issues — Browse issues with filtering by state and labels

  • List Pull Requests — View PRs with author and status info

  • Read READMEs — Get repository documentation instantly

Code Analysis

  • Code Quality Analysis — Detect issues, complexity, and best practices

  • Language Detection — Auto-detect programming languages

  • Issue Detection — Find TODOs, FIXMEs, console.logs, and more

Project Management

  • Task List Generator — Create structured task lists from descriptions

  • Priority Sorting — Organize tasks by priority and status

Quick Start

# Install
npm install mcp-toolkit-pro

# Or clone and build
git clone https://github.com/yourusername/mcp-toolkit-pro.git
cd mcp-toolkit-pro
npm install
npm run build

Configuration

Add to your MCP client config:

{
  "mcpServers": {
    "mcp-toolkit-pro": {
      "command": "node",
      "args": ["path/to/mcp-toolkit-pro/dist/index.js"]
    }
  }
}

Pro Features (Coming Soon)

  • GitHub Write Operations — Create issues, PRs, and manage workflows

  • Batch Operations — Process multiple items at once

  • Custom Templates — Create and save custom tool configurations

  • Priority Support — Direct line to the developer

License

MIT

Available Tools

7 tools
analyze_codeA

Analyze code for quality, complexity, and potential issues. Returns a detailed report.

Inputs: code (required), language.

create_task_listB

Create a structured task list from a description. Returns organized tasks with priorities.

Inputs: description (required), format.

github_list_issuesB

List issues in a GitHub repository. Returns issue number, title, state, labels, and URL.

Inputs: repo (required), owner (required), limit, state, +1 more.

github_list_prsA

List pull requests in a GitHub repository. Returns PR number, title, state, author, and URL.

Inputs: repo (required), owner (required), limit, state.

github_read_fileA

Read the contents of a file from a GitHub repository. Returns the file content as text.

Inputs: path (required), repo (required), owner (required), branch.

github_readmeA

Read the README file of a GitHub repository. Returns the markdown content.

Inputs: repo (required), owner (required).

github_search_reposA

Search GitHub repositories by keyword, language, or topic. Returns repo name, description, stars, and URL.

Inputs: query (required), sort, limit.

Tool Schema Changelog

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

Loading tool schema changelog…

    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.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: code analysis, task list creation, and the various GitHub read/search operations. The only potential confusion is between github_read_file and github_readme, since readme is a special case of file reading, but the descriptions make the distinction clear enough.

    Naming Consistency3/5

    GitHub tools consistently use a 'github_' prefix followed by a verb_noun pattern (e.g., github_search_repos, github_list_issues), but the two non-GitHub tools (analyze_code, create_task_list) lack any prefix. This mixed convention — some tools namespaced, others not — reduces naming consistency.

    Tool Count4/5

    With 7 tools, the set falls comfortably within the ideal 3-15 range. The count feels reasonable for a server that covers both general utility functions and GitHub-specific operations, though it could be seen as slightly sparse for a 'Toolkit Pro' label.

    Completeness2/5

    The GitHub toolset is read/search-only, lacking any create, update, or delete operations for issues or PRs. The task list tool only supports creation, with no way to update or delete tasks, creating dead-ends in workflows. For a general-purpose toolkit, the absence of write operations and task lifecycle management represents significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers