Skip to main content
TemplateDX uses .mdx files, so any MDX-aware editor gives you syntax highlighting for free. AgentMark layers on top of that with a JSON Schema for frontmatter (enables model_name autocomplete) and MCP configs that let your editor’s AI query AgentMark docs + traces.

​
Syntax highlighting

Install an MDX extension — TemplateDX files are recognized as MDX.
EditorExtension
VS Code / Cursor / WindsurfSearch for “MDX” in the extensions panel (unifiedjs.vscode-mdx) — also available via Open VSX for VSCodium, Cursor, and Gitpod.
JetBrains IDEsMDX plugin
ZedBuilt-in MDX support.

​
Frontmatter autocomplete via JSON Schema

Run the AgentMark CLI to generate a JSON Schema for your prompt frontmatter: 
npx agentmark generate-schema
This writes .agentmark/prompt.schema.json, classifying your configured models into text_config, object_config, image_config, and speech_config blocks with model-name enum autocomplete. Most editors (VS Code, Cursor, JetBrains) will pick up the schema automatically when it’s referenced from your .prompt.mdx frontmatter.

​
MCP: let your editor AI query AgentMark

When you scaffold an AgentMark project with npm create agentmark@latest, the scaffolder writes MCP server configs tailored to your editor:
  • agentmark-docs — lets the editor’s AI query AgentMark documentation
  • agentmark-traces — lets the editor’s AI query your local trace data
Per-editor setup:
EditorConfig fileShape
VS Code.vscode/mcp.json{ "servers": { ... } }
Cursor.cursor/mcp.json{ "mcpServers": { ... } }
Zed.zed/settings.json{ "context_servers": { ... } }
Claude Code.mcp.json{ "mcpServers": { ... } } — requires "type": "http" on URL servers
See the scaffolder source for the exact per-editor config, or rerun npm create agentmark@latest -- --client <vscode|cursor|zed|claude-code> to regenerate.

​
Related

Docs MCP

Per-IDE setup for agentmark-docs

Trace MCP server

Local trace debugging via agentmark-traces