ca1b37e91dfa60dbc67f4a3e37965ea7d3df16be
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 6s
Generic: Repo Health / Access control (push) Successful in 2s
Universal: Changelog Validation / Validate CHANGELOG.md (push) Failing after 7s
MCP: Standards Compliance / Secret Scanning (push) Successful in 5s
MCP: Standards Compliance / Repository Structure Validation (push) Failing after 5s
MCP: Standards Compliance / Coding Standards Check (push) Failing after 5s
MCP: Standards Compliance / License Header Validation (push) Failing after 6s
MCP: Standards Compliance / Workflow Configuration Check (push) Failing after 6s
MCP: Standards Compliance / Documentation Quality Check (push) Failing after 6s
MCP: Standards Compliance / README Completeness Check (push) Failing after 6s
MCP: Standards Compliance / Git Repository Hygiene (push) Successful in 7s
MCP: Standards Compliance / File Naming Standards (push) Successful in 5s
MCP: Tool Inventory / inventory (push) Failing after 21s
MCP: Standards Compliance / Line Length Check (push) Failing after 6s
MCP: Standards Compliance / Script Integrity Validation (push) Successful in 8s
MCP: Standards Compliance / Insecure Code Pattern Detection (push) Successful in 4s
MCP: Standards Compliance / File Size Limits (push) Successful in 4s
MCP: Standards Compliance / Dead Code Detection (push) Successful in 7s
MCP: Standards Compliance / Binary File Detection (push) Successful in 9s
MCP: Build & Release / Build, Validate & Release (push) Failing after 42s
MCP: Standards Compliance / TODO/FIXME Tracking (push) Successful in 8s
MCP: Build & Validate / build (20) (push) Failing after 52s
MCP: Build & Validate / build (22) (push) Failing after 52s
MCP: Standards Compliance / Broken Link Detection (push) Successful in 5s
MCP: Standards Compliance / API Documentation Coverage (push) Successful in 6s
MCP: Standards Compliance / Accessibility Check (push) Successful in 7s
MCP: Standards Compliance / Performance Metrics (push) Successful in 7s
MCP: Standards Compliance / Terraform Configuration Validation (push) Successful in 10s
MCP: Standards Compliance / Version Consistency Check (push) Successful in 1m7s
MCP: Standards Compliance / Code Duplication Detection (push) Successful in 57s
MCP: Standards Compliance / Code Complexity Analysis (push) Successful in 58s
Universal: CodeQL Analysis / Analyze (actions) (push) Failing after 1m25s
Universal: CodeQL Analysis / Analyze (javascript) (push) Failing after 1m26s
Universal: CodeQL Analysis / Security Scan Summary (push) Successful in 2s
MCP: Standards Compliance / Unused Dependencies Check (push) Successful in 53s
MCP: Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 1m1s
MCP: Standards Compliance / Repository Health Check (push) Successful in 54s
MCP: Standards Compliance / Enterprise Readiness Check (push) Successful in 58s
MCP: Standards Compliance / Compliance Summary (push) Failing after 2s
Generic: Repo Health / Scripts governance (push) Successful in 5s
Generic: Repo Health / Release configuration (push) Failing after 5s
Generic: Repo Health / Repository health (push) Failing after 6s
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.
Languages
TypeScript
75.4%
Markdown
19%
Shell
2.8%
JavaScript
1.4%
Makefile
0.6%
Other
0.8%