MCP Bundler Service
by highlight-ing
A microservice that bundles code from GitHub repositories and prepares it for deployment. It supports direct return of bundled code or uploading to Google Cloud Storage.
Last updated: N/A
What is MCP Bundler Service?
The MCP Bundler Service is a microservice designed to bundle code from GitHub repositories, preparing it for deployment. It offers the flexibility to either return the bundled code directly or upload it to Google Cloud Storage.
How to use MCP Bundler Service?
To use the service, install dependencies with pnpm install and start the development server with pnpm run dev. Access the interactive API documentation at /docs. Use the /bundler or /v2/bundler endpoints with the required parameters (GitHub URL, optional commit hash, and optional mcpId) to bundle code. Configure GCP integration by setting the GCP_SERVICE_ACCOUNT_KEY environment variable.
Key features of MCP Bundler Service
GitHub Integration
Format Options (ESM/CJS)
Commit Pinning
GCP Storage Integration
Swagger Documentation
Comprehensive Error Handling
Use cases of MCP Bundler Service
Automated deployment pipelines
Serverless function packaging
Microservice bundling
Reproducible builds
FAQ from MCP Bundler Service
What formats are supported for bundling?
What formats are supported for bundling?
The service supports both ESM (mjs) and CommonJS (cjs) formats.
Is GCP integration required?
Is GCP integration required?
No, GCP integration is optional. You can disable it by setting the DISABLE_GCP_INTEGRATION environment variable to true.
How do I specify a specific commit to bundle?
How do I specify a specific commit to bundle?
Use the commit parameter in the API request with the desired commit hash.
What permissions are required for GCP integration?
What permissions are required for GCP integration?
The service account needs Storage Admin permissions for the target bucket.
What happens if the bundling process times out?
What happens if the bundling process times out?
The API will return a 504 timeout error. This typically occurs for large repositories or complex dependencies.