Miro

Exposes Miro's REST API through the Model Context Protocol (MCP) using StdioServerTransport, enabling Claude Desktop to query and inspect board structure, metadata, and content without direct API calls. Implements Zod-based schema validation for all request/response payloads, ensuring type-safe interactions between Claude and Miro's API surface. The server acts as a protocol bridge that translates natural language intents into structured Miro SDK calls with standardized error handling and response formatting.

Enables Claude to create new Miro boards and add items (shapes, text, frames, connectors) through MCP tools that validate inputs against Zod schemas before API submission. Each tool maps directly to Miro SDK methods, translating Claude's natural language requests into structured API calls with required parameters (board ID, item type, position, styling). Supports batch item creation through sequential tool invocations, allowing Claude to build complex board layouts programmatically.

Exposes Miro's tagging system through MCP tools that allow Claude to create tags, apply tags to items, and query items by tag. Implements tag management as a separate tool category that mirrors Miro's tag API, enabling Claude to organize board content hierarchically without manual tag creation. Tags persist across board sessions and can be used for filtering, searching, and bulk operations on tagged items.

Implements the Model Context Protocol (MCP) using @modelcontextprotocol/sdk v1.8.0 with StdioServerTransport, enabling seamless integration with Claude Desktop as a native tool provider. The server registers itself as an MCP server that Claude Desktop discovers and invokes through stdio communication, eliminating the need for manual API key management or custom integrations. Configuration is managed through environment variables (dotenv) and Claude Desktop's native MCP configuration file.

Exposes the complete Miro SDK functionality through 89+ MCP tools organized into functional categories (board management, item creation, tagging, permissions). Each tool implements a consistent interface pattern with Zod-based input validation, standardized error handling, and response formatting. The tool system is designed for extensibility — new tools can be added by following the established pattern without modifying core MCP infrastructure.

Implements Zod-based runtime validation for all tool inputs and outputs, catching type mismatches and invalid parameters before API submission. Each tool defines a Zod schema that validates request parameters, providing detailed error messages when validation fails. Error responses include diagnostic context (error type, validation details, suggested fixes) that Claude can interpret and use to correct requests.

Distributes the MCP Miro Server through multiple channels: NPM package (@k-jarzyna/mcp-miro) for direct installation, Smithery.ai platform for managed deployment, and Docker containerization for isolated environments. The NPM package includes a binary executable (build/index.js) configured through package.json's bin field, enabling one-command installation via npx. Docker support enables deployment in containerized environments without local Node.js setup.

Uses dotenv (^16.4.7) to manage Miro API credentials and server configuration through environment variables, eliminating the need to hardcode secrets in source code. Configuration is loaded from .env files at server startup, and credentials are passed to the Miro SDK through environment variables. Supports multiple deployment contexts (development, staging, production) through environment-specific .env files.

Provides a standardized tool implementation pattern that developers can follow to add custom tools beyond the built-in 89+. Each tool follows a consistent structure: input validation with Zod, error handling, and response formatting. The framework is documented in the Development Guide, enabling developers to create custom tools that integrate seamlessly with the existing MCP infrastructure without modifying core server code.