Integrations and connected tools
Connections give PHPSandbox’s agent access to external tools and context. Open Integrations in organization settings to review connections, their status and any reconnect action.
GitHub MCP
GitHub MCP supplies repository, issue and pull-request tools to the agent. It is separate from GitHub Sync, which connects the project’s sandbox to a repository. Connecting one does not prove the other is configured.
For committing and pushing project changes, read Version control.
Laravel Nightwatch and Sentry
Managed Nightwatch and Sentry connections supply production telemetry and issue context when available. Reconnect an expired connection before retrying an operation that depends on its tools.
To create tasks from incoming events, separately configure the project’s automation source and webhook secret.
Custom MCP connections
Use the prompt input’s context menu to add a custom MCP server. Follow the connection’s authentication flow, then review its status in organization integrations settings. That screen also lets you remove an unused custom connection.
Connect only tools you intend the agent to use. Store credentials in the secure connection form, not chat or source files.
Reconnecting a provider
If a connection shows Reconnect required, complete its authorization flow and check the updated status. A connection error or failed availability check means its state is unknown; it does not establish that the provider or app is unavailable.
SDK integrations
For connecting a provider programmatically to a sandbox, use SDK integrations. This is the programmatic interface to the same product, not another product to choose.
Choose the connection for the evidence you need
Use GitHub tools for repository, issue and pull-request context. Use Laravel Nightwatch for production telemetry and debugging signals, and Sentry for issue and event details. This lets the agent inspect evidence rather than relying only on a pasted summary.
Review whether a connection is disconnected, connected, needs reconnecting or has an error. The integration settings show custom connections’ names, server URLs, status and last error when present. Reconnect expired authorization before retrying dependent work, and remove unused connections deliberately.
Use custom MCP servers when a required tool or information source is missing from the managed connections. Keep an owner for each connection and its authentication lifecycle; adding a connection alone does not configure project task webhooks.