Is io.github.POLONIBOI/zaai-dev-mcp safe to use?

io.github.POLONIBOI/zaai-dev-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.POLONIBOI/zaai-dev-mcp?

io.github.POLONIBOI/zaai-dev-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.POLONIBOI/zaai-dev-mcp?

io.github.POLONIBOI/zaai-dev-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

io.github.POLONIBOI/zaai-dev-mcp

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

0 tools GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

AI / ML Marketing

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-poloniboi-zaai-dev-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-poloniboi-zaai-dev-mcp)](https://mcppedia.org/s/io-github-poloniboi-zaai-dev-mcp)

Read me

What io.github.POLONIBOI/zaai-dev-mcp does

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

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.POLONIBOI/zaai-dev-mcp safe to use?: io.github.POLONIBOI/zaai-dev-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.POLONIBOI/zaai-dev-mcp?: io.github.POLONIBOI/zaai-dev-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.POLONIBOI/zaai-dev-mcp?: io.github.POLONIBOI/zaai-dev-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in ai-ml / marketing

View all →

Memory MCP Server98

Persistent memory using a knowledge graph

85.9k 5

Context Mode95

Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.

15.1k 6

Gemini Cli95

An open-source AI agent that brings the power of Gemini directly into your terminal.

104.3k 8

Better Chatbot94

Just a Better Chatbot. Powered by Agent & MCP & Workflows.

1.1k 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.POLONIBOI/zaai-dev-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML Marketing

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-poloniboi-zaai-dev-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-poloniboi-zaai-dev-mcp)](https://mcppedia.org/s/io-github-poloniboi-zaai-dev-mcp)

Read me

What io.github.POLONIBOI/zaai-dev-mcp does

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

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

Zaai Dev MCP

Model Context Protocol server for the Zaai Dev platform. Exposes your captured design references to MCP-compatible AI tools — Claude Code, Claude Desktop, Cursor, Continue, Cline, anything else that speaks MCP.

After a one-time token paste, prompts like "list my last 5 captures tagged hero and show me their palettes" call the workspace directly and pull back real data.

Install

You need:

Node 20 or newer (node --version)
A Zaai Dev workspace account at https://www.zaaistudio.com
An MCP token — mint one at https://www.zaaistudio.com/dev/settings/tokens (pick "mcp" as the kind). The token-mint screen also shows the config snippets below pre-filled with your secret.

Claude Desktop

Add to claude_desktop_config.json — merge into the existing mcpServers block, don't replace the whole file.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "zaai-dev": {
      "command": "npx",
      "args": ["-y", "@zaai-dev/mcp"],
      "env": {
        "ZAAI_API_TOKEN": "zaai_mcp_YOUR_SECRET_HERE"
      }
    }
  }
}

Restart Claude Desktop. The 17 tools below appear in the slash-command picker.

Cursor

Add to ~/.cursor/mcp.json — same JSON shape as Claude Desktop.

{
  "mcpServers": {
    "zaai-dev": {
      "command": "npx",
      "args": ["-y", "@zaai-dev/mcp"],
      "env": {
        "ZAAI_API_TOKEN": "zaai_mcp_YOUR_SECRET_HERE"
      }
    }
  }
}

Restart Cursor.

Claude Code (CLI)

One-liner — updates ~/.claude/mcp_servers.json automatically:

claude mcp add zaai-dev -e ZAAI_API_TOKEN=zaai_mcp_YOUR_SECRET_HERE -- npx -y @zaai-dev/mcp

Streamable HTTP (v0.3.0+, hosted-agent use cases)

If you want to run Zaai Dev MCP as a network service — e.g. behind a reverse proxy on Fly / Cloudflare / Render so hosted agents (Claude.ai web, OpenAI Assistants, custom frameworks) can reach it — use the zaai-dev-mcp-http binary instead of the stdio one:

ZAAI_API_TOKEN=zaai_mcp_... \
ZAAI_HTTP_PORT=3001 \
  npx -y --package=@zaai-dev/mcp zaai-dev-mcp-http
# POST /mcp for MCP traffic, GET /healthz for liveness

Single-tenant in v1.5 — one process serves one workspace token. Run one process per token if you need multi-tenant, or wait for v2 which adds per-request token binding. Most "I want HTTP" use cases are single-tenant anyway.

Tools

All tools except health need a valid token. All tools except health and whoami charge credits per successful call (your workspace plan determines the monthly grant — see pricing).

Captures (org-wide)

Tool	What it does	Cost
`health`	Server status + version + uptime. No auth.	0
`whoami`	Your userId, orgId, project scope, credit balance.	0
`list_captures`	Paginated list of your captures (newest first). Args: `q`, `cursor`, `limit`.	1
`search_captures`	Same as list but with `q` required. Tuned description for targeted retrieval.	1
`get_capture`	Full payload + signed screenshot URLs for one capture id.	1
`get_palette`	Just the palette slice (page) or eyedropper picks (element/composite).	1
`get_html`	Just the HTML. Page → full HTML; element → outerHTML; composite → concat with markers.	1
`get_animation`	Just the animation data — CSS transitions, keyframes, library hints.	1
`get_media`	Just the media inventory — videos, images, backgrounds, carousels.	1

Brand brief + references (project-scoped, v0.2.0+)

These tools each take a project_id arg (find via the workspace at zaaistudio.com/dev/projects/<id> — the UUID is in the URL).

Tool	What it does	Cost
`get_brand_brief`	Full published brief: positioning, values, voice, audience,

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.POLONIBOI/zaai-dev-mcp safe to use?: io.github.POLONIBOI/zaai-dev-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.POLONIBOI/zaai-dev-mcp?: io.github.POLONIBOI/zaai-dev-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.POLONIBOI/zaai-dev-mcp?: io.github.POLONIBOI/zaai-dev-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.