Run your Gydr account from your AI assistant
Console MCP lets you manage knowledge bases, Skills, widgets and data forms, and read conversations, by talking to Claude, Codex or another assistant that supports MCP. You sign in with your usual Gydr login, and the assistant can only do what your role allows.
This is for the people who run the account. It is separate from the MCP connector Plugin, which lets your chatbot call someone else's MCP server.
Add our new Sunday opening hours to the Shah Alam outlet.
Done. I updated the Shah Alam location in Bloom & Twig. Sunday now reads 10 am to 6 pm.
What it can do
The everyday Console jobs, by conversation
Ask in plain words. Each request is carried out through the same Console rules and permissions you already have.
Keep knowledge current
Look up, add, edit and remove products, FAQs, locations and documents, start a sync, or crawl a website.
Shape the chatbot
Create and edit Skills, edit a widget's draft, and publish it when you are ready.
Review conversations
List and search conversations, read messages and see analytics. Conversations are read only.
Manage data forms
Create, edit and delete the form definitions your chatbot asks in the chat.
How it works
Connect once, then just ask
Three steps, and nothing to install.
Add the server
In your assistant, add Gydr's Console MCP address as a custom connector or MCP server.
Sign in and choose an account
Sign in with your Gydr login, review who is asking, and choose which account the assistant works in.
Ask in plain words
Say what you want done. Changes name the account they were made in, and you can disconnect any time from Settings.
Safe by design
Your assistant gets no more power than you have
Console MCP is built so that a mistaken or manipulated assistant cannot reach further than you could.
Same permissions as the Console
A Viewer stays read only. Someone removed from the team is refused at the very next request.
Changes name their account
Every change must say which account it is for, and a mismatch is refused. Nothing switches accounts on its own.
Secrets and exports stay out
API keys, webhooks, team management, exports and deleting a whole knowledge base or widget are not available through it.
Pay with credits, for what you use
Each tool call uses credits from the account it runs in, on its own usage line: from 2 credits for a read and 3 for a change; large or slow requests use more. The app's other requests (starting a session, listing its tools, renewing its sign-in) use from 1 credit each, and connecting an app uses a few credits, once. Failed calls caused by Gydr are free.
Console MCP is on its way
It is built and being prepared for release. Until then, explore the Console and the rest of Gydr.
Console MCP will be part of the Growth plan and above.