Skip to main content
Glama

Skillroute MCP

Skillroute MCP is a Model Context Protocol (MCP) server that provides AI agents with access to a structured library of engineering skills, best practices, and playbooks.

Available Skills

This MCP server currently provides the following skills and best practice guidelines:

  • agent-development: Guidelines for developing AI agents.

  • agents-sdk: Documentation and rules for using the agents SDK.

  • ai-elements: Best practices for AI UI elements.

  • building-components: Standards for building reusable components.

  • code-reviewer: Guidelines and instructions for automated code review.

  • command-development: Rules for developing CLI commands and tools.

  • frontend-design: General frontend design rules and principles.

  • hook-development: Best practices for developing React hooks.

  • next-best-practices: Comprehensive Next.js best practices and app router guidelines.

  • next-cache-components: Guidelines for caching in Next.js.

  • skill-development: Instructions on how to write and structure skills.

  • vercel-react-best-practices: Vercel's recommended React best practices.

  • web-design-guidelines: General web design and aesthetic guidelines.

  • web-perf: Web performance optimization rules.

Related MCP server: Engineering Standards MCP Server

Setup Instructions

1. Clone the Repository and Build

First, clone the project to your local machine:

git clone https://github.com/vaibhavgupta5/SkillRoute-MCP.git
cd SkillRoute-MCP

Install dependencies and compile the TypeScript code:

npm install
npm run build

This will generate the compiled JavaScript in the dist/ directory.

2. Get the Absolute Path

For the MCP configuration, you will need the absolute path to the compiled index.js file. For example, if you cloned the repository into C:\Projects\skillroutemcp, your path will be C:/Projects/skillroutemcp/dist/index.js (make sure to use forward slashes or escaped backslashes in JSON).

In the configurations below, replace [ABSOLUTE_PATH_TO_DIST_INDEX_JS] with your actual absolute path.

3. Configure in Claude Desktop

To use this MCP server in Claude Desktop, add the following to your claude_desktop_config.json file (typically located at %APPDATA%\\Claude\\claude_desktop_config.json on Windows or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "skillroute": {
      "command": "node",
      "args": ["[ABSOLUTE_PATH_TO_DIST_INDEX_JS]"]
    }
  }
}

Restart Claude Desktop after updating the configuration.

4. Configure in VSCode (with extensions like Roo Code / Cline)

To use this MCP server in VS Code with extensions that support MCP, you can add it to their respective MCP settings configuration file:

{
  "mcpServers": {
    "skillroute": {
      "command": "node",
      "args": ["[ABSOLUTE_PATH_TO_DIST_INDEX_JS]"]
    }
  }
}

5. Configure in Antigravity

To use this MCP server in Antigravity, you need to register it in your Antigravity MCP configuration.

Open your Antigravity Settings and edit the mcp.json file (or navigate to the MCP Server configuration section). Add the server using the following structure:

{
  "mcpServers": {
    "skillroute": {
      "command": "node",
      "args": ["[ABSOLUTE_PATH_TO_DIST_INDEX_JS]"]
    }
  }
}

Alternatively, if adding via the Antigravity settings UI:

  • Command: node

  • Arguments: ["[ABSOLUTE_PATH_TO_DIST_INDEX_JS]"]

Reload the Antigravity workspace for the changes to take effect.

Available Tools

2 tools
get_framework_skillB

Fetches specific engineering guidelines, rules, and best practices for a given framework/technology.

Inputs: technology (required), path.

list_skillsB

Lists all available engineering skills and playbooks.

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: listing all available skills versus fetching details for a specific framework. There is no overlap or ambiguity an agent could encounter.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (list_skills, get_framework_skill) using snake_case. The naming clearly indicates the action and target resource.

    Tool Count3/5

    With only 2 tools, the set feels minimal but not inappropriate for a narrow domain like reference documentation. It is on the low end but earns its place.

    Completeness4/5

    The surface covers the basic operations for a skills reference: listing all available and retrieving one by framework. A gap might be the absence of search or filtering, but for a simple lookup tool it is largely complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers