On this page
Console MCP#
Console MCP lets you run your Gydr account from an AI assistant that supports the Model Context Protocol (MCP): Claude Desktop, claude.ai, Claude Code, Codex and other clients. You ask in plain words, and the assistant manages knowledge bases, Skills, widgets and data forms, and reads conversations, through the same Console checks you already work under.
It is available on the Growth plan and above. Every request runs as the person who connected it, with exactly the permissions their role (or custom permission set) gives them in the account they are working in.
Not the MCP connector Plugin
Connecting an assistant#
Every client needs the same address. You do not create or paste a key: the client signs you in through your normal Gydr login.
https://mcp.console.gydr.ai/mcp- Claude Desktop and claude.ai. Open Settings, then Connectors, choose Add custom connector, and paste the address.
- Claude Code. Run:
claude mcp add --transport http gydr-console https://mcp.console.gydr.ai/mcp- Codex and other clients. Add a remote MCP server (the streamable HTTP kind) with the same address. The client opens your browser to sign in.
The client registers itself automatically. A client whose sign-in returns to a custom app address (for example one that starts with cursor://) cannot connect yet: Console MCP only accepts https addresses and addresses on the same computer (localhost).
Signing in and choosing an account#
When the client first connects, a Gydr page opens in your browser. You sign in with your Gydr login, then see a consent page that names the app asking, the address it will return to, and your email. If you belong to several accounts, choose the one the assistant should work in. Accounts whose plan does not include Console MCP are shown but cannot be chosen. Choose Allow to connect, or Deny to refuse.
If none of your accounts is on the Growth plan or above, you see a refusal instead of a picker.
Switching accounts#
A connection works in one account at a time. The assistant can tell you which with whoami, list your accounts with list_accounts, and move with switch_account. Switching affects only your Console MCP connections. It never changes the account your open Console tab is using.
accountId, and it must be the account the connection is working in. A mismatch is refused, naming both accounts, and nothing changes. The assistant never switches on its own to make a call succeed. Every result begins with the name of the account it ran in.What the assistant can do#
- Area
- Account
- Tools
whoami,list_accounts,switch_account
- Area
- Knowledge bases
- Tools
- List, get, create and update a knowledge base; start a sync; products, FAQs and locations (list, create, update, delete, turn on or off in bulk); documents (list, list chunks, process, delete)
- Area
- Website crawler
- Tools
- Discover pages, start, list, get and cancel a crawl
- Area
- Skills
- Tools
- List, get, create, update, clone and delete
- Area
- Widgets
- Tools
- List and get, list and read saves, edit a save (draft), publish, and turn a widget on or off
- Area
- Data forms
- Tools
- List, get, create, update and delete form definitions
- Area
- Conversations
- Tools
- List, search, get, read messages and analytics (read only)
- Area
- Integrations, plugins and channels
- Tools
- List and get, with secrets redacted, plus a link to finish setup in the Console
| Area | Tools |
|---|---|
| Account | whoami, list_accounts, switch_account |
| Knowledge bases | List, get, create and update a knowledge base; start a sync; products, FAQs and locations (list, create, update, delete, turn on or off in bulk); documents (list, list chunks, process, delete) |
| Website crawler | Discover pages, start, list, get and cancel a crawl |
| Skills | List, get, create, update, clone and delete |
| Widgets | List and get, list and read saves, edit a save (draft), publish, and turn a widget on or off |
| Data forms | List, get, create, update and delete form definitions |
| Conversations | List, search, get, read messages and analytics (read only) |
| Integrations, plugins and channels | List and get, with secrets redacted, plus a link to finish setup in the Console |
Widget edits go into a draft save and reach visitors only after the assistant publishes it. Knowledge edits reach the chatbot after a sync. Tools the signed-in person's role does not allow are hidden from the assistant, and the Console still refuses anything not permitted.
What is deliberately left out#
Some things are done in the Console only, on purpose.
- Secrets and exit routes. API keys, webhooks, sign-in sources and integration keys. A webhook is also a way to send data out, so a session that reads visitor text must not be able to create one.
- People. Team members and ownership transfer.
- Exports. Data-form rows, transcripts and topics hold visitors' personal data.
- Deleting a whole knowledge base or widget.
- Creating or editing integrations, plugins and channels. They involve secrets and browser sign-in steps. The assistant can read them and gives you a link to the right Console page.
- File uploads.
Credits#
Each tool call uses credits from the account it runs in: from 2 credits for a read and 3 for a change; large or slow requests use more. They appear on their own Console MCP line in your usage. Failed calls caused by Gydr are free, and so is a call refused for the account's plan or credits: it is refused before anything is sent when the account does not have enough credits or its payment is overdue. A call the Console turns down because of what was asked (a field it does not accept, a permission the person does not have) uses the minimum for its kind. Work the Console already bills, such as a sync, a crawl or document processing, is billed on its own line exactly as it is in the Console.
The app's other requests on the connection, such as starting a session, listing its tools or renewing its sign-in, use from 1 credit each, on the same line. Connecting an app uses a few credits from the account you choose, once, when you select Allow; the consent page shows the exact number, and an account that cannot cover it is told so before anything is connected.
Disconnecting an app#
Open Settings, then Connected apps. Each row shows the app, where it returns to, when you connected it and when it was last used. Choose Revoke to disconnect it at once: the app can no longer act, and connecting again asks you to sign in and consent again. Each person sees and revokes only their own connections. Resetting your password, or being removed from the team, also stops a connection.
Security notes#
- Conversation text is untrusted. Messages are written by your website visitors. Conversation tools return them inside a labelled “visitor-written content” envelope, and the assistant is told to treat it as data to read, never as instructions.
- Your assistant never holds your Console login. It holds only a Console MCP token that works at the Console MCP address and nowhere else.
- Changes are audited. Requests made through Console MCP are recorded in the audit log with the name of the app that made them.
- Review before you approve. Check the app name and the address it returns to on the consent page. Connect only apps you trust.