Oh My Posh Validator
Validate oh-my-posh theme JSON and segment snippets in the agent before you ship a broken prompt config to every machine.
Overview
dev.ohmyposh/validator is an MCP server for the Ship phase that validates oh-my-posh configurations and segment snippets against the official schema via a hosted endpoint.
What is this MCP server?
- Remote MCP at https://ohmyposh.dev/api/mcp (streamable-http)
- Validates oh-my-posh configurations against the official schema
- Validates segment snippets—not just full config files
- Catalog version 29.14.0 aligned with Oh My Posh release line
- Documented at ohmyposh.dev/docs/advanced/mcp-server; source in oh-my-posh repo website/api/mcp
- Server version 29.14.0 (catalog)
- Remote endpoint: https://ohmyposh.dev/api/mcp (streamable-http)
- Validates full configurations and segment snippets per catalog description
Community signal: 22.8k GitHub stars.
What problem does it solve?
AI-assisted oh-my-posh edits often ship invalid JSON that breaks prompts silently until you open every terminal session.
Who is it for?
Indie builders and terminal-first developers iterating oh-my-posh themes with an MCP-aware coding agent.
Skip if: Users not on oh-my-posh, or teams wanting full shell security auditing beyond config schema validation.
What do I get? / Deliverables
After adding the validator MCP, your agent can flag schema violations in configs and snippets before you commit dotfiles or share themes.
- Schema validation results for oh-my-posh configs and segment snippets
- Fewer broken prompt deployments in dotfiles and shared themes
Recommended MCP Servers
Journey fit
Schema validation is a pre-ship quality gate—catch invalid terminal config before it breaks your daily driver shell. Official schema checking is automated verification of config artifacts, which fits the testing subphase on the Ship shelf.
How it compares
Official oh-my-posh schema validator MCP—not a generic theme marketplace or prompt designer skill.
Common Questions / FAQ
Who is dev.ohmyposh/validator for?
Developers using oh-my-posh who want Claude Code, Cursor, or similar agents to check theme JSON and segments against the official schema.
When should I use dev.ohmyposh/validator?
During Ship/testing when you are finalizing or sharing oh-my-posh configs and need fast schema validation before merge or rollout.
How do I add dev.ohmyposh/validator to my agent?
Add remote MCP https://ohmyposh.dev/api/mcp per ohmyposh.dev/docs/advanced/mcp-server in your client, then validate configs from the agent session.