Mosvera MCP server
Commit Nov 1, 2026Lets an AI client manage a local registry of design aesthetics, compile design tokens, and generate deterministic provider payloads.
Also known as mosvera/mcp
- Stars
- 0
- Tools
- 17
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 1, 2026
- License
- Apache-2.0
What is Mosvera MCP?
Mosvera lets an AI client manage a local registry of design aesthetics, compile design tokens, and generate deterministic provider payloads. It exposes 17 tools, such as server_status, list_aesthetics, get_registry_document.
Summary generated from the project's README
About Mosvera MCP server
Managing a local registry of design aesthetics and compiling design tokens is what this server enables for developers and desktop assistants. It allows users to inspect, resolve, draft, and save Mosvera aesthetics directly through an AI client like Claude Desktop. The server operates entirely locally, meaning it never executes provider APIs or sends HTTP requests, and it does not require or store any API keys or secrets.
Users can interact with the registry to turn composition documents into portable aesthetic packs, CSS variables, or deterministic provider payloads. The server provides specific tools for various tasks, such as resolve_aesthetic for generating canonical models, compile_design_tokens for creating CSS, and compile_provider_payload for preparing data for services like HeyGen or ElevenLabs. It supports both read-only and writable modes, allowing for safe experimentation or full registry management through commands like save_aesthetic and import_aesthetic_pack.
What you can do with it
- 1Generate CSS from aestheticsAsk the AI to transform a specific design aesthetic into usable CSS variables.
- 2Create portable design packsExport a named aesthetic and its dependencies into a single portable file for sharing.
- 3Prepare provider-specific payloadsGenerate deterministic JSON payloads for services like ElevenLabs or HeyGen without making actual API calls.
- 4Manage local design registriesSave a new aesthetic based on an existing one to refine a specific brand voice.
Written from the project's README. Every use case is checked against a quote from it.
Mosvera MCP tools 17
Detected from the READMEserver_statuslist_aestheticsget_registry_documentvalidate_documentvalidate_registryvalidate_aesthetic_packpreview_aesthetic_importexport_aesthetic_packresolve_aestheticcompile_design_tokenscompile_provider_payloaddraft_aesthetic
Show all 17 toolsShow fewer tools
save_aestheticsave_registry_documentdelete_registry_documentwrite_merge_strategiesimport_aesthetic_pack
Configuration
MOSVERA_MCP_READ_ONLYMOSVERA_REGISTRY_DIR
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemosvera/mcp is public and reachablegithub.com/mosvera/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-01github.com/mosvera/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@mosvera/mcp
Mosvera for agents and desktop assistants. This package runs a local Model Context Protocol server that lets Claude Desktop, editors, and automation tools inspect, resolve, compile, draft, save, and delete Mosvera aesthetics in a local registry.
The server runs locally. It never executes provider APIs, never sends provider HTTP requests, and does not store API keys or secrets. It turns documents in your local registry into canonical Mosvera models, portable design tokens, CSS variables, deterministic provider payloads, and portable aesthetic packs.
10-Minute Quickstart
New users should start with the
10-minute quickstart.
It begins with Claude Desktop, then shows the npm/MCP path and runtime paths.
Install In Claude Desktop
The easiest path for non-command-line users is the Mosvera MCP Bundle:
- Download
mosvera-mcp-0.1.10.mcpbfrom the latest GitHub release. - Double-click the file, drag it into Claude Desktop, or install it from Claude Desktop Settings → Extensions → Advanced settings → Install Extension.
- Leave the registry directory blank to use the platform default, or choose a folder where your aesthetic registry should live.
Default registry locations:
| Platform | Default registry |
|---|---|
| macOS | ~/Library/Application Support/Mosvera/registry |
| Windows | %APPDATA%/Mosvera/registry |
| Linux/dev | ~/.config/mosvera/registry |
On first run, Mosvera seeds four public demo aesthetics into the registry:
quiet-editorial, technical-manual, cinematic-lab, and
claymation-playful-builder.
Language
Mosvera uses a small term stack on purpose:
- A named aesthetic is the user-facing intent, like
executive-editorial. - A composition document is the technical Mosvera document that resolves that intent.
- An aesthetic pack is a portable
.mosvera.jsonfile for sharing a named aesthetic and its registry dependencies. - A local registry is the folder where your templates, palettes, modifiers, composition documents, manifests, and merge strategies live.
- Tokens and provider payloads are compiled outputs for other tools to consume.
Install With npm
Use npm when you are wiring Mosvera into another MCP host or a developer workflow:
npm install -g @mosvera/mcp
mosvera-mcp
Run with a custom registry:
mosvera-mcp --registry ./my-aesthetic-registry
Run read-only:
mosvera-mcp --read-only
Environment overrides:
MOSVERA_REGISTRY_DIR=./my-aesthetic-registry mosvera-mcp
MOSVERA_MCP_READ_ONLY=1 mosvera-mcp
What To Ask Claude
Try these after installing the bundle:
List my Mosvera aesthetics.
Resolve the claymation-playful-builder aesthetic and show me the canonical model.
Compile quiet-editorial into CSS variables.
Export quiet-editorial as an aesthetic pack.
Preview importing this aesthetic pack into my registry.
Import the claymation-playful-builder sample pack into my registry.
Save a new aesthetic called executive-editorial based on quiet-editorial-base with a more compact, board-ready voice.
The saved documents are deterministic JSON in your local registry directory.
Canonical sample pack: https://raw.githubusercontent.com/mosvera/spec/main/examples/packs/claymation-playful-builder.mosvera.json
Tools
Every tool returns structuredContent plus a short text summary. Tools are
annotated with MCP read/write/destructive hints so clients can present normal
approval flows. Read tools do not mutate the registry. Write tools are only
registered when the active local registry is writable and the server is not in
read-only mode.
| Tool | Mode | Purpose |
|---|---|---|
server_status |
Read | Registry path, write mode, versions, counts, diagnostics. |
list_aesthetics |
Read | List named composition aesthetics in the active registry. |
get_registry_document |
Read | Fetch a template, modifier, palette, composition, or capability manifest. |
validate_document |
Read | Validate one document against a Mosvera schema kind. |
validate_registry |
Read | Validate the active registry and return diagnostics. |
validate_aesthetic_pack |
Read | Validate an inline or local .mosvera.json aesthetic pack. |
preview_aesthetic_import |
Read | Preview importing an aesthetic pack without writing files. |
export_aesthetic_pack |
Read | Export a named aesthetic as a portable .mosvera.json pack. |
resolve_aesthetic |
Read | Resolve a named or inline aesthetic into canonical Mosvera JSON. |
compile_design_tokens |
Read | Compile tokens and CSS variables from exactly one of aesthetic, aesthetic_id, or canonical. Unknown aesthetic ids return an error. |
compile_provider_payload |
Read | Advanced deterministic provider payload compilation; no provider HTTP call. Supports provider-specific provider_options such as HeyGen avatar_id/script, ElevenLabs voice_id, and short-video duration settings. |
draft_aesthetic |
Read | Draft a composition document without saving it. |
save_aesthetic |
Write | Create or update a named composition aesthetic. |
save_registry_document |
Write | Advanced create/update for registry documents and manifests. |
delete_registry_document |
Destructive write | Delete a registry document. |
write_merge_strategies |
Write | Replace merge-strategies.json with deterministic JSON. |
import_aesthetic_pack |
Write | Import an aesthetic pack into the active local registry. |
When the server starts with --read-only, write tools are not registered.
Registry Files
Mosvera reads JSON and YAML, but writes deterministic JSON only:
template.<id>.json
modifier.<id>.json
palette.<id>.json
composition.<id>.json
manifests/<provider>.manifest.json
merge-strategies.json
Aesthetic packs are exchanged as separate .mosvera.json files. They can carry
templates, palettes, modifiers, composition documents, and merge strategies.
They do not carry assets, provider manifests, credentials, remote URLs, or zip
bundles in v1.
To test import/export without authoring a pack from scratch, use the canonical
sample pack in
mosvera/spec/examples/packs.
IDs must be safe Mosvera references: lowercase letters, numbers, _, and -,
starting with a letter. Absolute paths, dotfiles, path traversal, unknown
kinds, and unsafe filenames are rejected.
Developer Verification
npm install
npm run ci
npm audit --audit-level=moderate
npm pack --dry-run
npm run mcpb:pack
npm run mcpb:inspect
The MCPB pack step creates:
build/mosvera/mosvera-mcp-0.1.10.mcpb
Package Boundaries
Use @mosvera/runtime when your application wants to call the TypeScript
runtime directly.
Use the Python package mosvera when you want the peer Python runtime.
Use @mosvera/provider-* packages when you want direct provider payload
compilation without MCP. The MCP package loads optional provider adapters when
they are installed and always keeps provider calls out of MCP. The current
compile-only provider ids are:
openai-gpt-image-1
bfl-flux-2-pro
sdxl-replicate
heygen-avatar-video
google-gemini-image
google-veo-video
runway-gen4-image
runway-gen45-video
elevenlabs-tts
adobe-firefly-image
meshy-text-to-3d
Use @mosvera/mcp when an agent, editor, or automation system should call
Mosvera through MCP tools.
License
Code is Apache-2.0. Documentation is CC-BY-4.0.
Mosvera MCP questions
What tools does Mosvera MCP provide?
It exposes 17 tools, including server_status, list_aesthetics, get_registry_document, validate_document, validate_registry.
Does the Mosvera MCP server send data to external APIs?
No, the server runs locally and never executes provider APIs or sends provider HTTP requests.
What are the default registry locations for different operating systems?
On macOS, it is in ~/Library/Application Support/Mosvera/registry; on Windows, %APPDATA%/Mosvera/registry; and on Linux, ~/.config/mosvera/registry.
Can I use Mosvera to generate CSS variables?
Yes, you can compile aesthetics into CSS variables using the compile_design_tokens tool.