Oh My Posh Validator

dev.ohmyposhPublished by ohmyposh.devOfficial publisherv31.8.0Updated Oct 24, 2026

Validate oh-my-posh configurations and segment snippets against the official schema.

VerifiedStreamable HTTPWeb executableFiles & StorageDeveloper Tools

Overview

Oh My Posh Validator's hosted MCP server (ohmyposh.dev), published by ohmyposh.dev; no sign-in required; Streamable HTTP; 2 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
ohmyposh.dev
Endpoint
ohmyposh.dev
Last checked

Installation

In SourceWeft

  1. Open Oh My Posh Validator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.ohmyposh%2Fvalidator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "oh-my-posh-validator": {
      "type": "http",
      "url": "https://ohmyposh.dev/api/mcp"
    }
  }
}

README


title: MCP Validator Function description: 'Azure Function implementing the Model Context Protocol server for validating oh-my-posh configurations'

Overview

This directory contains the Azure Function that implements the Model Context Protocol (MCP) server for validating oh-my-posh configurations.

Endpoints

  • POST /api/mcp - MCP server endpoint that handles validation requests
  • GET /api/mcp - Returns server information and available tools

Supported Tools

validate_config

Validate an oh-my-posh configuration.

  • Supports JSON, YAML, and TOML formats
  • Returns detailed validation errors with JSON paths

validate_segment

Validate a segment snippet (individual prompt segment).

  • Validates against the segment schema definition
  • Useful for testing individual segments before adding them to a full configuration
  • Supports JSON, YAML, and TOML formats

Usage

As an MCP Server

Configure your MCP client to connect to this server:

json
{  "mcpServers": {    "oh-my-posh-validator": {      "type": "http",      "url": "https://ohmyposh.dev/api/mcp"    }  }}

Direct HTTP Requests

Get Server Info
bash
curl https://ohmyposh.dev/api/mcp
List Available Tools
bash
curl -X POST https://ohmyposh.dev/api/mcp \  -H "Content-Type: application/json" \  -d '{    "jsonrpc": "2.0",    "method": "tools/list",    "id": 1  }'
Validate a Configuration
bash
curl -X POST https://ohmyposh.dev/api/mcp \  -H "Content-Type: application/json" \  -d '{    "jsonrpc": "2.0",    "method": "tools/call",    "params": {      "name": "validate_config",      "arguments": {        "content": "{\"$schema\":\"https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json\",\"blocks\":[]}",        "format": "json"      }    },    "id": 1  }'
Validate a Segment Snippet
bash
curl -X POST https://ohmyposh.dev/api/mcp \  -H "Content-Type: application/json" \  -d '{    "jsonrpc": "2.0",    "method": "tools/call",    "params": {      "name": "validate_segment",      "arguments": {        "content": "{\"type\":\"path\",\"style\":\"powerline\",\"foreground\":\"#ffffff\",\"background\":\"#61AFEF\",\"template\":\" {{ .Path }} \"}",        "format": "json"      }    },    "id": 2  }'

Response Format

The validation result includes:

  • valid: Boolean indicating if the configuration is valid
  • errors: Array of validation errors (if any)
  • warnings: Array of warnings (best practices, deprecations)
  • detectedFormat: The detected or specified format
  • parsedConfig: The parsed configuration object (for debugging)

Example response:

json
{  "jsonrpc": "2.0",  "result": {    "content": [      {        "type": "text",        "text": "{          \"valid\": true,          \"errors\": [],          \"warnings\": [            {              \"path\": \"$schema\",              \"message\": \"Consider adding \\\"$schema\\\" property for better editor support.\",              \"type\": \"recommendation\"            }          ],          \"detectedFormat\": \"json\",          \"parsedConfig\": {...}        }"      }    ]  },  "id": 1}

Development

To test locally:

bash
cd website/apinpm installnpm start

Then send requests to http://localhost:7071/api/mcp

Publishing to MCP Registry

This server is published to the MCP Registry using GitHub Actions.

Publishing

Publishing is triggered automatically when you push a version tag (same as oh-my-posh releases):

bash
git tag v9.0.0git push origin v9.0.0

The workflow will:

  1. Extract version from the tag (e.g., v9.0.0 → 9.0.0)
  2. Update server.json version to match
  3. Validate the server.json file
  4. Authenticate with the MCP Registry using GitHub OIDC
  5. Publish the server to the registry

Note: The MCP server version will stay in sync with oh-my-posh versions automatically.

Files

  • server.json - MCP Registry server configuration
  • server.schema.json - JSON schema for validation
  • validate-server.js - Validation script
  • .github/workflows/publish-mcp.yml - GitHub Actions workflow

Validating server.json Locally

bash
cd website/apinpm installcd mcpnode validate-server.js

Source: website/api/mcp/README.md at commit e6c9eb7

Tools

2

validate_config

Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.

Parametersformatcontentrequired

validate_segment

Validate a segment snippet against the oh-my-posh schema. Useful for validating individual prompt segments before adding them to a configuration.

Parametersformatcontentrequired

Version history

2
  1. v31.8.0LatestOct 20, 2026
  2. v29.37.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Ohmyposh integrations