Install D365FO MCP Server in Goose
What you need first
- Goose, installed.
- uv, which
gives the
uvxcommand the server starts with. - Your own values for
YOUR_D365FO_CLIENT_ID,YOUR_D365FO_CLIENT_SECRET,YOUR_D365FO_TENANT_ID.
Steps
- Open
~/.config/goose/config.yaml. On Windows it is%APPDATA%\Block\goose\config\config.yaml. - Add this entry. If the file already has
extensions, add only the entry inside it.
extensions:
"d365fo-client":
type: stdio
name: "d365fo-client"
enabled: true
cmd: "uvx"
args: ["d365fo-client==0.3.6"]
env_keys: []
envs: { "D365FO_CLIENT_ID": "YOUR_D365FO_CLIENT_ID", "D365FO_CLIENT_SECRET": "YOUR_D365FO_CLIENT_SECRET", "D365FO_TENANT_ID": "YOUR_D365FO_TENANT_ID" }
timeout: 300 - Replace
YOUR_D365FO_CLIENT_ID,YOUR_D365FO_CLIENT_SECRET,YOUR_D365FO_TENANT_IDwith your own values. - Save the file and start a new Goose session.
Check it worked
Ask Goose: List the tools of d365fo-client.
If it does not start
- spawn uvx ENOENT
- uv is not on the PATH that Goose sees. Install it, or write the
full path of
uvxin the config. - The server starts, but its tools fail
- A
YOUR_…placeholder is still in the config, or its value is wrong. - Nothing changes after a restart
- The file is not valid YAML any more. Check that the entry is indented like the lines around it.