Skip to main content
Connect Slicker to an AI assistant and ask questions about your business in your own words. Slicker MCP combines your data with Slicker’s billing and payments expertise, so your assistant can investigate a change, explain what the evidence shows, and suggest relevant best practices. It can also help you monitor for problems and investigate alerts. Slicker hosts the MCP server. You do not need to install or run a Slicker server yourself.

​
Get started with your agent

Use an AI assistant that supports remote MCP connections. Copy this instruction into the assistant you want to use—Claude, Claude Code, Codex, ChatGPT, or another compatible client. It should identify the client, guide you through Slicker sign-in, and perform a read-only check. You do not need to create or paste an API key to use the recommended OAuth connection.

Copy to your agent to get started

If you prefer to configure the connection yourself, see manual setup and troubleshooting. OAuth sign-in works with compatible remote MCP clients. The connection guide includes specific steps for Codex, Claude Code, Claude, and ChatGPT, plus an API-key alternative for clients that support private Bearer tokens.

​
Examples of what you can do

  • Get a health check across subscriptions, renewals, authorization, churn, retention, recovery, and revenue at risk.
  • Investigate a change, such as a drop in payment acceptance or a rise in first-renewal failures, and see which customers or segments are affected.
  • Explore payment performance by gateway, card network, issuer, country, payment method, 3D Secure outcome, or decline reason.
  • Examine failed invoices, recovery outcomes, and the exact retries or dunning actions Slicker took.
  • Review active alerts, investigate why one fired, and see available alert presets.
  • Describe a billing or payment problem you want to monitor, then review a proposed alert and its backtest before deciding whether to enable it.
These are examples, not a fixed menu of questions. Slicker can combine your data with billing and payments expertise, distinguish measured findings from recommendations, and explain data gaps. The available analyses and alert signals depend on your connected data and enabled Slicker capabilities.

​
What happens when you connect

The connection uses your Slicker account and the permissions you authorize. OAuth read access does not authorize alert changes: those additionally require the alert-write permission. Asking a question or investigating an alert is read-only. Alert proposals and rule changes are different: a proposal is saved but not enabled, while enabling a rule can start evaluations and notifications. If you use the API-key alternative, treat that key as a full administrator credential. Before your assistant creates or changes an alert, review the exact change and use your MCP client’s tool-approval controls. The assistant’s promise to ask first is helpful, but it is not an access control.