Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
SFMC AMPscript/SSJS/GTL tools + searchable help for 7 MC products (Engagement, Pardot…) via MCP.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"sfmc": {
"command": "npx",
"args": [
"-y",
"mcp-server-sfmc"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add sfmc -- npx -y mcp-server-sfmcPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"sfmc": {
"command": "npx",
"args": [
"-y",
"mcp-server-sfmc"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"sfmc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-sfmc"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub JoernBerkefeld, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.10.1) llegó al registro hace 23 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, NexusWindows
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
MCP server providing Salesforce Marketing Cloud language intelligence — AMPscript, SSJS, GTL, and Marketing Cloud Next (MCN) Handlebars — as Model Context Protocol tools, resources, and prompts for AI-assisted development and code review. Ships two searchable doc indexes: MCE help (Salesforce Help for Marketing Cloud Engagement administration and setup) and MCN developer docs (Marketing Cloud Next REST API and developer reference). Includes full Marketing Cloud Next (MCN) platform awareness: auto-detects whether a project targets MCE or MCN, restricts completions and validation to MCN-supported functions, flags SSJS as unsupported in MCN, surfaces MCN behavioral differences in hover and diagnostics, validates MCN Handlebars templates, and provides a migration toolkit to analyze and rewrite code for MCN — including AMPscript ↔ Handlebars and SSJS → Handlebars conversion.
Built on sfmc-language-lsp, the same engine that powers the SFMC Language Service VS Code extension.
sfmc-language-lsp 4.0.0 changes shared validator codes to canonical sfmc/... IDs and preserves quick-fix variants and original payloads in a namespaced envelope. See the LSP migration and rule documentation. Documentation URLs are owned by the LSP version, not this MCP package.
Consumer regression coverage checks the canonical SSJS diagnostics, distinct polyfill/replacement payloads, and overlap suppression. This is not a new MCP tool or a promise that every tool response exposes raw LSP diagnostics.
Version 2.10.0 adopts ampscript-data: ^4.2.0 and sfmc-language-lsp: ^4.2.0 from npm. This Winter ’27 (API 68) catalog update makes the current AMPscript and shared language-service metadata available to MCP clients. MCP validation and review output continues to format locations, severities, and messages rather than expose raw LSP codes or envelopes.
@mcp)This package is registered with the official MCP Registry as `io.github.JoernBerkefeld/mcp-server-sfmc` so it can appear in Visual Studio Code when you use the `@mcp` filter in the Extensions view (see the publish quickstart). Enable `chat.mcp.gallery.enabled` if the gallery does not show.
The registry only stores metadata; the server still runs locally via stdio (for example npx -y mcp-server-sfmc@latest). This is separate from `@contribute:mcp`, which lists VS Code extensions that contribute MCP definitions — use the SFMC Language Service for that path.
After publishing metadata (see Publish an MCP Server or the release workflow), you can confirm the entry with:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.JoernBerkefeld/mcp-server-sfmc"
If you use the SFMC Language Service extension (1.101+), it registers this MCP server for discovery in VS Code — you normally do not need to edit .vscode/mcp.json or run npm install for that path; VS Code still launches the published package via npx when the server starts.
For other editors, or if you prefer explicit configuration, use the npx or install options below.
You do not have to install the VS Code extension. Pick one way to run the server:
| Approach | When to use it | |
|---|---|---|
| `npx` (no install) | Default in the examples below. Runs the latest published version from npm on demand; first run may download the package. Requires Node.js and npm (which provides npx). | |
| `npm install -g mcp-server-sfmc` | Same CLI as npx, but the package stays on disk so startup is faster and you can set "command": "mcp-server-sfmc" with empty args in your MCP config. | |
| `npm install mcp-server-sfmc` in a project | Keeps a pinned version in that folder's node_modules — point your MCP config at npx mcp-server-sfmc with cwd set to the project, or run ./node_modules/.bin/mcp-server-sfmc directly. | |
| `sfmc-review-diff` (bundled CLI) | For CI: spawns this MCP server, calls review_change on a unified diff (stdin or file), exits non-zero on ERROR by default. Install the package in the job, then e.g. `git diff base...HEAD \ | npx sfmc-review-diff`. |
None of these replace the VS Code extension for editing (syntax, LSP, snippets); they only expose the MCP server to tools that speak the Model Context Protocol.
sfmc-review-diffReady-to-copy workflows (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines) live under [`ci-templates/`](./ci-templates/). They run `eslint-plugin-sfmc` on changed files and `sfmc-review-diff` on the PR/MR unified diff. See [`ci-templates/README.md`](./ci-templates/README.md) for what each file does and how the two checks differ.
| Feature | Details |
|---|---|
| Validation | Syntax errors, unknown functions, arity mismatches, unsupported SSJS syntax; target: 'next' flags MCN-incompatible functions and all SSJS; validate_handlebars checks MCN Handlebars helper names, arity, block balance, and unsupported constructs |
| Lookup | Full function signatures, parameters, return types, MCN compatibility badge (API version), behavioral notes, and examples |
| PR review | Diff-aware review tool that surfaces issues in the exact lines that changed |
| Fix suggestions | Concrete, compilable replacement code; target: 'next' includes MCN platform issues |
| Completions | AMPscript completions (filtered to MCN-supported when target: 'next'); SSJS catalog (redirects to AMPscript for MCN) |
| Platform detection | detect_sfmc_platform checks .mcdevrc.json (MCE) or sfdx-project.json (MCN) in the project root |
| MCN compatibility analysis | check_mcn_compatibility analyzes files for MCN readiness — per-function classification (supported / needs review / not supported), SSJS block migration difficulty, and an executive summary |
| MCN migration | rewrite_for_mcn (tool + prompt) deterministically rewrites AMPscript and converts convertible SSJS to AMPscript for MCN, then applies AI reasoning to remaining manual-rewrite sections |
| Code conversion | convertSsjsToAmpscript and convertAmpscriptToSsjs (tool + prompt hybrid) — rule-based conversion with AI-enhanced handling of flagged sections |
| MCN Handlebars | lookup_handlebars_helper, list_handlebars_helpers, get_handlebars_completions, and write_handlebars (authoring) backed by the handlebars-data catalog |
| Handlebars conversion | convertAmpscriptToHandlebars, convertHandlebarsToAmpscript, and convertSsjsToHandlebars (tool + prompt hybrid) — data-driven from ampscript-data handlebarsEquivalent / handlebarsExact |
| Prompts | Guided prompts for writing AMPscript/SSJS/Handlebars (with MCN constraints), reviewing code, converting between languages, and rewriting for MCN |
| Resources | Full function catalogs, keyword list, unsupported ES6+ syntax list, MCN Handlebars helper and binding catalogs |
| Help search | search_help (unified, auto-detects MCE vs MCN from project root); search_mce_help (MCE help, 7 product scopes); search_mcn_help (MCN developer API reference) |
Starting with version 2.10.1, validate_sfmc_html validates embedded AMPscript/GTL and applies SSJS checks only to actual server JavaScript bodies (runat="server", excluding AMPscript script bodies). Browser scripts and non-JavaScript script data are not sent to the SSJS validator. Server diagnostics retain locations in the original HTML, and browser declarations, Core loads, or polyfills cannot suppress server warnings. HTML without server JavaScript does not receive an SSJS incompatibility error solely because target is 'next'.
This tool does not validate browser JavaScript or provide DOM/type diagnostics. The standalone validate_ssjs tool continues to validate raw SSJS with its existing target-platform behavior.
This boundary uses the published validateMixedDocumentSsjs API from sfmc-language-lsp 4.3.1 or newer. Version 2.10.1 raises the dependency floor to ^4.3.1; release verification uses a clean registry-only installation.
mcp.jsonIf you are not using the SFMC Language Service extension's built-in MCP registration, add a .vscode/mcp.json file
Solo se muestra el principio; lee el resto en el repo