Dart MCP Server
An MCP server that exposes Dart SDK commands for AI-powered development.
Dart MCP Server
A distributable Model Context Protocol (MCP) server that exposes Dart SDK commands for AI-powered development. This server bridges the gap between AI coding assistants and Dart/Flutter development workflows by implementing the Model Context Protocol (MCP).
Features
This MCP server provides seamless access to the following Dart SDK commands:
| Command | Description |
|---|---|
dart-analyze | Analyze Dart code for errors, warnings, and lints |
dart-compile | Compile Dart to various formats (exe, AOT/JIT snapshots, JavaScript) |
dart-create | Create new Dart projects from templates |
dart-doc | Generate API documentation for Dart projects |
dart-fix | Apply automated fixes to Dart source code |
dart-format | Format Dart source code according to style guidelines |
dart-info | Show diagnostic information about the installed Dart tooling |
dart-package | Work with packages (get, add, upgrade, outdated, etc.) |
dart-run | Run Dart programs with support for passing arguments |
dart-test | Run tests with support for filtering and reporting options |
Key Benefits
- Intelligent Path Handling: Automatically resolves relative paths to absolute paths, ensuring commands work correctly regardless of working directory
- Project Auto-Detection: Identifies Dart/Flutter projects in common locations like home directories and workspaces
- Cross-Platform Support: Works on macOS, Linux, and Windows
- Zero Configuration: Works out of the box with sensible defaults
- MCP Integration: Compatible with any MCP client, including Windsurf, Cline, and other Model Context Protocol implementations
Prerequisites
- Node.js: 18.x or higher
- Dart SDK: 3.0 or higher installed and available in your PATH
Installation
Installing via Smithery
To install Dart MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @egyleader/dart-mcp --client claude
Using npx (recommended)
The server can be run directly without installation using npx:
npx @egyleader/dart-mcp-server
Global Installation
For easier access, you can install the server globally:
npm install -g @egyleader/dart-mcp-server
Then run it using:
dart-mcp-server
From Source
# Clone the repository
git clone https://github.com/egyleader/dart-mcp-server.git
cd dart-mcp-server
# Install dependencies
npm install
# Build the project
npm run build
# Run the server
node dist/index.js
Integration with MCP Clients
Windsurf / Codeium IDE Configuration
To use this MCP server with Windsurf or Codeium IDE, add the following to your mcp_config.json file (typically located at ~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"dart": {
"command": "npx",
"args": [
"-y",
"@egyleader/dart-mcp-server"
]
}
}
}
Environment Variables
DART_MCP_VERBOSE: Set to any value to enable verbose logging for debugging
MCP Tool Usage Examples
Here are examples of how to use the MCP tools provided by the server. These examples show the parameters that can be passed to each tool.
dart-analyze
Analyze Dart code for errors, warnings, and lints:
{
"path": "lib/main.dart",
"options": ["--fatal-infos", "--fatal-warnings"]
}
dart-compile
Compile Dart code to various formats:
{
"path": "lib/main.dart",
"format": "exe",
"output": "build/app",
"options": ["--verbose"]
}
Supported formats: exe, aot-snapshot, jit-snapshot, kernel, js
dart-create
Create a new Dart project from a template:
{
"projectName": "my_awesome_app",
"template": "console",
"output": "projects/my_awesome_app",
"options": ["--force"]
}
Note on projectName and output:
- If only
projectNameis provided, it's used as the directory name where the project is created. - If
outputis provided, it's used as the directory where the project is created. - The actual package/project name in Dart is derived from the final directory name by the Dart CLI.
Supported templates: console, package, server-shelf, web
dart-doc
Generate API documentation for a Dart project:
{
"path": ".",
"output": "doc",
"options": ["--exclude", "lib/generated"]
}
dart-fix
Apply automated fixes to Dart source code:
{
"path": "lib",
"apply": true,
"options": ["--pedantic"]
}
dart-format
Format Dart source code according to style guidelines:
{
"paths": ["lib/main.dart", "lib/models"],
"setExitIfChanged": true,
"options": ["--line-length=100"]
}
dart-info
Show diagnostic information about the installed Dart tooling:
{
"options": ["--verbose"]
}
dart-package
Work with packages (pub commands):
{
"command": "get",
"workingDir": ".",
"args": ["--offline"]
}
Supported commands: get, upgrade, outdated, add, remove, publish, deps, downgrade, cache, run, global
dart-run
Run Dart programs with support for passing arguments:
{
"script": "bin/server.dart",
"workingDir": ".",
"args": ["--port=8080", "--mode=production"]
}
dart-test
Run tests with support for filtering and reporting options:
{
"path": "test",
"workingDir": ".",
"options": ["--name=login", "--platform=chrome"]
}
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Tool API Reference
dart-analyze
Analyze Dart code in a directory or file.
{
path?: string; // Directory or file to analyze
options?: string[]; // Additional options for the dart analyze command
}
Example:
{
path: "lib",
options: ["--fatal-infos", "--fatal-warnings"]
}
dart-compile
Compile Dart to various formats.
{
format: 'exe' | 'aot-snapshot' | 'jit-snapshot' | 'kernel' | 'js'; // Output format
path: string; // Path to the Dart file to compile
output?: string; // Output file path
options?: string[]; // Additional compilation options
}
Example:
{
format: "exe",
path: "bin/main.dart",
output: "bin/app"
}
dart-create
Create a new Dart project.
{
template: 'console' | 'package' | 'server-shelf' | 'web'; // Project template
projectName: string; // Name of the project to create
output?: string; // Directory where to create the project
options?: string[]; // Additional project creation options
}
Note:
- If
outputis provided, the project will be created in that directory. - If only
projectNameis provided, it will be used as the directory name. - The actual Dart package name is derived from the final directory name.
Example:
{
template: "package",
projectName: "my_dart_library",
output: "projects/my_dart_library"
}
dart-doc
Generate API documentation for Dart projects.
{
path?: string; // Directory containing the Dart package to document
output?: string; // Output directory for the generated documentation
options?: string[]; // Additional documentation options
}
Example:
{
path: ".",
output: "doc/api"
}
dart-fix
Apply automated fixes to Dart source code.
{
path?: string; // Directory or file to apply fixes to
apply?: boolean; // Whether to apply the suggested fixes (default: true)
options?: string[]; // Additional fix options
}
Example:
{
path: "lib",
apply: true,
options: ["--pedantic"]
}
dart-format
Idiomatically format Dart source code.
{
paths: string[]; // Files or directories to format
setExitIfChanged?: boolean; // Return exit code 1 if there are formatting changes (default: false)
options?: string[]; // Additional format options
}
Example:
{
paths: ["lib", "test"],
setExitIfChanged: true,
options: ["--line-length=80"]
}
dart-info
Show diagnostic information about the installed tooling.
{
options?: string[]; // Additional info options
}
Example:
{
options: ["--verbose"]
}
dart-package
Work with packages (pub commands).
{
command: 'get' | 'upgrade' | 'outdated' | 'add' | 'remove' | 'publish' | 'deps' | 'downgrade' | 'cache' | 'run' | 'global'; // Pub subcommand
args?: string[]; // Arguments for the pub subcommand
workingDir?: string; // Working directory for the command
}
Examples:
// Add a package
{
command: "add",
args: ["rxdart"],
workingDir: "my_project"
}
// Get dependencies
{
command: "get",
workingDir: "my_project"
}
dart-run
Run a Dart program.
{
script: string; // Path to the Dart script to run
args?: string[]; // Arguments to pass to the script
workingDir?: string; // Working directory for the command
}
Example:
{
script: "bin/main.dart",
args: ["--verbose"],
workingDir: "my_project"
}
dart-test
Run tests for a project.
{
path?: string; // Path to the test file or directory
options?: string[]; // Additional test options
workingDir?: string; // Working directory for the command
}
Example:
{
path: "test",
options: ["--coverage", "--name=auth"],
workingDir: "my_project"
}
Development
# Watch mode for development
pnpm run dev
# Build for production
pnpm run build
Error Handling
The server implements comprehensive error handling:
- Command execution errors are captured and formatted appropriately
- Path resolution issues are reported with detailed diagnostics
- Timeout handling for long-running operations
- Proper exit code propagation from Dart commands
Contributing
Please see CONTRIBUTING.md for detailed contribution guidelines.
Our commit format follows:
<type>[optional scope]: [JIRA-123(optional)] <description>
Example:
feat(tools): [DART-456] add support for dart test tags
License
MIT
संबंधित सर्वर
Alpha Vantage MCP Server
प्रायोजकAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
vidlizer
Extract structured JSON from video, images, and PDFs using local LLMs (Ollama, LM Studio, oMLX) or via OpenRouter. Runs fully offline
Cisco SSH MCP Server
Connect to, configure, and monitor Cisco network devices like routers and switches via SSH.
pilot-mcp
Fast browser automation MCP server — in-process Playwright, 58 tools, cookie import from Chrome/Arc/Brave, 41% faster than @playwright/mcp.
Synth MCP
Access financial data like stock prices, currency info, and insider trading data using the Synth Finance API.
OSSInsight
Analyze GitHub repositories, developers, and organizations with data from OSSInsight.io.
Autoconsent MCP
A server for browser automation to create and test Autoconsent rules for web page consent management.
DevBrain
Finds relevant code snippets, developer articles, and blog posts based on your queries.
TestRail MCP Server
Interact with TestRail to manage test cases, projects, suites, and runs directly from your AI chat client.
Bedrock Server Manager
Manage your Bedrock server with natural language commands using the Bedrock Server Manager API.
BCMS MCP
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update content entries, manage media files, and explore your content structure—all through natural language conversations with AI. ## What is MCP? The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard developed by Anthropic that allows AI applications to securely connect to external data sources and tools. With BCMS MCP support, you can leverage AI assistants to: - Query and explore your content structure - Create new content entries with AI-generated content - Update existing entries - Manage your media library - Get intelligent suggestions based on your content model --- ## Getting Started ### Prerequisites 1. A BCMS account with an active instance 2. An MCP key with appropriate permissions 3. An MCP-compatible client (Claude Desktop, Cursor, or any MCP client) ### Step 1: Create an MCP Key 1. Navigate to your BCMS dashboard 2. Go to Settings → MCP 3. Click Create MCP Key 4. Configure the permissions for templates you want the AI to access:GET: Read entries 5. POST: Create entries 6. PUT: Update entries 7. DELETE: Delete entries Note: Right now, MCP only supports creating, reading and updating content. ### Step 2: Configure Your MCP Client You can find full instructions for integrating BCMS with your AI tools right inside BCMS, on the MCP page. But in general, installing BCMS MCP works in a standard way: ``` { "mcpServers": { "bcms": { "url": "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY" } } } ``` ## Available Tools Once connected, your AI assistant will have access to the following tools based on your MCP key permissions: ### Content Discovery #### list_templates_and_entries Lists all templates and their entries that you have access to. This is typically the first tool to call when exploring your BCMS content. Returns: - Template IDs, names, and slugs - Entry IDs with titles and slugs for each language Example prompt: "Show me all the templates and entries in my BCMS" --- ### Entry Management #### list_entries_for_{templateId} Retrieves all entries for a specific template with full content data. A separate tool is generated for each template you have access to. Returns: - Complete entry data including all meta fields - Content in all configured languages - Entry statuses Example prompt: "List all blog posts from my Blog template" --- #### create_entry_for_{templateId} Creates a new entry for a specific template. The input schema is dynamically generated based on your template's field structure. Input: - statuses: Array of status assignments per language - meta: Array of metadata for each language (title, slug, custom fields) - content: Array of content nodes for each language Example prompt: "Create a new blog post titled 'Getting Started with BCMS' with a brief introduction paragraph" --- #### update_entry_for_{templateId} Updates an existing entry for a specific language. Input: - entryId: The ID of the entry to update - lng: Language code (e.g., "en") - status: Optional status ID - meta: Updated metadata - content: Updated content nodes Example prompt: "Update the introduction paragraph of my 'Getting Started' blog post" --- ### Media Management #### list_all_media Lists all media files in your media library. Returns: - Media IDs, names, and types - File metadata (size, dimensions for images) - Parent directory information Example prompt: "Show me all images in my media library" --- #### list_media_dirs Lists the directory structure of your media library. Returns: - Hierarchical directory structure - Directory IDs and names Example prompt: "Show me the folder structure of my media library" --- #### create-media-directory Creates a new directory in your media library. Input: - name: Name of the directory - parentId: Optional parent directory ID (root if not specified) Example prompt: "Create a new folder called 'Blog Images' in my media library" --- #### request-upload-media-url Returns a URL you use to upload a file (for example via POST with multipart form data), which avoids pushing large binaries through the MCP tool payload. You still need a valid file name and MIME type when uploading, as described in the tool response. Availability: Only when the MCP key has Can mutate media enabled. Example prompt: “Give me an upload URL for a new hero image, then tell me how to upload it.” Input: - fileName: Name of the file with extension - fileData: Base64-encoded file data (with data URI prefix) - parentId: Optional parent directory ID Example prompt: "Upload this image to my Blog Images folder" --- ### Linking Tools #### get_entry_pointer_link Generates an internal BCMS link to an entry for use in content. Input: - entryId: The ID of the entry to link to Returns: - Internal link format: entry:{entryId}@*_{templateId}:entry Example prompt: "Get me the internal link for the 'About Us' page entry" --- #### get_media_pointer_link Generates an internal BCMS link to a media item for use in content. Input: - mediaId: The ID of the media item Returns: - Internal link format: media:{mediaId}@*_@*_:entry Example prompt: "Get the link for the hero image so I can use it in my blog post" --- ## Content Structure ### Entry Content Nodes When creating or updating entries, content is structured as an array of nodes. Supported node types include: Type Description paragraph Standard text paragraph heading Heading (h1-h6) bulletList Unordered list orderedList Numbered list listItem List item codeBlock Code block with syntax highlighting blockquote Quote block image Image node widget Custom widget with props ### Example Content Structure ``` { "content": [ { "lng": "en", "nodes": [ { "type": "heading", "attrs": { "level": 1 }, "content": [ { "type": "text", "text": "Welcome to BCMS" } ] }, { "type": "paragraph", "content": [ { "type": "text", "text": "This is your first paragraph." } ] } ] } ] } ``` ## Security & Permissions ### MCP Key Scopes Your MCP key controls what the AI can access: - Template Access: Only templates explicitly granted in the MCP key are visible - Operation Permissions: Each template can have independent GET/POST/PUT/DELETE permissions - Media Access: Media operations are controlled separately ### Best Practices 1. Principle of Least Privilege: Only grant the permissions needed for your use case 2. Separate Keys: Create different MCP keys for different purposes or team members 3. Regular Rotation: Periodically rotate your MCP keys ## Use Cases ### Content Creation Workflows Blog Post Creation "Create a new blog post about the benefits of headless CMS. Include an introduction, three main benefits with explanations, and a conclusion. Use the Blog template." Product Updates "Update the price field for all products in the Electronics category to apply a 10% discount" ### Content Exploration Content Audit "List all blog posts that don't have a featured image set" Translation Status "Show me which entries are missing German translations" ### Media Organization Library Cleanup "Show me all unused images in the media library" Folder Setup "Create folder structure for: Products > Categories > Electronics, Clothing, Home" ## Troubleshooting ### Common Issues #### "MCP key not found" - Verify your MCP key format: keyId.keySecret.instanceId - Ensure the MCP key hasn't been deleted or deactivated - Check that you're using the correct instance #### "MCP key does not have access to template" - Review your MCP key permissions in the dashboard - Ensure the required operation (GET/POST/PUT/DELETE) is enabled for the template #### Session Expired - MCP sessions may timeout after periods of inactivity - Simply start a new conversation to establish a fresh session ### Getting Help - Documentation: [thebcms.com/docs](https://thebcms.com/docs) - Support: [[email protected]](mailto:[email protected]) - Community: [Join BCMS Discord](https://discord.com/invite/SYBY89ccaR) for community support ## Technical Reference ### Endpoint POST https://app.thebcms.com/api/v3/mcp?mcpKey={MCP_KEY} ### Transport BCMS MCP uses the Streamable HTTP transport with session management. Sessions are maintained via the mcp-session-id header. ### Response Format All tools return structured JSON responses conforming to the MCP specification with: - content: Array of content blocks - structuredContent: Typed response data ## Rate Limits MCP requests are subject to the same rate limits as API requests: - Requests are tracked per MCP key - Contact support if you need higher limits for production workloads