Database, storage and email

Use MCP to prepare and inspect resources. Your application uses the API or SDK for its own data, files and email.

Your connected AI uses these MCP tools to carry out your request. Application HTTP calls are documented separately in API reference.

Find the database

Use the organization’s existing Live or Test database. Confirm the intended environment and database ID before changing data.

  • list_databases

Tables and queries

MCP manages table structure and can query data. Bind input values with params; run_query uses sql while the direct Query API uses query. Separate calls do not share a transaction.

  • list_tables
  • create_table
  • update_table
  • delete_table
  • run_query

Files

MCP lists files and prepares transfers. Upload bytes to the returned URL and verify completion; preparing an upload does not transfer the file.

  • list_storages
  • list_files
  • prepare_file_uploads
  • get_file
  • delete_file
  • get_storage_metrics

Email

Your AI can register sending domains and check messages. The user publishes DNS records. Send only the requested recipient and content, and reuse the same idempotency key and content when checking an uncertain send.

  • list_mail_domains
  • create_mail_domain
  • delete_mail_domain
  • send_mail
  • list_mails
  • get_mail
  • get_mail_metrics