SFMC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SFMC_MODE | No | Operation mode: 'read' (default) or 'write' | read |
| SFMC_CLIENT_ID | Yes | Client ID from SFMC installed package | |
| SFMC_SUBDOMAIN | Yes | Subdomain from SFMC installed package (e.g., mcXXXXX) | |
| SFMC_ACCOUNT_ID | No | Optional MID for a specific business unit | |
| SFMC_CLIENT_SECRET | Yes | Client Secret from SFMC installed package |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_data_extensionsA | Lista Data Extensions da Business Unit conectada, com nome, external key (customerKey), e opcionalmente os campos de cada uma. Suporta filtro por nome e paginação. |
| query_data_extensionA | Consulta registros de uma Data Extension pelo external key (customerKey). Suporta filtro simples (ex: "Status eq 'Active'"), ordenação e paginação. Retorna no máximo 50 linhas por chamada para não estourar o contexto. |
| validate_sqlA | Valida uma Query Activity do SFMC Automation Studio antes de executá-la. Checa construções não suportadas pelo dialeto restrito do SFMC (ORDER BY, CTE, MERGE, variáveis, temp tables, funções indisponíveis) e — se possível — confere se as Data Extensions e colunas referenciadas realmente existem. Retorna erros bloqueantes, avisos e sugestões. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: listing data extensions, querying records, and validating SQL. No overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_data_extensions, validate_sql).
Three tools is slightly below the typical range but appropriate for a focused server on data extensions and SQL validation.
Covers listing, querying, and SQL validation but misses create/update/delete for data extensions, which are common workflows.