Connecting Claude to the DAZZM MCP server

Early Beta

The DAZZM MCP server is available as an Early Beta. This is an experimental feature: it is installed through Claude’s configuration file and cannot yet be set up from the user interface.

Introduction

The DAZZM MCP (Model Context Protocol) server lets you connect Claude directly to a DAZZM application. Once the connection is established, Claude can act in two areas:

• Modify the application by manipulating its definitions (models, pages, workflows, scripts, etc.);
• Read and modify the data contained in the application.

This guide covers the connection for Claude Desktop — which includes Claude Chat, Claude Cowork and Claude Code — as well as for Claude Code CLI, the command-line version. The preparation steps — generating the API key, choosing the environment, usage tips — are identical for both; only the place where the configuration is stored differs.

N.B.: The MCP server was designed to be connected to a development environment, where modifying definitions is allowed. See the Choosing the right environment section before connecting to any other environment.

Prerequisites

• Access to your DAZZM organization’s Account application;
• A DAZZM application with a development environment;
• Claude Desktop or Claude Code CLI installed;
• Node.js installed (the connection uses npx).

Steps to follow

1. Generate an API key (Account)

1. Open the Account application;
2. Access the application you want to connect;
3. Access a development environment of that application;
4. Create an API key. You can name it, for example, “Claude”;
5. Copy the key’s value.

2. Configure Claude Desktop

This configuration applies to all of Claude Desktop: Claude Chat, Claude Cowork and Claude Code will all have access to it. (For the command-line version of Claude Code, see step 3.)

Edit the Claude Desktop configuration file:

Claude\claude_desktop_config.json

Locate the mcpServers section. It may not exist by default; in that case, create it:

{
  "mcpServers": {}
}

Then add an entry for your application. Here is a complete example:

{
  "mcpServers": {
    "dazzm-<app-name>": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<app-name>-<env-name>.apps.dazzm.com/api/prod/mcp",
        "--header",
        "api-key:<YOUR_API_KEY>"
      ]
    }
  }
}

A few notes about this example:

• dazzm-<app-name> is the name of the MCP server as Claude will see it. We recommend naming it dazzm- followed by your application’s name. This is particularly useful if you control several applications through Claude;
• The URL follows the format https://<app-name>-<env-name>.apps.dazzm.com/api/prod/mcp, where <app-name> is the name of your application and <env-name> is the name of the environment you are connecting to — the same URL segment you use to access your application;
• The prod segment in /api/prod/mcp is fixed: it refers to the version of the DAZZM platform, not to your application’s environment. Do not replace it;
• api-key: is followed directly by the key value copied in step 1, with no space.

Save the file, then quit Claude and relaunch it.

N.B.: On Windows, you must quit Claude from the system tray (notification area), not just close its window.

3. Configure Claude Code CLI

Coming soon: the configuration procedure for Claude Code CLI. The preparation (API key, URL) is identical to Claude Desktop’s; only the place where the configuration is stored differs.

4. Verify the connection

When it launches, Claude connects to the configured MCP servers. If one of them does not work, an error is displayed immediately. If there is no error, the MCP server most likely loaded successfully.

To confirm, start a conversation in Claude Chat, Claude Cowork or Claude Code and press the + button: the list of active connectors should include your DAZZM server.

Tips

If you connect Claude to a brand-new application, it has few examples to rely on to find the right solutions. The first two tips help it find some:

Connect a reference application. Register a second MCP connection, this time to one of your complete, well-built applications. Choose any application you like, create an API key for it as well (step 1), then add it to the configuration and name that connector dazzm-examples. The name matters: it is what tells Claude that this is a registry of examples, and Claude will intuitively use it to draw on good DAZZM practices.

Point Claude to the documentation. At the start of a conversation, you can simply tell Claude to visit doc.dazzm.com to find more examples and guides about the platform.

Let Claude test in the application. To make sure Claude understands and tests what it is doing, it is really useful to give it access to the application it is working on. This is easy: open your browser already logged into the application and tell Claude to use the Chrome MCP to run tests on the application it is modifying. A good practice is to ask it to run end-to-end tests every time it has completed a task.

Choosing the right environment

The MCP server can act on any environment, but not all uses are equal:

1. Nominal case — development environment. This is what the MCP server was designed for: Claude can freely manipulate definitions and test data there.
2. Acceptable case — production environment, read-only. It is possible to connect the MCP server to a production environment if the goal is to use its data reading capabilities for analysis.
3. Strongly discouraged case — writing data outside a test environment.

Modifying data through the MCP server

The MCP server is capable of modifying data in a non-test environment, but this is strongly discouraged. Writing through the MCP server bypasses all of the application’s constraints and business rules: data is written directly to the database, which can lead to integrity errors that crash the application.