← All documentation

MCP · Customer documentation

Deploy a GitHub MCP server as a remotely accessible endpoint.

What you prepare

A GitHub repository with MCP server code; access permission for private repositories.

Steps in the workspace

  1. 01Enter a repository URL and access mode.
  2. 02Check build and startup status.
  3. 03Add the issued URL to an MCP client.

Example request / integration

Register your search MCP from GitHub, then put its URL in your AI client and test the connection.

# Workspace: enter a GitHub repository URL, branch, and access mode.
# When the deployment finishes, copy the actual connection URL.
# Client settings vary: paste that URL in your MCP client's remote-server configuration.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Management API entry point

POST /api/servers

Repository URL, branch, and public or token-based access.

Deployment result, connection URL, and build/runtime status.

What it does not do

Some dependencies or launch methods are unsupported; verify actual client connectivity.

Feature comparison and sources

MCP publishing and distribution：Deploy from GitHub source and check status in the workspace.

Smithery：Documents MCP distribution, discovery, and connection workflows.

Feature comparison and sources · Smithery ↗
Overview, workspace, and dashboard

The product overview is public. The workspace handles creation, editing and history. The all-service dashboard shows usage and links for all 16 tools.

Workspace →Product overview →All-service dashboard →