Clone
1
templates-mcp
Jonathan Miller edited this page 2026-05-20 01:26:23 +00:00

← Back to Home

Template-MCP Reference

Template repository for creating MokoStandards-compliant Model Context Protocol (MCP) servers. Provides TypeScript scaffolding, configuration patterns, and architecture conventions for bridging AI assistants with REST APIs through a standardized tool interface.


Type MCP Server Template
Language TypeScript
License GPL-3.0-or-later
Repo Template-MCP
Wiki Template-MCP wiki

Purpose

Template-MCP is the starting point for all new MCP servers in the Moko Consulting ecosystem. It provides a pre-configured TypeScript project with tool registration, stdio transport, multi-connection config.json pattern, and a standardized REST API bridge architecture.

What the Template Provides

Component Description
MCP server scaffolding TypeScript project with tool registration and stdio transport
Multi-connection support config.json pattern for named API connections with default fallback
REST API bridge Standardized pattern for exposing any REST API as MCP tools
TypeScript-first Strict mode, ES modules, full type safety
Build tooling Makefile and npm scripts for build, dev, clean, lint
MokoStandards compliance Governance conventions, templates, file headers

Quick Start

  1. Click Use this template on the Template-MCP repo
  2. Clone and install dependencies:
git clone git@git.mokoconsulting.tech:MokoConsulting/my-mcp.git
cd my-mcp
npm install
  1. Configure connections in config.json:
{
  "connections": {
    "default": {
      "baseUrl": "https://api.example.com",
      "apiKey": "your-api-key"
    }
  }
}
  1. Implement your MCP tools in src/tools/
  2. Build and run:
npm run build
npm start

Architecture

The template follows a layered architecture:

Claude / AI Assistant
  ↓ MCP Protocol (stdio)
MCP Server (tool registration, routing)
  ↓ REST API Bridge
External API (any REST endpoint)

Each tool maps to one or more REST API operations. The multi-connection config allows a single MCP server to bridge multiple API endpoints.


Naming Convention

All MCP server repos use the mcp_moko* prefix with underscores:

Pattern Example
mcp_moko{service} mcp_mokowaas, mcp_mokocrm
mcp_moko{function} mcp_mokossh, mcp_mokodeploy, mcp_mokobackup, mcp_mokomonitor

Why underscores? MCP tool identifiers use mcp__server_name__tool_name. Hyphens in server names create parsing ambiguity.


Key Wiki Pages

Page Description
Installation Prerequisites (Node.js 20+) and configuration
API Tool reference and connection parameters
Architecture MCP server design and REST API bridge pattern

Existing MCP Servers (Built from This Template)

Server Repo Purpose
mcp_mokossh repo SSH server management
mcp_mokowaas repo MokoWaaS Joomla Web Services API
mcp_mokocrm repo MokoCRM Dolibarr API
mcp_mokogitea_api repo MokoGitea REST API + GitHub mirrors
mcp_mokogitea_wiki repo MokoGitea wiki CRUD
mcp_mokogitea_project repo MokoGitea project boards
mcp_mokogitea_issues repo MokoGitea issue tracking
mcp_mokobackup repo Akeeba, Dolibarr, MySQL, file backups
mcp_mokomonitor repo Server health + Grafana
mcp_mokodreamhost repo DNS/domains


Repo: moko-platform · moko-platform wiki

Field Value
Minimum Version 04.07.00
Platform all
Applies To MCP server repositories
Revision Date Author Description
1.0 2026-05-19 Moko Consulting Initial version