Grok DDG Agent Services ddg_data_query
How to: Grok DDG Agent Services ddg_data_query
Add DDG Agent Services to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"ddg-agent-services-mcp": {
"type": "http",
"url": "https://mcp.daedalusdevelopmentgroup.com/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something ddg_data_query does. Grok lists the server's tools on connect and calls ddg_data_query itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that DDG Agent Services's identifier in your config matches the one above exactly.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
DDG Agent Services will not start until these are set, so ddg_data_query never becomes available.
-
DDG_AGENT_ID -
DDG_PRIVATE_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.