MCP Bundler Service

Created By
highlight-inga year ago
A microservice for bundling MCP servers from GitHub repositories and preparing it for deployment.
Overview

what is MCP Bundler?

MCP Bundler is a microservice designed to bundle code from GitHub repositories and prepare it for deployment, supporting both direct returns of bundled code and uploads to Google Cloud Storage.

how to use MCP Bundler?

To use MCP Bundler, install the dependencies using pnpm install, start the development server with pnpm run dev, and access the API documentation at http://localhost:8080/docs.

key features of MCP Bundler?

  • GitHub Integration for bundling code from public repositories
  • Output format options: ESM (mjs) or CommonJS (cjs)
  • Commit pinning for reproducible builds
  • Optional upload of bundled code to Google Cloud Storage
  • Interactive API documentation with Swagger UI
  • Comprehensive error handling with appropriate status codes

use cases of MCP Bundler?

  1. Bundling code for deployment from GitHub repositories.
  2. Integrating with Google Cloud Storage for further deployment processes.
  3. Facilitating CI/CD pipelines by providing bundled code directly.

FAQ from MCP Bundler?

  • Can MCP Bundler handle private repositories?

No, MCP Bundler currently only supports public GitHub repositories.

  • Is there a timeout for bundling large repositories?

Yes, repository bundling has a 5-minute timeout limit.

  • How do I disable GCP uploads?

Set the environment variable DISABLE_GCP_INTEGRATION=true to disable GCP uploads.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
highlight-ing
Star
1
Language
TypeScript
License
MIT 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
Crevio

2 days ago