MCP connectors link GENI to tools that have no dedicated dGENIX connection, through the Model Context Protocol: an open standard by which external services expose their capabilities.
The practical consequence: a dGENIX connection no longer has to be built for every tool separately. If a service offers an MCP server, it can be plugged in as a connector. For you such a connector works exactly like any other: activate it, connect your account, done.
What you can do with it
What an MCP connector can do is decided by the service itself. In practice it comes down to the same kinds of actions as our own connections: look something up, create something, update something. Every connector shows in the dashboard which actions it brings.
The point is not that MCP does something other connections cannot, but that adding a tool goes much faster.
Activating
- Go to Dashboard -> Skills and find the connector
- Click Activate; it appears as a regular skill toggle
- Follow the step-by-step instruction that appears right after activation
- Connect your own account via Dashboard -> Connectors, if the connector asks for it
- Ask GENI to do something with it
Every MCP connector has its own instruction in the dashboard, just like Gmail or WhatsApp. You do not need to do anything technical or run a server.
Ways of connecting
| Method | How it goes | Comparable to |
|---|---|---|
| Signing in | You log in to the service and grant permission | Slack, Notion |
| Pasting a key | You paste a key from your own account | Stripe, HubSpot |
| No connection | Activating is enough, no account needed | , |
Which one applies is shown in the connector's own instruction.
What access you give
An MCP connector works on your own account at that service by default. That has three consequences worth knowing:
- You keep control over the account and the data in it
- If the service charges, those costs run through your account and not through dGENIX
- You can disconnect any time, after which GENI immediately loses access
What a connector is allowed to do is decided by the service at connection time. If you log in at the service, you see its consent screen listing the permissions requested , read that, because the real answer is there. If you paste a key, whatever that key allows applies; create one with as few rights as possible.
Whatever is requested: actions that change or delete something always ask for your confirmation at dGENIX first.
Checking that it works
After connecting, ask GENI to read something rather than create something:
What can you do with [connector name]?
I have access to [connector] and can currently run 4 actions there: search, open an item, create an item and update an item. Shall I look something up for you?
If you get that list, the connection stands and you immediately know which actions you have. If GENI says it has no access, check under Dashboard -> Connectors whether the connector shows as Connected.
Disconnecting
Go to Dashboard -> Connectors, find the connector and click Disconnect. Access ends immediately and GENI can no longer do anything with it.
Two things to know:
- The skill stays activated. To remove it entirely, switch it off in the marketplace too.
- What the connector created earlier stays put. Disconnecting pulls nothing back out of the service; you clear that up there.
You can also revoke the permission at the service itself. If you do, the connector stops without warning , disconnecting inside dGENIX keeps the overview cleaner.
What it costs
MCP connectors use the same credit system as all other skills: a fixed price per action, visible before it runs. More expensive actions ask for confirmation first, so there are no surprises. See The credit system.
MCP connectors sit in Growth and up.
Limits
- A connector can only do what the service itself exposes through MCP
- If the service is down, the connector is down; dGENIX cannot work around that
- Actions that change or delete something always ask for confirmation
- We decide which connectors are available; you cannot add your own
- The range grows gradually, so your tool may not be there yet
Troubleshooting
The connector is not in the marketplace. Then it is not available yet. You can request it through the skill marketplace.
Activating works, but nothing happens. The connector probably still needs a connection. Check Dashboard -> Connectors to see whether it shows as Connected.
You do not know which actions it supports. Open the connector in the dashboard; the instruction states exactly what it can do.
Frequently asked questions
What is MCP, really? An open standard by which a service exposes its capabilities to AI assistants in a uniform way. Because it is a standard, not every connection has to be hand-built from scratch.
Does it feel different from a regular connection? No. In the dashboard, in chat and in credit accounting it works identically.
Can I plug in my own MCP server? Not at the moment. The range is curated by us, so every connector comes with a tested instruction and a fixed credit price.
Back to Connectors Next: Skills explained · The credit system On the site: all integrations
dGENIX Docs, MCP connectors, updated August 2026