Register a new MCP server in the current teamspace. Each teamspace can have at most 30 registered MCP servers.
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. Each teamspace can register up to 30 MCP servers. If the limit is reached, the request returnsDocumentation Index
Fetch the complete documentation index at: https://developers.datagrid.com/llms.txt
Use this file to discover all available pages before exploring further.
409 Conflict. Remove an existing server before adding a new one.
You can provide auth in either form:
authorization_secret_id: reference an existing Datagrid secretauthorization: raw Authorization header value (Datagrid stores it as a secret automatically)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.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
255The HTTPS URL of the MCP server.
http 64102432Secret ID containing the full Authorization header value to use when calling this MCP server.
Raw Authorization header value (for example, 'Bearer '). Datagrid stores it as a secret and links it to this server. If both authorization and authorization_secret_id are provided, authorization takes precedence.
64000Created MCP server
mcp_server Secret ID containing the full Authorization header value used for this registered MCP server.
Safe subset of server metadata exposed to API consumers.