Upload a database import

Send import-file bytes through the API with filename in the query string. Uploading the file does not start an import.

Tool: uploadDatabaseImport
Permission: database-imports:write
Kind: Destructive

Clients are told this tool can remove, overwrite or interrupt resources, or grant access. Set your client to ask before it runs it.

MCP can't carry file bytes. This tool returns the URL to send or fetch them with an HTTP client, using the same credential.

Arguments

Name	Type	Required	Limits
`filename`	`string`	Yes	At least 1 character(s)
`projectId`	`string`	Yes	At least 1 character(s)
`databaseId`	`string`	Yes	At least 1 character(s)

Full input schema

{
  "type": "object",
  "properties": {
    "filename": {
      "type": "string",
      "minLength": 1
    },
    "projectId": {
      "type": "string",
      "minLength": 1
    },
    "databaseId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "projectId",
    "databaseId",
    "filename"
  ],
  "additionalProperties": false
}

Example call

The params of a tools/call request. Replace the placeholder values with your own IDs.

{
  "name": "uploadDatabaseImport",
  "arguments": {
    "projectId": "REPLACE_WITH_PROJECT_ID",
    "databaseId": "REPLACE_WITH_DATABASE_ID",
    "filename": "source.zip"
  }
}

Result

The same data as the API operation, wrapped as {"untrusted_data": true, "source": "uploadDatabaseImport", "note": "...", "data": ...} so the model treats project content as data, not instructions.