Slack (Slackbot MCP client) + SpendixAI
Slack’s Slackbot can act as an MCP client for a remote server over Streamable HTTP. A Slack app developer adds SpendixAI to an app, an admin approves it, and each person then enables it.
Connect in a few minutes.
In Slack, SpendixAI is added to a Slack app under MCP Servers, or through the app manifest.
Open MCP Servers in your app
In the settings for your Slack app go to Features → MCP Servers and choose Get Started.
Enter the server details
Give the server a name such as spendixai, paste the SpendixAI server address from Developer → MCP connections and set the auth type to Dynamic client registration. Save, and Slack adds the mcp:connect scope for you.
Install and get it approved
Install the app to your workspace. The server is off by default, so an admin must enable it through the app approval workflow.
Enable it in Slackbot
Each person enables the connector in Slackbot and signs in to SpendixAI, choosing a workspace and a permission preset. Start with Read only.
Approve each tool call
Slack asks you to approve every third-party tool call with Allow once, Always allow or Deny. Choose Allow once for finance data.
{
"oauth_config": { "scopes": { "bot": ["mcp:connect"] } },
"mcp_servers": {
"spendixai": {
"url": "https://spendix-api.kriva.studio/mcp",
"auth_type": "dynamic_client_registration"
}
}
}The manual_auth type is for servers that need a fixed client ID and secret, which SpendixAI does not. You can change a tool’s approval choice later in the MCP configuration dialog.
What you need
- A Slack workspace where you can create and install an app
- An admin to approve the server through the app approval workflow
- A SpendixAI workspace
- The server address from Developer → MCP connections
Good to know
- The Slack plans that include this feature, and whether it is generally available or in beta, were not confirmed in the documentation we read.
- A server on a new domain needs fresh approval, each person can have 5 active MCP servers, and a tool call times out after 60 seconds.
- Slack requires Streamable HTTP. Servers that use standalone HTTP with SSE, or stdio, are not supported.
- Because every tool call needs your approval, Slack suits a finance server well, but Always allow removes that protection for the tool.
Questions to start with.
These need only read access. Add records or upload statements once you have moved to a broader preset.
Start read only. Widen it later.
Ask about transactions, summaries and reports. Nothing can be added, changed or uploaded.
Ask questions, add expenses and upload statements or receipts.
Everything above, plus categorisation rules and insights. Billing and member settings stay in the console.
Slack (Slackbot MCP client) and SpendixAI.
Why do I need a Slack app?
Slack’s documentation sets up an MCP server from an app’s settings or manifest, so someone who can create an app does the one-off setup and an admin approves it.
Can I stop it asking every time?
You can choose Always allow for a tool, but for finance data it is safer to keep approving each call.
Do I need to paste an API key?
No. The connection uses your SpendixAI sign-in and a consent screen, with dynamic client registration, so there is no secret to copy into a config file.
Can I keep the connection read only?
Yes. Read only is the recommended preset, and you can grant more access later or disconnect the assistant at any time from Developer → MCP connections.
Setup steps were checked against Slack’s own documentation in November 2026. Menus and commands change, so if a step does not match what you see, follow the vendor’s current guide.
Bring Slack (Slackbot MCP client) into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.



