ember-cli

This MCP server enables MCP clients to run Ember CLI commands directly within your projects. With this server, clients can request tasks like creating new Ember apps, starting a dev server, building for production, running tests with various filters, generating components, routes, services, and more. It exposes a suite of commands that map to Ember CLI actions, allowing you to orchestrate your development workflow from an MCP-enabled assistant or editor integration. The included command set mirrors common Ember CLI operations, so Claude Code or other MCP clients can ask for actions such as generating components, starting or building apps, and inspecting project details, all within the context of your local project via the MCP server.

To use it, configure your MCP client to target the ember-cli MCP server (as named in your MCP settings, here "ember-cli"), then issue phrases like "run my tests", "generate a component called user-card", or "build my app for production". The MCP server will translate these intents into Ember CLI commands, execute them in your project directory (cwd) as appropriate, and return the results back to the client. This enables a smoother, command-free workflow for common Ember tasks across multiple projects or environments.

Key capabilities include: running ember_test with optional filters, creating new apps with ember_new, starting a dev server with ember_serve, building with ember_build, generating components/routes/services with ember_generate, and querying project information with ember_project_info or listing addons and blueprints. Each command supports a cwd option to operate within a specific project, and most commands can be composed with additional Ember CLI arguments via the MCP interface.

Prerequisites:

• Node.js (v18+ recommended) and npm or yarn
• Access to the MCP client environment (e.g., Claude Code) and the ability to install or run MCP servers

Installation steps:

1. Install the MCP server package (globally or in your environment) so that the ember-cli-mcp server is available:

   npm install -g ember-cli-mcp

2. If you are configuring via MCP, ensure your MCP client recognizes the ember-cli server entry. Example configuration (as shown in this repository):

   { "ember-cli": { "command": "npx", "args": ["-y", "ember-cli-mcp"] } }

3. Start using CLI or your MCP client to connect to the server. If running locally, you may also start the underlying server manually depending on your deployment (see the project's instructions for local development and building if needed).

4. Optional local development workflow:

   git clone https://github.com/stefanoamorelli/ember-cli-mcp.git cd ember-cli-mcp npm install npm run build npm link

5. Verify installation by invoking a simple command via your MCP client, for example: asking the server to list available blueprints or run a small Ember CLI command in your project.

Tips and notes:

• The server wraps common Ember CLI operations; you can pass additional Ember CLI flags through the MCP client as part of the command arguments.
• Ensure your working directory (cwd) is set to the target Ember project when issuing commands that require a project context.
• If you encounter permission or PATH issues with npx, consider installing ember-cli-mcp globally or configuring your environment to resolve npm binaries correctly.
• For production usage, you may want to pin Node.js versions and test the MCP server against multiple Ember CLI versions to ensure compatibility with your projects.
• The npm package name for this MCP server is ember-cli-mcp; use it in your MCP configuration as shown in the example.
• If you rely on environment variables for paths or API keys in your projects, document and propagate them through the MCP client configuration as needed.