Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
mcdev_search_docsB

Search bundled sfmc-devtools wiki Markdown (from GitHub wiki) for mcdev configuration, commands, markets, createDeltaPkg, build, validations.

mcdev_explain_config_keyA

Explain a .mcdevrc.json concept (markets, marketList, createDeltaPkg, deployment, validations, etc.) with a short summary and wiki file hints.

mcdev_component_checklistA

Return a structured checklist of questions and dependent metadata types for authoring or migrating SFMC components with mcdev (e.g. journey, automation).

mcdev_list_metadata_typesB

List metadata types supported by the installed mcdev package (from Mcdev.explainTypes). Optional filter substring.

read_mcdev_project_configA

Read .mcdevrc.json from a workspace path (never reads .mcdev-auth.json). Use to inspect markets and marketList with the assistant.

Prompts

Interactive templates invoked by user choice

NameDescription
plan_mcdev_changePlan an mcdev retrieve/build/deploy change using wiki-backed checks and dependency awareness.

Resources

Contextual data attached and managed by the client

NameDescription
mcdev-wiki-index

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct core purpose, but mcdev_search_docs and mcdev_explain_config_key both cover configuration concepts like markets and createDeltaPkg, so an agent could occasionally hesitate between them. The other tools are clearly separated by function: checklist, metadata types, and project config reading.

Naming Consistency4/5

Most tools follow a clear mcdev_verb_noun pattern, which is predictable and readable. Minor deviations exist: read_mcdev_project_config breaks the prefix convention, and mcdev_component_checklist is a noun phrase rather than a verb-led name.

Tool Count5/5

Five tools is a well-scoped set for a documentation and configuration-assistance server. Each tool covers a meaningful capability without bloat or redundancy.

Completeness4/5

The tool surface covers the main assistant workflows: searching docs, explaining config keys, getting authoring checklists, listing metadata types, and reading project config. It lacks direct execution or write operations, but that appears outside the server's stated purpose as a knowledge and inspection helper.

Maintenance

ActivityMaintained
ResponsivenessNo issues