Oh My Posh Validator is an MCP server published by dev.ohmyposh, hosted at ohmyposh.dev. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 2 tools, including validate_config, validate_segment.
Validate oh-my-posh configurations and segment snippets against the official schema.
4 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.
| Parameter | Type | Description |
|---|---|---|
| format | string | The format of the configuration (auto-detect if not specified) |
| content * | string | The configuration content as a string (JSON, YAML, or TOML) |
{
"name": "validate_config",
"description": "Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.",
"inputSchema": {
"type": "object",
"required": [
"content"
],
"properties": {
"format": {
"enum": [
"json",
"yaml",
"toml",
"auto"
],
"type": "string",
"default": "auto",
"description": "The format of the configuration (auto-detect if not specified)"
},
"content": {
"type": "string",
"description": "The configuration content as a string (JSON, YAML, or TOML)"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration.
| Parameter | Type | Description |
|---|---|---|
| format | string | The format of the segment (auto-detect if not specified) |
| content * | string | The segment content as a string (JSON, YAML, or TOML) |
{
"name": "validate_segment",
"description": "Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration.",
"inputSchema": {
"type": "object",
"required": [
"content"
],
"properties": {
"format": {
"enum": [
"json",
"yaml",
"toml",
"auto"
],
"type": "string",
"default": "auto",
"description": "The format of the segment (auto-detect if not specified)"
},
"content": {
"type": "string",
"description": "The segment content as a string (JSON, YAML, or TOML)"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.