Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Connect AI assistants to your Vaiz workspace: tasks, projects, boards, documents and milestones.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
VAIZ_API_TOKEN, VAIZ_SPACE_ID, VAIZ_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"vaiz": {
"command": "npx",
"args": [
"-y",
"vaiz-mcp"
],
"env": {
"VAIZ_API_TOKEN": "your-value",
"VAIZ_SPACE_ID": "your-value",
"VAIZ_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add vaiz --env VAIZ_API_TOKEN=your-value --env VAIZ_SPACE_ID=your-value --env VAIZ_API_URL=your-value -- npx -y vaiz-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vaiz": {
"command": "npx",
"args": [
"-y",
"vaiz-mcp"
],
"env": {
"VAIZ_API_TOKEN": "your-value",
"VAIZ_SPACE_ID": "your-value",
"VAIZ_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"vaiz": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vaiz-mcp"
],
"env": {
"VAIZ_API_TOKEN": "your-value",
"VAIZ_SPACE_ID": "your-value",
"VAIZ_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
VAIZ_SPACE_ID envVAIZ_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain vaiz.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: VAIZ_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.1.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
DEPRECATED. This package is no longer maintained and this repository is archived.
Vaiz now provides a hosted MCP server at `https://api.vaiz.com/mcp` with OAuth. You no longer need a local
npxproxy or aVAIZ_API_TOKEN.
Cursor users: install the official Vaiz plugin from the Cursor Marketplace — https://github.com/vaizcom/vaiz-cursor-plugin
Any MCP client: point it at the remote server directly.
`json
{
"mcpServers": {
"Vaiz": { "url": "https://api.vaiz.com/mcp" }
}
}
`
Then authenticate when prompted (in Cursor: Settings → Tools & MCPs → Authenticate).
Guide: https://vaiz.com/help/tutorials/how-to-connect-vaiz-to-mcp · Support: https://vaiz.com/support
Existing installations of
vaiz-mcpkeep working for now, but will not receive updates or security fixes. Please migrate.
The original documentation is kept below for reference.
MCP (Model Context Protocol) client for Vaiz — connect Cursor/Claude to your Vaiz workspace.
npm install -g vaiz-mcp
Or use directly via npx:
npx vaiz-mcp
| Variable | Required | Description |
|---|---|---|
VAIZ_API_TOKEN | Yes | Your Vaiz API key (Bearer token) |
VAIZ_SPACE_ID | No | Your Vaiz Space ID |
VAIZ_API_URL | No | MCP API URL (default: https://api.vaiz.com/mcp) |
VAIZ_DEBUG | No | Set to true for debug output to stderr |
Create or edit ~/.cursor/mcp.json:
{
"mcpServers": { "vaiz": { "command": "npx", "args": ["vaiz-mcp@latest"], "env": { "VAIZ_API_TOKEN": "your-api-key", "VAIZ_SPACE_ID": "your-space-id" } } } }
Or after global installation (npm install -g vaiz-mcp):
{
"mcpServers": { "vaiz": { "command": "vaiz-mcp@latest", "env": { "VAIZ_API_TOKEN": "your-api-key", "VAIZ_SPACE_ID": "your-space-id" } } } }
Add to claude_desktop_config.json:
{
"mcpServers": { "vaiz": { "command": "npx", "args": ["vaiz-mcp@latest"], "env": { "VAIZ_API_TOKEN": "your-api-key", "VAIZ_SPACE_ID": "your-space-id" } } } }
After configuration, Cursor/Claude will automatically connect to your Vaiz workspace and gain access to:
To enable debug output, add the VAIZ_DEBUG variable:
{
"mcpServers": { "vaiz": { "command": "npx", "args": ["vaiz-mcp@latest"], "env": { "VAIZ_API_TOKEN": "your-api-key", "VAIZ_DEBUG": "true" } } } }
Debug messages will be output to stderr.
You can also use the library programmatically:
import { createVaizMCPClient } from 'vaiz-mcp';
const client = createVaizMCPClient({ apiKey: 'your-api-key', spaceId: 'your-space-id', });
// Initialize connection const initResult = await client.initialize();
// Get list of tools const tools = await client.listTools();
// Call a tool const result = await client.callTool('search', { query: 'important task', entityType: 'task' });
# Clone the repository
git clone https://github.com/vaiz/vaiz-mcp.git cd vaiz-mcp
npm install
npm run build
npm run dev
MIT