Clients setup
Connect an external MCP client to a supported DataMaker deployment.
The current DataMaker server uses Streamable HTTP, with separate metadata and execution endpoints. The in-product agent already connects to these services. External setup requires deployment-specific authentication; there is no supported one-command API-key install for all clients.
Before configuring a client
Obtain these from your DataMaker administrator:
- The metadata endpoint, normally the API host plus
/mcp. - Any execution or system endpoint you need, such as
/mcp-exec. - A supported way to obtain and refresh a session JWT for that deployment.
- The authorized team and project IDs.
The request context is:
Authorization: Bearer <session-jwt>
X-Team-Id: <team-id>
X-Project-Id: <project-id>These are HTTP headers, not a complete client configuration file. Store session tokens using your client's secret-input mechanism. Do not copy browser cookies into a shared config or commit credentials.
Register and verify
- Add a remote MCP server using your client's Streamable HTTP transport and the supplied URL.
- Configure the authentication and scope headers using the client's supported settings. If it cannot send the required headers or refresh sessions, use DataMaker chat or REST/SDK automation instead.
- Connect and inspect the announced tool list. Register additional execution or system services separately when required.
- Ask it to list templates in the selected project. An empty list can be valid for a new project.
- Test a small generation only after confirming the project and available tool schema.
A successful metadata connection does not prove an execution service is configured. Desktop execution may require a local service and access to the target from that machine.
Troubleshooting
| Symptom | Check |
|---|---|
401 or authentication failure | Correct session token, expiry and API host. A REST API key does not authenticate the built-in MCP transport. |
403 or inaccessible resource | Team membership, project scope, permissions and pending approvals. |
| Generation tool absent | Inspect both the connected metadata and execution catalogues for your release. |
| Old install command fails | The legacy standalone npm package is unpublished; use the current services described above. |
| Tool schema changed | Reconnect to refresh the catalogue and use the advertised arguments. |
For unattended automation with durable API keys, use REST, Python or TypeScript.