GitHub Models Helper MCP Server

Created By
michaelwybranieca year ago
Overview

what is GitHub Models Helper MCP Server?

GitHub Models Helper MCP Server is a tool designed to help users interact with and compare various language models available on GitHub and AzureML, including models from OpenAI, Microsoft, Meta, and Mistral.

how to use GitHub Models Helper MCP Server?

To use the server, install the necessary dependencies, set up your environment variables with a GitHub token, build the project, and run the server in development mode. You can also integrate it with Claude Desktop by adding it to the configuration file.

key features of GitHub Models Helper MCP Server?

  • Lists available language models with metadata
  • Compares responses from different models for the same prompt
  • Filters and sorts models by various criteria
  • Comprehensive error handling and fallbacks
  • Visualizes model comparisons

use cases of GitHub Models Helper MCP Server?

  1. Comparing responses from different AI models to the same prompt.
  2. Analyzing the performance of various language models.
  3. Visualizing the differences in model outputs for better understanding.

FAQ from GitHub Models Helper MCP Server?

  • What models can I compare?

You can compare any models available in the GitHub Models and AzureML repositories.

  • Do I need a GitHub token?

Yes, you need a personal access token to access the models.

  • Can I visualize the model comparisons?

Yes, the server provides functionality to visualize the responses from different models.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
michaelwybraniec
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago