g-gremlin-dynamics

You use the MCP launcher to connect your MCP clients to Dynamics 365 Dataverse tools through a dedicated command that delegates to read/analyze tools by default or to write-enabled tools when you opt in, enabling streamlined access without invoking the broader command-line interface. This makes it easier to deploy and manage automated tools that interact with Dataverse while keeping write access under explicit control.

How to use

You will run the MCP launcher as part of your client configuration to expose Dynamics tools to MCP clients. The launcher provides two primary modes: read/analyze mode, which exposes read-only capabilities, and write-enabled mode, which makes write operations available (note that any write actions still require a plan hash for authorization). If you need to switch between modes, you can start the launcher with or without the write flag as shown in the configuration examples.

To enable your MCP client to use Dynamics tools, configure your MCP server entry to point to the launcher. Use the default command to expose read-only tools, or add the flag to enable writes when you need those capabilities. Your client will then communicate with Dataverse tools through the launcher, handling authentication and tool availability according to the selected mode.

How to install

Prerequisites: you should have Python installed and access to install Python packages. You will also need a tool for running Python-based commands. The following steps assume you are starting from a fresh environment.

Step 1: Install the main CLI and the Dynamics MCP launcher. Run these commands in your shell:

pipx install g-gremlin
pipx install g-gremlin-dynamics-mcp

Step 2: Configure Dynamics credentials for the main CLI so the MCP launcher can authenticate with Dataverse tools. Run the following command and follow prompts to set Dynamics credentials:

g-gremlin auth set dynamics

Configuration snippets you can use

Configure your MCP client to connect to the Dynamics MCP launcher in your environment by pointing to the launcher command. The following examples show how to expose the launcher in your client configuration to enable read-only access and, optionally, write access.

To expose read-only tools in your MCP client:

{
  "mcpServers": {
    "g-gremlin-dynamics": {
      "command": "g-gremlin-dynamics-mcp"
    }
  }
}

To expose write-enabled tools in your MCP client (writes require a plan hash for calls):

{
  "mcpServers": {
    "g-gremlin-dynamics": {
      "command": "g-gremlin-dynamics-mcp",
      "args": ["--enable-writes"]
    }
  }
}

Available tools

serve-dynamics (read/analyze tools)

Launches read-only Dynamics tools for analysis and data inspection without performing write actions.

serve-dynamics with writes

Launches Dynamics tools with write capabilities exposed; all write calls still require a plan_hash for authorization.

profile-aware startup

Optionally start the MCP launcher with a specific profile to select tool configurations depending on the environment.