No coding required

Getting started, step by step

This guide takes you from a brand-new account to an AI assistant that knows your Dynamics 365 codebase and writes X++ against it. It should take about ten minutes, and you won't need to write a single line of code.

What this actually does

You already talk to AI assistants like Claude, Copilot or Cursor. On their own they guess at X++, because your Dynamics codebase is private and nothing they were trained on contains it, so the code they write often does not compile. Connecting one to Dynamics MCP lets it look things up for real: every table, field, class and label, checked before it writes a line. It then builds what you asked for, and you review it here.

Create your account

1 minute

Go to the sign-up page and register with your work email and a password. That's the whole process. There is nothing to install on your computer and no card required.

Once you're in, you'll land on your dashboard. It will be empty. That's expected, because everything on it gets built by your AI assistant later.

Make a project

1 minute

A project is just a folder for related work. If you're building something for the finance team and something else for warehouse, those are two projects, and things you build in one never get mixed up with the other.

Open Projects in the left-hand menu, type a name (something like Finance revamp), and click Create project.

Why this matters later

In the next step you make a key, and you choose the project it belongs to. Everything your assistant builds with that key is filed there. You never have to tell it which project you mean, and it cannot quietly put work somewhere else. Want to work on two projects at once? Make a key for each.

Choose your settings (or skip this)

2 minutes, optional

Open Preferences in the left-hand menu. These are house rules your assistant follows every time, so you don't have to repeat yourself in each conversation.

Object prefix

A few letters put at the front of everything created for you, so a table you call Vendor is actually saved as DM_Vendor.

It makes your own work instantly recognisable next to Microsoft's standard code. Every object gets one: DM_ to start with, change it to your own.

Generate number sequences

Whether numbering schemes get built for you, rather than only referred to.

Switched on already, because it's what most people want.

Translate labels into

Pick any languages you need, and the names shown on screen get translated into each one.

Useful for international teams. Each extra language costs more to run, so stick to about three unless you truly need more.

Happy to skip this?

Please do. Every setting already has a sensible default, and you can change them at any time, including after you've started building. Nothing here has to be decided up front.

Create your key

1 minute

A key is a long password that proves a request came from you. Your AI assistant uses it to reach your account, and nobody else can use it without it.

Open Connect an agent in the left-hand menu. Give the key a name describing where you'll use it. Claude on my laptop is a good one, because later you'll want to remember which is which. Click Generate key.

Copy it now: you only see it once

We deliberately don't keep a readable copy, so if you lose it, nobody (including us) can recover it. That's a safety feature, not an inconvenience. Paste it somewhere safe for the next couple of minutes. If you do lose it, just click Revoke and make a new one. It takes seconds.

Pick the project this key belongs to from the box next to the name. Everything built with it is filed there. One key per project per device is the usual arrangement.

Give the key to your AI assistant

3 minutes

Your assistant needs to be told where to find us. It keeps a settings file for connections like this, a small text file it reads when it starts up.

Still on Connect an agent, find the row of buttons and click the assistant you use: Claude Code, Cursor, VS Code, Visual Studio, Antigravity or Codex. Every one of them needs something slightly different, so the page rewrites itself for whichever you pick.

There are three ways to do it, easiest first. You only need one.

Let the assistant do it. Click Copy prompt and paste it into your assistant. It will find the right file, add the connection without disturbing anything already in there, check that it works, and tell you what it found. This is the one to use if you're not comfortable editing files.
One-click install. Cursor and VS Code can be set up by a single button: Add to Cursor or Add to VS Code. It opens the app and adds everything for you.
Do it by hand. Further down the page, under “Or add this to…”, you'll find the name of the file and the exact text to paste, with your key already filled in. If the file already has other things in it, keep them and add this alongside. Don't replace the whole file.

Then restart the assistant

Close it completely and open it again. It only reads that settings file at start-up, so until you restart, nothing will appear to have changed. This catches almost everybody out, and it's true even if you used the copy-prompt route, because the assistant can write the file but can't load it into the conversation it's already in.

The prompt contains your key

If you use the copy-prompt route, your key ends up in that chat's history. That's usually fine, since it's your own machine and your own account, but if you'd rather it didn't, use the by-hand route instead. Either way you can Revoke a key at any time and generate a fresh one.

Start working

ongoing

Open a new conversation and just describe what you want. You don't need to tell it which project to use. That comes from the key you gave it in step 5.

Then try something like:

“Show me the fields on CustTable, then build me a vendor rating table with a rating, a comment and a link to the vendor.”

The first half of that is the part that matters: it looks the real table up in your codebase before it writes anything, instead of guessing at field names.

Come back to this site and open Objects in the left-hand menu. Everything it built is listed there, grouped by project, with the field counts. If something isn't right, just say so in the conversation. You don't need to fix it here.

You don't need to know the right words

Describe what you want in your own language. “We need to track which supplier each part comes from” works perfectly well. You don't have to say “create a foreign key relationship”.

If something doesn't work

“My assistant doesn't seem to know about any of this”

It almost certainly wasn't restarted after you saved the settings file. Close it fully and reopen it. If that doesn't help, check you pasted into the exact file named on the Connect an agent page.

“It says the key isn't valid”

Check the key was copied whole, with no stray spaces at either end. If you've since clicked Revoke on it, it stopped working immediately, which is intended. Generate a new one and paste it in again.

“My work is showing up under the wrong project”

Work is filed under whichever project is active for your account, not one your assistant picks and not one baked into the key — a key works across all of your projects. Switch the active project on the Projects page; the next object your agent generates lands in the new one. Objects already filed stay where they are.

“Everything is named with DM_ in front and I didn't ask for that”

That's the object prefix from step 3. Every object carries one, which is how your own work stays recognisable next to standard Microsoft code, but you choose which. Change it in Preferences and the very next object uses the new one.

“It worked earlier and now says I'm out of calls”

Each plan includes a set number of tool calls per month (250 on the free plan), and once they're used up, further calls are refused unless your account has credits. Open Plan & usage to see where you are. The count resets at the start of each month.

“It says my account is suspended”

Suspended means your API keys have been switched off, though you can still sign in and see your account. Disabled means the whole account is switched off. Either way that's something we've done deliberately, so contact support and we'll explain.

“I pasted the setup prompt but the assistant says it can't find the tools”

That's expected until you restart. An assistant can write the settings file, but it only loads connections when it starts up, so the tools don't exist in the conversation that just created them. Close it fully, reopen, and approve the connection when it asks.

Ready?

Start at step 1. It's free while we're in preview.

Create my account

Prefer the technical version, or passing this to a developer? The reference docs are at /docs.