GlubGlub

Created By
maxyharra year ago
A repository demonstrating GitHub MCP server configuration in VS Code
Overview

What is GlubGlub?

GlubGlub is a repository that demonstrates how to configure and use the GitHub Model Context Protocol (MCP) server within Visual Studio Code (VS Code) for managing GitHub repositories.

How to use GlubGlub?

To use GlubGlub, clone the repository and follow the setup instructions to configure the GitHub MCP server in VS Code. You can then create and manage GitHub repositories using natural language commands through GitHub Copilot.

Key features of GlubGlub?

  • Demonstrates GitHub MCP server configuration in VS Code.
  • Allows repository creation using natural language commands.
  • Supports both Docker-based and Copilot advanced settings for setup.

Use cases of GlubGlub?

  1. Creating new GitHub repositories directly from VS Code.
  2. Managing repository settings and configurations using natural language.
  3. Streamlining GitHub operations without leaving the development environment.

FAQ from GlubGlub?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized communication protocol that enables large language models to interact with external services, facilitating operations like repository management.

  • Is GlubGlub free to use?

Yes! GlubGlub is open-source and free to use for everyone.

  • Can I use GlubGlub without Docker?

Yes, you can configure MCP using GitHub Copilot's advanced settings without Docker.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
maxyharr
Star
0
Language
-
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)

a day ago