36b642e23f
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 1s
Universal: Changelog Validation / Validate CHANGELOG.md (push) Failing after 3s
Generic: Repo Health / Access control (push) Successful in 2s
MCP: Standards Compliance / Secret Scanning (push) Successful in 4s
MCP: Standards Compliance / Repository Structure Validation (push) Failing after 3s
MCP: Standards Compliance / License Header Validation (push) Failing after 4s
MCP: Standards Compliance / Coding Standards Check (push) Failing after 3s
MCP: Standards Compliance / Workflow Configuration Check (push) Failing after 4s
MCP: Standards Compliance / Documentation Quality Check (push) Failing after 3s
MCP: Tool Inventory / inventory (push) Failing after 16s
MCP: Standards Compliance / README Completeness Check (push) Failing after 3s
MCP: Standards Compliance / Git Repository Hygiene (push) Successful in 3s
MCP: Standards Compliance / Line Length Check (push) Failing after 5s
MCP: Standards Compliance / File Naming Standards (push) Successful in 4s
MCP: Build & Release / Build, Validate & Release (push) Failing after 33s
MCP: Standards Compliance / Insecure Code Pattern Detection (push) Successful in 5s
MCP: Build & Validate / build (20) (push) Failing after 41s
MCP: Build & Validate / build (22) (push) Failing after 41s
MCP: Standards Compliance / File Size Limits (push) Successful in 4s
MCP: Standards Compliance / Binary File Detection (push) Successful in 3s
MCP: Standards Compliance / Script Integrity Validation (push) Successful in 33s
MCP: Standards Compliance / TODO/FIXME Tracking (push) Successful in 3s
MCP: Standards Compliance / Version Consistency Check (push) Successful in 49s
MCP: Standards Compliance / Broken Link Detection (push) Successful in 4s
Universal: CodeQL Analysis / Analyze (actions) (push) Failing after 1m2s
MCP: Standards Compliance / Dead Code Detection (push) Successful in 20s
Universal: CodeQL Analysis / Analyze (javascript) (push) Failing after 1m5s
MCP: Standards Compliance / API Documentation Coverage (push) Successful in 5s
MCP: Standards Compliance / Accessibility Check (push) Successful in 4s
MCP: Standards Compliance / Performance Metrics (push) Successful in 4s
Universal: CodeQL Analysis / Security Scan Summary (push) Successful in 1s
MCP: Standards Compliance / Terraform Configuration Validation (push) Successful in 13s
MCP: Standards Compliance / Code Complexity Analysis (push) Successful in 46s
MCP: Standards Compliance / Code Duplication Detection (push) Successful in 46s
MCP: Standards Compliance / Unused Dependencies Check (push) Successful in 46s
MCP: Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 48s
Universal: Sync Version on Merge / Propagate README version (push) Failing after 37s
MCP: Standards Compliance / Enterprise Readiness Check (push) Successful in 41s
MCP: Standards Compliance / Repository Health Check (push) Successful in 40s
MCP: Standards Compliance / Compliance Summary (push) Failing after 1s
Generic: Repo Health / Release configuration (push) Has been cancelled
Generic: Repo Health / Scripts governance (push) Has been cancelled
Generic: Repo Health / Repository health (push) Has been cancelled
Authored-by: Moko Consulting
3.8 KiB
3.8 KiB
Template-MCP
Template repository for creating MokoStandards-compliant Model Context Protocol (MCP) API servers. Provides the scaffolding, configuration patterns, and architecture conventions used by all Moko Consulting MCP servers, enabling AI assistants like Claude to interact with REST APIs through a standardized tool interface.
Features
- MCP server scaffolding -- pre-configured TypeScript project structure with entry point, tool registration, and stdio transport ready to go
- Multi-connection support -- built-in
config.jsonpattern for managing multiple named API connections with a default fallback; all tools accept an optionalconnectionparameter - REST API bridge architecture -- standardized pattern for bridging any REST API as MCP tools, with typed request/response handling
- TypeScript-first -- full TypeScript setup with
tsconfig.json, strict mode, and ES module output - Build tooling -- Makefile with
build,dev,clean, andlinttargets; npm scripts for compilation and development - MokoStandards compliant -- follows all Moko Consulting governance conventions: file headers, commit messages,
.gitattributes,.gitmessage, PR/issue templates - Example configuration --
config.example.jsondemonstrates the connection configuration schema - Documentation templates -- wiki pages for API reference, architecture overview, and installation pre-generated
Installation
- Create a new repository from this template (or clone directly):
git clone https://git.mokoconsulting.tech/MokoConsulting/Template-MCP.git my-mcp-server cd my-mcp-server - Install dependencies:
npm install - Copy and configure the connection file:
cp config.example.json config.json # Edit config.json with your API credentials - Build the project:
npm run build - Run the server:
node build/index.js
Configuration
| Path | Purpose |
|---|---|
src/ |
TypeScript source files (server entry, tool definitions, API client) |
config.example.json |
Example multi-connection configuration schema |
config.json |
Local connection configuration (gitignored) |
package.json |
npm dependencies and scripts |
tsconfig.json |
TypeScript compiler configuration |
scripts/ |
Build and development utility scripts |
docs/ |
Developer documentation |
Makefile |
Build, dev, clean, and lint targets |
Requirements
- Node.js 20.0.0 or later
- npm 9+
- TypeScript 5+ (installed via npm)
Documentation
Full documentation is available on the Wiki, including:
- API -- tool reference and connection parameter documentation
- ARCHITECTURE -- MCP server design and REST API bridge pattern
- INSTALLATION -- setup prerequisites and configuration guide
Contributing
See the wiki for development guidelines and contribution instructions.
License
This project is licensed under the GNU General Public License v3.0 or later -- see the LICENSE file.