# zipBoard MCP

> zipBoard manages visual feedback, bug tracking, and design review across websites, images, and documents. Connect your AI agent to track issues, build projects, and manage QA cycles directly from chat, eliminating manual dashboard updates.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** bug-tracking, visual-feedback, issue-management, document-review, quality-assurance, task-tracking

## Description

Need to collect detailed feedback on a new website or PDF? This MCP lets you connect any AI agent directly to the zipBoard platform for visual review and bug tracking. Instead of juggling screenshots and spreadsheets, your agent handles the whole process. You can tell it to list all active projects or create a new task right in the chat window. It pulls details on files, URLs, and organization structure so you don't have to click through five different dashboards just to get status updates. If you’re building complex automation that spans multiple services, knowing exactly what data flowed into the agent is critical. This is where Vinkius AI Analytics helps; it gives you full visibility into every tool call and piece of data used during a bug report, so nothing happens in the dark. You use this MCP when your work revolves around checking design concepts or finding bugs on live assets.

## Tools

### create_project
Sets up a new container for visual reviews and related assets.

### create_task
Adds a specific bug or issue to an existing project's tracking list.

### get_organization
Retrieves high-level metadata about the entire zipBoard account structure.

### list_files
Provides an inventory of all files and URLs attached to a specific project.

### list_projects
Generates a list showing every visual review project you have running.

### list_tasks
Pulls all the open bugs and tasks for a designated project.

## Prompt Examples

**Prompt:** 
```
List all active review projects in zipBoard.
```

**Response:** 
```
I've retrieved your projects. You have 3 active environments: 'Website Redesign', 'Mobile App QA', and 'Landing Page Review'. Which one should we check for issues?
```

**Prompt:** 
```
Show me the pending bugs for the 'Mobile App QA' project.
```

**Response:** 
```
There are 5 pending bugs for 'Mobile App QA', including 'Login button alignment' (High Priority) and 'Splash screen delay'. Would you like more details on any of these?
```

## Capabilities

### Start New Projects
Creates a structured container to hold all related files and tasks for a specific review effort.

### Log Bugs and Issues
Adds new tasks or bugs, setting priorities and assigning them directly within the project context.

### Get Organization Details
Pulls metadata about your entire zipBoard account setup to understand team structure and settings.

### Track Project Assets
Lists all the files or URLs attached to a project, giving you an inventory of what's being reviewed.

### View All Projects
Retrieves a complete list of every visual review project currently stored in your account.

### List Project Issues
Pulls all the tasks and bugs associated with a specific project for quick status checks.

## Use Cases

### The QA team needs a status report on three concurrent designs.
Instead of manually logging into the system and checking each project's dashboard, ask your agent to use `list_projects` first. Then, for each one, tell it to run `list_tasks`. You get an aggregated list of all bugs in a single response.

### A designer finished a concept and needs to start tracking feedback.
The agent handles the setup: first, it runs `create_project` with the name 'New Homepage V2'. Then, you can use `list_files` immediately after to attach all necessary mockups.

### A PM needs to see if a new feature was designed for the right team.
The agent runs `get_organization`. This quickly verifies which department owns the asset, saving minutes of digging through emails and internal wikis.

### You need to log three bugs found during a quick test session.
You tell your agent: 'Log these three issues for Project Alpha.' The agent uses `create_task` three times, setting the priority and assignee for each one automatically.

## Benefits

- Stop switching tabs. You can list all projects with one command, getting an overview of every review effort without leaving your agent window.
- Quickly create tasks or bugs using the `create_task` tool, controlling priority and assignment right in the conversation flow.
- Need to know what assets are involved? Use `list_files` to get a complete inventory of all URLs and documents associated with any project.
- Get an immediate snapshot of your entire team's setup using `get_organization`, so you never forget who owns what project.
- `list_projects` makes it easy to see every active review container, helping you manage dozens of different client projects at once.

## How It Works

The bottom line is you manage complex visual feedback cycles using natural language commands instead of clicking through interfaces.

1. Subscribe to this MCP and paste your zipBoard API Key into your agent settings.
2. Tell your AI client what you need—for example, 'List all projects that are ready for QA review.'
3. The agent executes the necessary tool calls and returns a plain text summary of the findings or actions taken.

## Frequently Asked Questions

**How do I list projects using the zipBoard MCP?**
You tell your agent to run `list_projects`. This tool pulls a complete list of all active review containers, letting you see everything in one go.

**Can I create tasks with the zipBoard MCP?**
Yes. You use the `create_task` tool to log new bugs or issues directly into an existing project's tracking board through your agent chat.

**What is the difference between list_files and list_projects?**
The `list_projects` tool shows you a directory of all review efforts. The `list_files` tool takes one project name, then gives you an inventory of only the assets (URLs/documents) attached to that specific project.

**I need organization details; which tool do I use?**
Use `get_organization`. This single call retrieves metadata about your entire zipBoard account setup, giving you an overview of team roles and configurations.

**How do I properly use the `create_project` tool?**
You pass data as a JSON string that defines the new project. To succeed, you must include required metadata like the project name and owner ID before running the command.

**What happens if I run `list_tasks` for a non-existent project?**
The tool will throw an API error code indicating that the specified Project ID was not found. You must verify the project's existence before listing tasks.

**Are there any rate limits or constraints when I run `list_projects` repeatedly?**
Yes, standard API rate limiting applies to this MCP. Exceeding the allowed number of calls per minute will result in an HTTP 429 error.

**What specific data points are returned when I call `list_files`?**
The tool returns metadata for every file, including the direct URL and a unique identifier linking it back to its parent project. This helps you map document scope.

**How do I find my zipBoard API Key?**
Log in to your zipBoard account, navigate to **Settings** > **Account**, and you will find your unique secret API Key in the API section.

**Can I assign tasks to specific team members via AI?**
Yes! When creating a task with the `create_task` tool, you can provide an `assignee_id` to direct the issue to the correct person automatically.