GitHub Copilot CLI + SpendixAI
GitHub Copilot CLI can add a remote HTTP MCP server and sign in to it with OAuth. Add SpendixAI with one command, then approve access in your browser.
Connect in a few minutes.
GitHub Copilot CLI adds remote servers with a single command, and /mcp auth handles the browser sign-in.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the SpendixAI server address.
Add the server
Run the command below in your terminal. It saves the server in your Copilot CLI MCP config file.
Sign in if asked
If the server shows that it needs authentication, run /mcp auth spendixai inside a Copilot CLI session and finish the browser sign-in.
Approve access
Sign in to SpendixAI, choose your workspace and pick a permission preset. Read only is the recommended start.
Keep permission prompts on
In the default mode Copilot CLI asks before it uses a tool. Avoid /allow-all and --allow-all for this server.
copilot mcp add --transport http spendixai https://spendix-api.kriva.studio/mcpConfig file alternative, in ~/.copilot/mcp-config.json (the tools field is required, and ["*"] means all tools): { "mcpServers": { "spendixai": { "type": "http", "url": "https://spendix-api.kriva.studio/mcp", "tools": ["*"] } } } For one session only, pass the same JSON with --additional-mcp-config.
What you need
- GitHub Copilot CLI installed and an active Copilot subscription
- On Copilot Business or Enterprise, the MCP servers in Copilot policy must be enabled (it is off by default)
- A SpendixAI workspace
- A browser for the sign-in step
Good to know
- Whether the very first sign-in starts automatically was not confirmed. The documentation describes /mcp auth for a server that needs authentication.
- A minimum Copilot CLI version was not stated in the documentation we read.
- The Copilot cloud agent and Copilot code review do not currently support remote servers that use OAuth, so these steps cover the CLI only.
- The --allow-tool flag pre-approves tools, and /allow-all, /yolo and --allow-all remove the prompts. Do not use them with your finance data.
- An organisation can restrict which servers are allowed, so a work account may block this connection.
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.
GitHub Copilot CLI and SpendixAI.
Why is my Copilot CLI refusing the server on a work account?
On Business and Enterprise plans an administrator must enable the MCP servers in Copilot policy, and a registry allowlist can block servers. Ask your administrator.
Can I limit which SpendixAI tools Copilot sees?
The tools field in the server entry limits which tools are exposed. SpendixAI’s Read only preset also stops any change to your records.
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 GitHub’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 GitHub Copilot CLI into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.