MokoGIT MCP Server

The MokoGIT MCP server puts your entire forge inside your AI assistant. Install it with a single npm command and Claude Desktop, Claude Code, or any MCP-compatible client can manage repositories, issues, pull requests, CI/CD, releases, org governance, and wikis on your MokoGIT instance — safely, through your own token. It's the same platform you use in the browser, now driveable in natural language.

What it is

@mokoconsulting/mcp-mokogit is a Model Context Protocol (MCP) server that exposes your MokoGIT instance to AI assistants. It authenticates with a MokoGIT access token and turns forge operations into tools your assistant can call directly — no copy-pasting API calls. It is TypeScript-first, ships as a modern ESM package, and requires Node.js 20 or newer.

It exposes 118 logical tools covering the whole forge, and supports multiple named connections so a single install can manage several MokoGIT instances. Tools act on your default connection unless you name another one.

Install (npm)

The @mokoconsulting/mcp-* servers are published to public npm. Install globally:

npm install -g @mokoconsulting/mcp-mokogit

Or run on demand without installing:

npx -y @mokoconsulting/mcp-mokogit

Requires Node.js 20 or newer. The packages are also mirrored to the MokoGIT registry; to pull from there instead, point the scope at it once in your ~/.npmrc:

@mokoconsulting:registry=https://git.mokoconsulting.tech/api/packages/MokoConsulting/npm/

Configure

The server loads a single JSON config file from ~/.mcp_mokogit.json (or the path in the MOKOGIT_MCP_CONFIG environment variable, if set). Each named connection is one MokoGIT instance:

{
  "defaultConnection": "moko",
  "connections": {
    "moko": {
      "baseUrl": "https://git.mokoconsulting.tech",
      "token": "your-mokogit-access-token",
      "insecure": false
    }
  }
}

Connection fields:

• baseUrl — the base URL of your MokoGIT instance.
• token — a MokoGIT access token (Settings → Applications → Generate Token). The server authenticates with MokoGIT's native Authorization: token header. Scope the token to exactly what the assistant should be able to do.
• insecure (optional) — set true to skip TLS verification for self-signed certificates (local development only).

Register the server with your MCP client (for example, a project-level .mcp.json or your Claude Desktop / Claude Code config):

{
  "mcpServers": {
    "mokogit": {
      "command": "npx",
      "args": ["-y", "@mokoconsulting/mcp-mokogit"]
    }
  }
}

Hosted SSE endpoint

In addition to running the server locally over stdio, MokoGIT exposes a hosted MCP endpoint over Server-Sent Events at https://git.mokoconsulting.tech/mcp/. Point an SSE-capable MCP client at that URL with your MokoGIT token to use the server without a local install. (Local stdio via npx remains the simplest option for Claude Desktop / Claude Code.)

Tool naming: mokogit_* (canonical)

The canonical name for every tool is mokogit_* — for example mokogit_repo_get, mokogit_pull_merge, mokogit_metadata_update. Legacy git_* aliases are still registered by default for backward compatibility during the transition window; new integrations should use the mokogit_* names. To expose only the canonical names (halving the tool count), set the environment variable MOKOGIT_MCP_LEGACY_ALIASES to a falsy value (0, false, off, or no).

Tooling

The 118 tools cover the whole forge:

• Repositories & files — create/edit/fork repos, read/write/delete files, directories, trees, branches, commits.
• Issues & project management — create/edit/search issues, comments, labels, milestones.
• Pull requests & code review — open/merge PRs, list changed files, create reviews.
• Actions (CI/CD) — list and inspect workflow runs.
• Organizations & users — org details, teams, members, user profiles and search.
• Releases & tags — create/get/delete releases, latest release, create/delete tags.
• Wiki — create/edit/delete wiki pages, revisions, search.
• Webhooks & notifications — list/create webhooks, list and mark notifications.
• Generic — a raw mokogit_api_request passthrough to any MokoGIT v1 endpoint, plus mokogit_list_connections.

Related MCP servers

The MokoGIT MCP is part of the @mokoconsulting/mcp-* family — mcp-mokossh (server ops), mcp-mokomysql (databases), mcp-mokomonitor (monitoring), mcp-mokobackup (backups), mcp-mokodreamhost, mcp-mokowindows, and mcp-mokoonyx (Joomla/MokoOnyx). Each installs the same way (npm install -g @mokoconsulting/mcp-<name>).

Get help

Open a support ticket or call (931) 279-6313.