indigitall, now
connected to your AI
Pull your campaign, journey and chat statistics straight from Claude — no dashboards, no exports. Just ask, and your numbers come back clear and visual.
The indigitall MCP
The Model Context Protocol (MCP) is the open standard that AI agents like Claude use to connect — securely and in a standardized way — to external data and tools.
indigitall's MCP Gateway exposes your platform through that protocol. Instead of building a one-off integration, your agent gets a single, secure connector to the statistics that live inside indigitall.
Once connected, you describe what you want in natural language and your agent returns the numbers — campaign performance, journey conversion, chat metrics, messaging costs — ready to read and act on.
Your AI agent
You ask a question in Claude
indigitall MCP Gateway
Secure, standardized connection
Your indigitall instance
Campaigns · journeys · chat · pricing
From your question to a clear answer
Watch a request travel through the connector — and the data come back to life.

Connect indigitall to your AI agent
Everything the connector brings to your conversations.
Natural-language stats
Ask for your platform's metrics in plain language — campaigns, journeys, chat, pricing — and get clear, structured answers back.
Customer Journey
Daily conversion stats per journey, broken down by platform — iOS, Android, Web Push — and by journey state.
Chat & Contact Center
Aggregate and per-campaign chat metrics — sent, delivered, read, errors — plus daily, weekly and monthly contact-center reports.
Meta / WhatsApp pricing
Billable messages by category — authentication, marketing, utility — with cost time-series by hour or day.
Raw CSV / ZIP export
Non-aggregated data served as authenticated file downloads, so you can pull the underlying numbers straight into your own tools.
Read-only by design
The connector only reads statistics. It never sends campaigns or changes anything in your account — you keep operating inside indigitall.
Ask whatever you need
Real prompts, verified against the live connector.
Connect now
One click opens Claude with the connector pre-filled. Authentication happens on indigitall's side.
Add indigitall to Claude
Claude opens with the name and server URL already filled in. Review, authorize through indigitall, and you're connected.
mcp.eu1.indigitall.com and authorize.Manual setup
- In Claude, go to Settings → Connectors and click "+ Add custom connector."
- Set the Name to
indigitalland paste the remote MCP server URL below. - Leave the rest as default and click Add. Claude will walk you through indigitall's authorization to finish connecting.
https://mcp.eu1.indigitall.com/mcpEverything you're wondering
What data does it read?
Can it operate on my account?
How is authentication handled?
Which agents does it work with?
Who maintains it?
Built read-only, secured on our side
The connector adds a conversational layer — it never operates on your account.
Authentication on our side
You authorize through indigitall's own flow. No server keys are pasted into your AI client, and credentials never live in a chat.
Read-only access
The connector cannot place orders, send campaigns, or modify anything. It only reads the statistics you ask for.
Your data stays in your platform
Stats are served on request. The connector adds a conversational layer on top of indigitall — it doesn't move your data anywhere new.