MCP.so
ログイン
M

MCP Vercel Github Integration

@mixuechu

基本情報

カテゴリ

バージョン管理

トランスポート

stdio

作者

mixuechu

投稿者

Xuechuan Mi

MCP Vercel Github Integration について

概要はまだありません

MCP Vercel Github Integration の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

MCP Vercel Github Integration のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Mcp Vercel Github Integration?

Mcp Vercel Github Integration is an MCP (Model Control Protocol) server that automates creating GitHub repositories, pushing template code, and configuring Vercel deployments. It is designed for developers who want to quickly scaffold and deploy projects using Vercel and GitHub.

How to use Mcp Vercel Github Integration?

Install the package globally via npm (npm install -g mcp-vercel-github-integration), then configure it in your MCP configuration file (usually ~/.cursor/mcp.json) by providing VERCEL_API_KEY, GITHUB_API_KEY, and GITHUB_NAMESPACE environment variables. Run the tool from the command line with flags like --VERCEL_API_KEY, --repoName, and --templateSource to start a workflow that creates a GitHub repo, pushes a template, and sets up a Vercel project.

Key features of Mcp Vercel Github Integration

  • Automates GitHub repository creation
  • Pushes template code automatically
  • Configures Vercel project integration
  • Supports team and personal GitHub accounts
  • Allows custom template source URLs

Use cases of Mcp Vercel Github Integration

  • Quickly bootstrap a new Next.js project on Vercel from a template
  • Automate setting up deployment for a team’s GitHub organization
  • Create a standard project structure with Vercel integration in one command
  • Integrate into a CI/CD pipeline for one-click repo-and-deploy workflows

よくある質問

1

What runtime or system requirements are needed?

Node.js and npm or yarn are required. You also need a Vercel account and a GitHub account.

2

How are API keys used?

The tool requires `VERCEL_API_KEY` and `GITHUB_API_KEY` environment variables to authenticate with Vercel and GitHub APIs. It does not store keys elsewhere.

3

Where does the tool run?

It runs as a local MCP server (using `npx`) on the user’s machine, typically configured in a Cursor or other MCP host configuration file.

4

Does it support custom templates?

Yes, you can specify a custom template source URL using the `--templateSource` flag. The default template is Vercel’s Next.js example.

5

What is the default repository name and template?

The default repository name is `scene-order-table`, and the default template source is `https://github.com/vercel/vercel/tree/main/examples/nextjs`.

コメント

「バージョン管理」の他のコンテンツ