ecosystem MCP server
Commit Nov 14, 2026Provides shared infrastructure, templates, and coding standards for developing and managing Very Good Plugins MCP servers.
Also known as verygoodplugins/mcp-ecosystem
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- MIT
What is ecosystem MCP?
ecosystem provides shared infrastructure, templates, and coding standards for developing and managing Very Good Plugins MCP servers.
Summary generated from the project's README
About ecosystem MCP server
This repository serves as the central infrastructure and source of truth for developers building Very Good Plugins MCP servers. It provides standardized templates, coding requirements, and automated workflows to ensure consistency across various integrations, including tools for Evernote, Telegram, WhatsApp, and Toggl Track. By using this ecosystem, developers can maintain high quality through shared CI/CD pipelines, security scanning, and registry registration processes.
The system supports both TypeScript and Python development environments. TypeScript users work with Node.js 24 and Vitest, while Python developers utilize Python 3.11, pytest, and ruff. The repository includes specialized scripts to audit existing servers, apply new templates, and validate synchronization before opening pull requests. This centralized approach manages dependency baselines and repository profiles through machine-readable configurations like ecosystem-policy.json and server-inventory.json.
What you can do with it
- 1Audit existing MCP serversRun a script to check if a specific server follows the established ecosystem standards.
- 2Initialize new server templatesApply standardized TypeScript or Python templates to a new project directory.
- 3Register tools with the registrySubmit a completed MCP server to the official MCP Registry.
- 4Validate configuration changesEnsure that generated file differences are compatible with the repository profile before creating a pull request.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableverygoodplugins/mcp-ecosystem is public and reachablegithub.com/verygoodplugins/mcp-ecosystem ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/verygoodplugins/mcp-ecosystem ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Ecosystem
Shared infrastructure, templates, and standards for Very Good Plugins MCP servers.
Our MCP Servers
| Server | Description | npm/PyPI | MCP Registry |
|---|---|---|---|
| mcp-automem | Graph-vector memory for AI assistants | @verygoodplugins/mcp-automem | ✅ |
| mcp-edd | Easy Digital Downloads | @verygoodplugins/mcp-edd | ✅ |
| mcp-evernote | Evernote note management | @verygoodplugins/mcp-evernote | ✅ |
| mcp-freescout | FreeScout helpdesk integration | @verygoodplugins/mcp-freescout | ✅ |
| mcp-local-wp | WordPress via Local by Flywheel | @verygoodplugins/mcp-local-wp | ✅ |
| mcp-pirsch | Pirsch Analytics integration | @verygoodplugins/mcp-pirsch | ✅ |
| mcp-toggl | Toggl Track time tracking | @verygoodplugins/mcp-toggl | ✅ |
| mcp-ical | macOS Calendar integration | PyPI | ✅ |
| telegram-mcp | Telegram messaging | PyPI | ✅ |
| whatsapp-mcp | WhatsApp messaging | GitHub Release | ✅ |
| streamdeck-mcp | Elgato Stream Deck control | PyPI | ✅ |
Repository Structure
mcp-ecosystem/
├── README.md # This file
├── STANDARDS.md # Coding standards for all servers
├── PUBLISHING.md # Publishing checklist
├── config/
│ └── ecosystem-policy.json # Machine-readable repo profiles and policy
├── templates/
│ ├── typescript/ # Templates for TypeScript MCP servers
│ │ └── .github/workflows/
│ │ ├── ci.yml
│ │ ├── dependabot-auto-merge.yml
│ │ ├── release-please.yml
│ │ └── security.yml
│ └── python/ # Templates for Python MCP servers
│ └── .github/workflows/
│ ├── ci.yml
│ ├── dependabot-auto-merge.yml
│ ├── release.yml
│ └── security.yml
├── scripts/
│ ├── audit-server.sh # Audit a server against standards
│ ├── apply-templates.sh # Copy templates to a server
│ ├── configure-github-defaults.sh # Apply repo-level GitHub defaults
│ ├── render-managed-files.mjs # Generate profile-aware managed workflows/config
│ ├── validate-sync.mjs # Preflight generated diffs before opening PRs
│ ├── register-mcp.sh # Submit to MCP Registry
│ └── update-utm-links.sh # Update README links with UTM
└── server-inventory.json # Machine-readable inventory
Quick Start
Audit an existing server
./scripts/audit-server.sh ../mcp-freescout
Apply templates to a server
./scripts/apply-templates.sh typescript ../mcp-freescout
Preview downstream template drift
./scripts/propagate-templates.sh --server mcp-pirsch --dry-run
Validate a generated sync before opening a PR
./scripts/render-managed-files.mjs whatsapp-mcp ../whatsapp-mcp
./scripts/sync-template-baseline.mjs whatsapp-mcp ../whatsapp-mcp
./scripts/validate-sync.mjs whatsapp-mcp ../whatsapp-mcp
Register a server in MCP Registry
./scripts/register-mcp.sh ../mcp-freescout
Standards
See STANDARDS.md for complete coding standards.
Key requirements:
- TypeScript: Node.js >=24, ES2022, strict mode, Vitest, release-please
- Python: Python ≥3.11, pyproject.toml, pytest, ruff
- All: CI/CD, security scanning, MCP Registry, UTM tracking
Source Of Truth
mcp-ecosystem is the source of truth for shared MCP server workflows, config, and baseline dependency versions.
- Update templates and shared baselines here first.
- Merge the source-of-truth change to
main. server-inventory.jsonnow carries repo capabilities such aspackagePath,ciProfile,releaseProfile,securityProfile,templateTier,docsDispatch, andpropagate.config/ecosystem-policy.jsonis the machine-readable source for shared CI/release/security policy and repo defaults..github/workflows/propagate-templates.ymlopens or updateschore/template-syncPRs in downstream repos fromserver-inventory.json.scripts/render-managed-files.mjsgenerates profile-aware managed workflows/config instead of force-copying one workflow shape into every repo.- Managed standard workflow check contexts are normalized in this repo first:
TypeScript CI,Python CI, andLint PR Title. scripts/sync-template-baseline.mjsupdates managed dependency baselines with parsed JSON/TOML data and reports when lockfiles need regeneration.scripts/validate-sync.mjsblocks PR creation when the generated diff is incompatible with the repo profile.- TypeScript templates use
@modelcontextprotocol/serverv2, Zod 4, a stable Node 24Testcheck, and host-neutralAGENTS.mdinstructions. - Every v2 tool contract declares output and safety metadata, returns matching
structured and JSON-text results, uses
isErrorfor expected failures, and validates external credentials lazily so MCP discovery remains available. mcp-freescoutuses thets-vitest-integration-nonblockingprofile: its secret-mapped integration job runs after the stable test job and cannot block merges; its release metadata usesrelease-please-manifest.- Org rulesets are the canonical branch-protection layer for MCP repos; repo-level
GitHub booleans like
allow_auto_mergeare applied separately withscripts/configure-github-defaults.sh. - See STANDARDS.md for the current org rulesets, repo-level defaults, and rollout policy.
The propagation workflow requires an org/repo secret named VGP_TEMPLATE_SYNC_TOKEN with access to the downstream repos and workflow files.
Publishing
See PUBLISHING.md for the complete publishing checklist.
Links
Follow
- X: @jjack_arturo
- GitHub: @verygoodplugins
ecosystem MCP questions
What is the purpose of mcp-ecosystem?
It serves as the shared infrastructure, templates, and standards for Very Good Plugins MCP servers.
How can I audit an existing server against the ecosystem standards?
You can use the audit script by running ./scripts/audit-server.sh followed by the path to your server.
What are the coding requirements for TypeScript servers?
TypeScript servers require Node.js >=24, ES2022, strict mode, Vitest, and release-please.
How do I register a new server in the MCP Registry?
Use the registration script by running ./scripts/register-mcp.sh with the path to your server.