Mcp Vercel Github Integration

Name: Mcp Vercel Github Integration
Author: mixuechu

Local

github.com/mixuechuVersion Control0Updated 81w ago

Repository

About Mcp Vercel Github Integration

GitHub-Vercel MCP Server automates creating GitHub repositories and deploying Vercel templates. It is intended for users provisioning template-based projects, with namespace detection and support for Vercel team operations.

Key features

01Create GitHub repositories
02Deploy Vercel templates
03Detect GitHub namespace from token
04Support Vercel team operations
05Return deployment and project details

Use cases

01Create a repository from a template
02Deploy a template project to Vercel
03Provision projects using Vercel teams

MCP support

It exposes GitHub repository creation and Vercel template deployment as an MCP service for MCP clients.

#mcp #vercel #github-integration

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

{
  "mcpServers": {
    "vercel-github-integration": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-vercel-github-integration"
      ],
      "env": {
        "VERCEL_API_KEY": "<VERCEL_API_KEY>",
        "GITHUB_API_KEY": "<GITHUB_API_KEY>",
        "GITHUB_NAMESPACE": "<GITHUB_NAMESPACE>"
      }
    }
  }
}

Run commandnpx -y mcp-vercel-github-integration

Environment variables to set

VERCEL_API_KEYSecret

GITHUB_API_KEYSecret

GITHUB_NAMESPACE

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

npmmcp-vercel-github-integrationstdio

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

GitHub-Vercel MCP Server

Automated GitHub repository creation and Vercel template deployment as an MCP service.

Features

🚀 Auto-detection of GitHub namespace from token
🤖 Team-aware Vercel operations
⚡ Zero-config for most use cases
🔒 Secure credential handling

Local Installation

npm install -g @yourpackage/mcp-server-github

MCP Configuration

Add to your mcp.config.json:

{
  "mcpServers": {
        "vercel-github": {
          "command": "npx",
          "args": [
            "mcp-vercel-github-integration",
            "-v",
            "<Your Vercel API Key>",
            "-g",
            "<Your Git API Key>"
          ]
    }
  }
}

Required Permissions

GitHub Token

repo:       # Full repository control
user:       # Read user profile
read:org    # If using organizations

Vercel Token

projects:read and projects:write
teams:read (if using teams)

Usage

Basic Deployment

mcp execute github --REPO_NAME "my-app" --TEMPLATE_SOURCE "https://github.com/vercel/vercel/tree/main/examples/nextjs"

All Parameters

Parameter	Default	Description
`VERCEL_API_KEY`	-	(Required) Vercel API key
`GITHUB_TOKEN`	-	(Required) GitHub personal access token
`REPO_NAME`	"new-repo"	Repository name
`TEMPLATE_SOURCE`	Vercel Next.js	Template Git URL
`IS_PRIVATE`	true	Make repository private

API Response

Successful execution returns:

{
  "status": "success",
  "data": {
    "githubRepo": "https://github.com/yourname/repo",
    "vercelProject": "https://repo.vercel.app",
    "projectId": "prj_abc123"
  }
}

Error Handling

Common error responses include:

{
  "status": "error",
  "error": {
    "code": "GITHUB_AUTH_FAILED",
    "message": "Invalid GitHub token"
  }
}

Development

Clone the repository
Install dependencies:
```
npm install
```
Set up environment:
```
cp .env.example .env
```
Run tests:
```
npm test
```

Deployment

Package and publish to npm:

npm publish --access public

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.