Connection details
Sign in to your Slicker account in the browser. The connection uses the access you authorize during sign-in.
Slicker asks for the
slicker:read permission to read recovery records, analyze your business, and investigate alerts. Creating or changing alert rules additionally requires slicker:alerts:write. Review the permissions shown during sign-in. Your organization’s access settings may also restrict who can receive alert-write permission. Even with that permission, review each proposed alert change in your assistant before approving the tool call.
Codex CLI
/mcp inside Codex to check the connection. For an in-depth investigation that exceeds your client’s default tool timeout, set tool_timeout_sec = 900 for this server in your user-level Codex MCP configuration. Codex’s MCP guide covers configuration and OAuth troubleshooting.
Claude Code
/mcp in an interactive Claude Code session. If an existing Slicker entry uses an API-key Authorization header, remove that entry and add it again without the header before using OAuth; Claude Code will not fall back to OAuth when an explicit header fails. See Claude Code’s MCP guide for server and sign-in management.
Claude on the web or Claude Desktop
Open Customize → Connectors → Add custom connector, name it Slicker, and enter the server URL above. Keep the detected OAuth sign-in option rather than choosing No sign in or adding a fixed request header. Follow the browser sign-in flow, then enable the connector for your conversation. On a Team or Enterprise plan, an owner may need to add the connector before you can connect your own Slicker account. The Claude connector guide has the current steps and plan requirements.ChatGPT
If your plan and workspace allow custom MCP servers, use ChatGPT on the web → Plugins → Add custom MCP server. Enter the server URL above, choose OAuth authentication, and use Client ID Metadata Document (CIMD) when offered. Create and install the connection, then sign in to Slicker when prompted. Do not choose an unauthenticated connection. Availability and controls depend on your ChatGPT plan and workspace; see OpenAI’s custom MCP setup guide. The ChatGPT desktop app’s local MCP configuration is separate from a ChatGPT web plugin. If you use the desktop app’s Settings → MCP servers, add Slicker as a Streamable HTTP server and select Authenticate when prompted. Follow OpenAI’s desktop MCP instructions if your app’s labels differ. A web connection does not automatically configure a local Codex session, or vice versa.Check the connection
In a new conversation, ask:Use only the connected Slicker MCP server. List one recent recovery action as a read-only connection check. If there are no actions, say so. Do not change any alerts.A successful empty result still confirms that Slicker accepted the connection. Then explore what Slicker can help with. Seeing a tool listed does not establish that every optional capability is enabled for your organization.
Organization API key alternative
Slicker also accepts organization API keys for MCP clients that can privately supply anAuthorization: Bearer header. Create or retrieve a key at Slicker API keys. An organization API key is a full administrator credential, unlike a scoped OAuth connection. Do not paste it into an AI chat, a command argument, source code, or a shared connector.
For Codex CLI, put the key in a local environment variable before starting the client, then configure only the variable’s name:
Troubleshooting
For help, contact Slicker support. See also Slicker API authentication.