About Opsphere for Slack
Opsphere for Slack connects Slackbot to the Opsphere MCP gateway and makes the tools enabled for each Opsphere tenant available within Slack.
Users can invoke supported operational tools through natural-language requests in Slackbot, including queries related to infrastructure, Kubernetes, cloud services, observability, deployments, incidents, logs, monitoring, repositories, and other configured integrations.
The app uses the integrations, credentials, environments, tool permissions, and policies already configured in your Opsphere tenant. Tool availability is controlled independently for the Slack runtime, allowing administrators to enable or disable specific capabilities without changing the underlying integrations. Requests are associated with the originating Slack workspace and user, while Opsphere applies tenant isolation, authorization, audit logging, and the configured execution context before running any tool.
Install Opsphere for Slack
Use Add to Slack from opsphere.io or your locale install URL. Slack redirects through OAuth; then complete MCP setup in Slackbot.
- Choose Add to Slack in the site footer, open /slack-install in your locale (for example /en/slack-install), or use Connect Slack on the Slack integration page.
- Approve Opsphere for Slack for your workspace when Slack opens slack.com/oauth/v2/authorize.
- In Slackbot, add Opsphere as a remote MCP app, authenticate to your Opsphere tenant, and approve tool access when prompted.
- Run a simple read-only question (for example deployment status or service health) to confirm tools respond.
Add Opsphere to Slack · Slack integration guide · Documentation · Watch installation walkthrough (YouTube)
Reconnect or authorize again
If OAuth, MCP, or tenant sessions expire, reinstall or reauthorize without changing your Opsphere integrations.
- Open /slack-install again and complete Slack OAuth if the app was removed or scopes changed.
- In Slackbot, open Opsphere MCP settings and sign in again with the correct Opsphere tenant.
- Review allow-once versus always-allow tool prompts if Slackbot stopped invoking tools.
- Ask your Opsphere administrator to confirm Slack runtime tools are still enabled for your tenant.
Permissions and tenant controls
Slack installation grants Slack-side scopes required for MCP connection. Operational access still follows Opsphere tenant policies.
- Slack OAuth covers workspace installation and MCP connection scopes configured for Opsphere for Slack.
- Opsphere enforces which tools are available to the Slack runtime separately from Cursor, Codex, or the web client.
- Each tool call is authorized against your tenant, environment, and integration credentials — not shared across customers.
- Audit logging and read-only defaults apply the same way as other Opsphere clients unless your tenant enables governed actions.
Troubleshooting
Slackbot does not list Opsphere tools
Confirm the app is installed for the workspace, MCP remote URL is configured, and you completed Opsphere sign-in. Reopen /slack-install if OAuth failed.
Tools return permission or integration errors
Verify the integration is connected in the Opsphere admin panel for the target environment and that the Slack runtime allows that tool category.
Wrong tenant or environment
Sign out of Opsphere in the MCP connection flow and authenticate again with the intended tenant. Check active work context with your administrator.
Install link or Marketplace validation fails
Use https://opsphere.io/en/slack-install (or the same path with your locale prefix). It redirects to Slack OAuth as required for direct install URLs.
Contact support
For billing, enterprise requirements, or issues not covered here, contact Opsphere directly. Engineers review operational and integration questions.
Privacy and terms
How Opsphere handles account data, credentials, and operational metadata.