Centralized catalog, standards, and scaffolding for TMHSDigital Cursor IDE plugins, MCP servers, and developer tools.
Tools • Standards • Scaffold • Catalog Site
17 repos • 195 skills • 80 rules • 441 MCP tools
flowchart LR
A["registry.json\n(source of truth)"] --> B["GitHub Pages\ncatalog site"]
A --> C["README tables\n(below)"]
D["scaffold/\ncreate-tool.py"] --> E["New repo with\nall standards"]
F["standards/\n(conventions)"] --> D
G["site-template/\nbuild_site.py"] --> H["Tool repo\nGitHub Pages"]
Registry tracks every tool repo. Standards document conventions for CI/CD, folder structure, manifests, and versioning. Scaffold generates new repos that follow those standards automatically. Site template provides a shared build system for tool repo GitHub Pages sites.
Tool descriptions
| Tool | Description |
|---|---|
| CFX Developer Tools | AI-powered Cursor IDE plugin for FiveM and RedM resource development |
| Unity Developer Tools | Cursor IDE plugin for Unity game development with URP, HDRP, and Built-in render pipeline support |
| Docker Developer Tools | Cursor IDE plugin for Docker workflows with container management, Compose, and Dockerfile support |
| Home Lab Developer Tools | Home lab and Raspberry Pi workflows for Cursor with Docker Compose, monitoring, DNS, networking, and security |
| Mobile App Developer Tools | Cursor plugin for mobile app development with React Native, Expo, and Flutter support |
| Plaid Developer Tools | Cursor plugin and MCP companion for building on the Plaid API |
| Monday Cursor Plugin | Cursor IDE plugin for Monday.com with boards, items, sprints, docs, dashboards, and GraphQL |
| Steam Cursor Plugin | Steam and Steamworks integration for Cursor IDE for game developers, modders, and power users |
| Steam MCP Server | MCP server for Steam and Steamworks APIs with store data, player stats, reviews, achievements, and workshop tools |
| Developer Tools MCP | MCP server providing agent-callable read and write access to the TMHSDigital developer-tools ecosystem: registry, fleet status, drift checking, and standards management |
| CFX MCP | MCP server providing agent-callable tools for CFX/FiveM resource development, server management, and community platform integration. |
| Blender Developer Tools | Cursor and Claude Code skills, rules, snippets, and templates for Blender Python add-on and scripting development |
| Local AI MCP | Unified MCP server for managing local model runtimes (Ollama, LM Studio, and more): provider-agnostic discovery, lifecycle, hardware-fit, and delegated inference. |
| Screencast MCP | MCP server for Windows screen recording, frame sampling, and minimal ffmpeg edits (capture, watch, trim/concat/convert). |
| Tailscale MCP | MCP server for safe programmatic access to the local Tailscale daemon: tailnet discovery, SSH config generation, port sharing via Serve/Funnel, and latency matrices. |
| Godot Correctness MCP | Offline static correctness for Godot 4.x GDScript projects: anti-pattern linting via tree-sitter, cross-version API lookup and diff (4.4/4.5), and scene/resource/registry validation. Headless, offline, CI-first. |
| Bounty Radar MCP | Paid MCP server exposing a GitHub bounty radar tool. One tool, github_bounty_radar, priced at $0.05 USDC on Base and settled over x402 via the CDP facilitator. |
Documented conventions for building new developer tools. All docs in standards/.
| Standard | Summary |
|---|---|
| Folder Structure | Canonical repo layout for plugins and MCP servers |
| Plugin Manifest | .cursor-plugin/plugin.json specification and required fields |
| CI/CD | GitHub Actions workflows every repo must have |
| GitHub Pages | Documentation site setup (static HTML or MkDocs Material) |
| Commit Conventions | Conventional commits and version bumping rules |
| README Template | Standard README structure and required sections |
| AGENTS.md Template | AI agent guidance file structure |
| Versioning | Semver management and automated release flow |
| Release-doc-sync | Composite action contract for keeping CHANGELOG, CLAUDE, and ROADMAP in sync after auto-release |
| Born-Green Contract | Acceptance criterion every repo generator must satisfy |
| Testing | Test frameworks, coverage bar, and CI wiring |
| Skills | SKILL.md structure and frontmatter |
| Rules | .mdc structure, globs, and the secrets rule pattern |
| MCP Server | Tool naming, runtime, transport, destructive ops |
| Security | Disclosure, secrets handling, workflow supply chain |
| Licensing | DCO + inbound license grant model |
| Scope | What belongs in the directory and what does not |
| Lifecycle | Tool status transitions |
| Writing Style | Prose conventions across all repos |
Core principles
- Derived artifacts are generated, not edited -
registry.jsonis the single source of truth. README tables, catalog site, and About section are emitted from it. - Single branch - All repos use
mainonly. No develop, staging, or release branches. - Conventional commits - Every commit follows the conventional format. Release workflows parse them to determine version bumps.
- AI-agent friendly - Every repo includes
AGENTS.mdand.cursorrules. Standards are written so an agent can apply them without guessing. - Inbound DCO, outbound CC-BY-NC-ND-4.0 - See
standards/licensing.md. - Scope gate - Tools must be developer-facing, Cursor or MCP native, and actively maintained. See
standards/scope.md. - Lifecycle transitions are explicit - Tools move through documented states. See
standards/lifecycle.md.
Generate a fully standards-compliant repository from the command line.
Prerequisites:
pip install Jinja2python scaffold/create-tool.py \
--name "Unreal Developer Tools" \
--description "Cursor plugin for Unreal Engine development" \
--mcp-server \
--skills 5 \
--rules 3All options
| Flag | Required | Default | Description |
|---|---|---|---|
--name |
Yes | -- | Display name (e.g., "Unreal Developer Tools") |
--description |
Yes | -- | One-line description |
--slug |
No | auto | Kebab-case identifier (derived from name) |
--type |
No | cursor-plugin |
cursor-plugin or mcp-server |
--mcp-server |
No | false | Include MCP server scaffold |
--skills N |
No | 0 | Number of placeholder skill directories |
--rules N |
No | 0 | Number of placeholder rule files |
--license |
No | cc-by-nc-nd-4.0 |
cc-by-nc-nd-4.0, mit, or apache-2.0 |
--output |
No | ./output |
Output directory |
--author-name |
No | TMHSDigital | Author name for manifests |
--author-email |
No | contact@... | Author email |
What it generates
- Full folder structure per the standard
- Populated
plugin.jsonwith provided metadata - All 4 core GitHub Actions workflows (validate, release, pages, stale)
- Skeleton docs:
AGENTS.md,CLAUDE.md,README.md,CONTRIBUTING.md,CHANGELOG.md,CODE_OF_CONDUCT.md,SECURITY.md,ROADMAP.md - GitHub Pages site template (
docs/index.html) - MCP server scaffold (if
--mcp-server):server.py,tools/,data/,requirements.txt .cursorrules,.gitignore,LICENSE
Developer-Tools-Directory/
.github/
workflows/ CI/CD (validate, pages, release, stale, codeql, dep-review, label-sync)
release-drafter.yml Release notes category config
assets/ Logo
docs/ GitHub Pages catalog site
scaffold/ Repo generator + Jinja2 templates
site-template/ Shared GitHub Pages build system for tool repos
build_site.py Reads plugin.json, skills/, rules/, mcp-tools.json -> index.html
template.html.j2 Jinja2 HTML template with configurable branding
fonts/ Self-hosted Inter + JetBrains Mono woff2
SETUP-PROMPT.md Copy-paste prompt for applying template to a repo
standards/ Convention documentation (index in standards/README.md)
registry.json Tool registry (source of truth)
AGENTS.md AI agent guidance
CLAUDE.md Claude Code project docs
.cursorrules Cursor IDE agent rules
Pull requests welcome. See CONTRIBUTING.md for setup, how-to guides, and PR process.
Built by TMHSDigital
