Zaai Dev Mcp

io.github.POLONIBOIPublished by GitHub account POLONIBOIv0.6.2Updated Oct 24, 2026

Zaai Dev brand brief + captured design references for MCP-compatible AI tools.

VerifiedSTDIODesktop onlyKnowledge & MemoryMedia & Design

Overview

AI-generated overview

Local MCP server that gives an assistant a user's Zaai Dev brand brief and captured design references, scoped to that user's account.

What you can do
  • Retrieves the user's brand brief and captured design references from Zaai Dev for use in MCP-compatible AI tools.
  • Scopes access to a single user's captures and options through a per-user token.
  • Talks to the Zaai Dev workspace over HTTP, with the base URL configurable for local or staging use.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to work from your own Zaai Dev brand brief and saved design references, for example when generating or reviewing design work that should follow your brand.
Requirements
Runs as a local process over stdio, installed from the npm package @zaai-dev/mcp (Node.js runtime). Requires a Zaai Dev account and a per-user MCP token in ZAAI_API_TOKEN, minted in the Zaai Dev developer settings with kind set to mcp. Network access to the Zaai Dev workspace; ZAAI_API_URL defaults to the hosted service and should only be overridden for local dev or staging.
Before you install
The token in ZAAI_API_TOKEN is a secret that authorizes access to your Zaai Dev captures and options; keep it out of shared configs and logs. Requests send your brand and design data to the configured workspace URL, so only override ZAAI_API_URL with an endpoint you trust. Desktop only; no web execution.

Installation

In SourceWeft

  1. Open Zaai Dev Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.2LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.