Skip to main content
Registers a new MCP server at teamspace scope. Use this first in the MCP setup flow. Datagrid automatically attempts an initial tool sync after create. You can provide auth in either form:
  • authorization_secret_id: reference an existing Datagrid secret
  • authorization: raw Authorization header value (Datagrid stores it as a secret automatically)
If both are sent, authorization takes precedence. Ownership note:
  • authorization creates a Datagrid-managed secret for this MCP server. If you later rotate or clear that value, Datagrid cleans up the previously auto-created secret.
  • authorization_secret_id references an existing secret that you manage. Datagrid uses the reference, but does not delete that secret automatically.
curl -X POST https://api.datagrid.com/v1/organization/mcp-servers \
  -H "Authorization: Bearer $DATAGRID_API_KEY" \
  -H "Datagrid-Teamspace: $DATAGRID_TEAMSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "manhour",
    "base_url": "https://mcp.example.com/mcp",
    "transport": "http",
    "authorization": "Bearer external-api-token"
  }'