MCP · OAuth 2.1

Connect Dingix to Gemini

The Gemini CLI speaks MCP over HTTP with a bearer token, so Dingix plugs straight in.

Why connect Dingix to your assistant

An AI assistant without your data can only give you advice. It can tell you what a good budget looks like; it cannot tell you whether yours is working. Connecting Dingix closes that gap: the assistant you already talk to gets your real agenda, your real ledger and your real history, and it can act on them in the same message where you ask.

What changes the moment it is connected

Answers come from your own records, not from generic advice. "Can I afford this?" is checked against your actual balance and this month's spending.
One sentence does the whole job. "Book the dentist for Tuesday at 4 and remind me the day before" creates the event and the reminder, with no app switching.
Nothing has to be copied between apps any more. What you tell the assistant is already in Dingix, and what is in Dingix is already available to the assistant.
Your context survives the conversation. Close the chat, come back next week, and it still knows your goals, the people who matter and what you decided last time.
It works the same in English, Persian and Arabic, including dates in the Solar Hijri and Hijri calendars.

Things people actually ask once it is connected

Where did my money go last month, and what is the one thing worth cutting?
Plan the rest of my day around the meetings I already have.
Log 40 on groceries and remind me to call my mother tomorrow at nine.
Am I on track for the savings goal I set in March?
What did we decide about my training plan three weeks ago?
Give me a full life report for this month and tell me where I slipped.

Before you start

The Gemini CLI installed and signed in.
A Dingix access key from Settings → API & integrations.

Step by step

Install the CLI

Run npm install -g @google/gemini-cli, start it with gemini and sign in.
Create a key

In Dingix → Settings → API & integrations, generate an access key and copy it.
Add the server

In ~/.gemini/settings.json, add Dingix under mcpServers with httpUrl set to the connector URL below and an Authorization: Bearer <key> header.

https://dingix.com/api/mcp
Verify

Restart Gemini and run /mcp — Dingix should be listed as connected.

Open Dingix

What it can do once connected

The same full tool set as the other clients, over the same endpoint.

What it costs you

Nothing to install and nothing to maintain. The connector is a single URL and one sign-in; there is no API key to generate, store or rotate. Dingix itself is free, and connecting it does not change that: the assistant runs on your existing subscription with that provider, not on a Dingix plan.

You stay in control

The assistant reads only your own account, never anyone else's.
It asks before writing anything you did not explicitly request.
It can never write a value the system computes for itself, such as a balance, a streak or a score.
Access is revocable in one click, from Dingix settings or from the assistant.

Security

The key is a full-access token. Treat it like a password and revoke it from Settings whenever you want.

Troubleshooting

Gemini shows no tools

Check the Authorization header reads “Bearer ” followed by the key, and that the URL ends in /api/mcp.