mcpField
Z
zaai-dev-mcp

zaai-dev-mcp

Local
zaaidev.comMedia & Design
RepositoryVisit website

About zaai-dev-mcp

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "poloniboi-zaai-dev": {
      "command": "npx",
      "args": [
        "-y",
        "@zaai-dev/mcp"
      ],
      "env": {
        "ZAAI_API_TOKEN": "<ZAAI_API_TOKEN>",
        "ZAAI_API_URL": "<ZAAI_API_URL>"
      }
    }
  }
}
Run commandnpx -y @zaai-dev/mcp
Environment variables to set
ZAAI_API_TOKENSecretPer-user MCP token, prefix zaai_mcp_. Mint at https://zaaidev.com/dev/settings/tokens (kind = mcp). Sent as Bearer auth on every workspace request; scopes the server to one user's captures and optionally a project allowlist.
ZAAI_API_URLWorkspace base URL. Defaults to https://zaaidev.com. Override only for local dev or staging.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@zaai-dev/mcp0.6.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.