Oh My Posh Configurator
NPM · OHMYPOSH-CONFIGURATOR · SCANNED SEP 27
MCP server for creating, validating, and exporting Oh My Posh terminal prompt configurations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 155 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jamesmontemagno/ohmyposh-configurator). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1000 tokens (~52/item across 19 items; 13 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (85% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Oh My Posh Configurator MCP server?
Oh My Posh Configurator runs locally as an npm package, launched with npx -y ohmyposh-configurator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ohmyposh-configurator
claude mcp add jamesmontemagno-ohmyposh-configurator -- npx -y ohmyposh-configurator
{
"mcpServers": {
"jamesmontemagno-ohmyposh-configurator": {
"command": "npx",
"args": [
"-y",
"ohmyposh-configurator"
]
}
}
} {
"servers": {
"jamesmontemagno-ohmyposh-configurator": {
"command": "npx",
"args": [
"-y",
"ohmyposh-configurator"
]
}
}
} codex mcp add jamesmontemagno-ohmyposh-configurator -- npx -y ohmyposh-configurator
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jamesmontemagno-ohmyposh-configurator": {
"type": "local",
"command": [
"npx",
"-y",
"ohmyposh-configurator"
],
"enabled": true
}
}
} openclaw mcp add jamesmontemagno-ohmyposh-configurator --command npx --arg -y --arg ohmyposh-configurator
mcp_servers:
jamesmontemagno-ohmyposh-configurator:
command: "npx"
args: ["-y", "ohmyposh-configurator"] {
"McpServers": {
"jamesmontemagno-ohmyposh-configurator": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ohmyposh-configurator"
]
}
}
} assistant mcp add jamesmontemagno-ohmyposh-configurator -t stdio -c npx -a -y ohmyposh-configurator
{
"mcpServers": {
"jamesmontemagno-ohmyposh-configurator": {
"command": "npx",
"args": [
"-y",
"ohmyposh-configurator"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Analysed npm/ohmyposh-configurator@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jamesmontemagno/ohmyposh-configurator |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jamesmontemagno/ohmyposh-configurator/.github/workflows/publish-mcp-npm.yml@refs/tags/mcp-v1.1.1 |
| Rekor log index | 2337577762 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3d7804995172a3570c164e4463a14ba5d0b12e021ad4841865970c2f61488eb43d0898ac960780ed0473d7b168af46c5c1ee2b2be7d628e15e43a3f0e |
Background: How many MCP packages publish verified provenance →
Dependencies 155 packages
| Packages resolved | 155 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_segment ~132
Add a segment to an existing Oh My Posh configuration with smart defaults. Automatically applies appropriate colors, templates, and options based on segment type.
| Name | Type | Req | Description |
|---|---|---|---|
| blockIndex | number | – | The index of the block to add the segment to (default: 0) |
| config | string | yes | The existing Oh My Posh configuration as JSON string |
| segmentType | string | yes | The type of segment to add (e.g., "git", "python", "aws") |
| style | string | – | Style for the segment (default: powerline) |
| template | string | – | Optional custom template for the segment |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
No examples provided.
create_configuration ~102
Create a new Oh My Posh configuration from a natural language description. Generates a complete configuration with blocks, segments, and smart defaults.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Natural language description of the desired prompt (e.g., "developer prompt with git and python") |
| segments | array | – | Optional list of segment types to include (e.g., ["path", "git", "python"]) |
| style | string | – | Style for all segments (default: powerline) |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
No examples provided.
export_configuration ~64
Export an Oh My Posh configuration in different formats (JSON, YAML, TOML). Automatically cleans internal IDs and ensures proper formatting.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The Oh My Posh configuration as JSON string |
| format | string | – | Output format (default: json) |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| output | string | yes | – |
No examples provided.
get_ohmyposh_cli_status ~34
Check whether Oh My Posh is installed locally for this MCP server and return its version when available.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | – |
| reason | string | – | – |
| version | string | – | – |
No examples provided.
get_ohmyposh_segment_docs ~70
Get the official Oh My Posh documentation for a specific segment type. Returns detailed information from https://ohmyposh.dev/docs/segments/
| Name | Type | Req | Description |
|---|---|---|---|
| segmentType | string | yes | The segment type to get documentation for (e.g., "git", "python", "aws") |
No output schema declared.
No examples provided.
get_segment_info ~50
Get detailed information about a specific segment type including properties, options, and template variables.
| Name | Type | Req | Description |
|---|---|---|---|
| segmentType | string | yes | The segment type to get information about (e.g., "git", "python") |
| Name | Type | Req | Description |
|---|---|---|---|
| segment | object | yes | – |
No examples provided.
list_sample_configs ~19
List all available sample configurations with descriptions and tags.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| configs | array | yes | – |
No examples provided.
list_segments ~62
List all available Oh My Posh segments with their descriptions, categories, and default settings. Can filter by category or search by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter segments by category |
| search | string | – | Search segments by name, type, or description |
| Name | Type | Req | Description |
|---|---|---|---|
| segments | array | yes | – |
No examples provided.
load_sample_config ~33
Load a specific sample configuration by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| configId | string | yes | The ID of the sample configuration to load |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
| metadata | object | yes | – |
No examples provided.
modify_configuration ~79
Modify an existing Oh My Posh configuration. Can update global settings, add/remove blocks, modify segments, or change colors and templates.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The existing Oh My Posh configuration as JSON string |
| modifications | object | yes | Object describing the modifications to make (e.g., {"final_space": false, "palette": {...}}) |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
No examples provided.
render_live_preview ~92
Explicitly render an Oh My Posh configuration with the locally installed Oh My Posh CLI. This evaluates the configuration against the local environment and returns terminal ANSI output for the MCP preview app.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgeRisk | boolean | yes | Must be true to confirm that rendering executes the local Oh My Posh CLI against this configuration. |
| config | string | yes | The Oh My Posh configuration to render as a JSON string |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | – |
| output | string | – | – |
| reason | string | – | – |
| version | string | – | – |
No examples provided.
search_ohmyposh_docs ~96
Get links to the official Oh My Posh documentation at https://ohmyposh.dev/docs/ for a given topic. Returns documentation URLs and guidance for segments, configuration options, templates, and features.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (e.g., "git segment options", "powerline symbols", "color templates") |
| topic | string | – | Optional: Narrow search to a specific documentation topic |
No output schema declared.
No examples provided.
validate_configuration ~46
Validate an Oh My Posh configuration for correctness. Checks required fields, structure, and palette references.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The Oh My Posh configuration to validate as JSON string |
| Name | Type | Req | Description |
|---|---|---|---|
| validation | object | yes | – |
No examples provided.
What is the Oh My Posh Configurator MCP server?
Oh My Posh Configurator is an MCP server listed in the public MCP registry as io.github.jamesmontemagno/ohmyposh-configurator. MCP server for creating, validating, and exporting Oh My Posh terminal prompt configurations. This page covers its npm package (ohmyposh-configurator).
Is the Oh My Posh Configurator MCP server safe to use?
Oh My Posh Configurator scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Oh My Posh Configurator MCP server expose?
Oh My Posh Configurator exposes 13 tools: create_configuration, add_segment, modify_configuration, validate_configuration, export_configuration, and 8 more. Their descriptions and schemas cost roughly 879 tokens of context every time the server is loaded.
Is the Oh My Posh Configurator MCP server still maintained?
Oh My Posh Configurator is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.