Backwrite MCP setup and database tools
The documented @backwrite/mcp package runs as a local stdio server. A remote ChatGPT connection requires an actual MCP protocol endpoint, not a marketing page.
Run the package
Configure BACKWRITE_URL, BACKWRITE_SERVICE_KEY, and BACKWRITE_PROJECT_ID in the MCP client environment. Set BACKWRITE_BRANCH_ID to target a specific development or preview branch. Keep service credentials out of browser code and public chat output.
npx -y @backwrite/mcpInspect before modifying
Use backwrite_get_database_schema, backwrite_list_tables, and backwrite_describe_table to inspect the target schema. Use backwrite_list_branches to confirm the branch. Generate application definitions with backwrite_generate_types.
SQL and connection information
backwrite_execute_sql sends a SQL request to the selected project and optional branch. backwrite_get_connection_string returns connection coordinates. SQL can change or delete data, and connection output can be sensitive; obtain authorization before consequential writes.
Remote connection requirements
Use a stable HTTPS URL that accepts MCP initialization and advertises tools. Confirm the transport and authentication method with the deployment owner. Website reachability alone is not a successful MCP connection.