Fishbowl MCP
ILC MCP connects an AI client — Claude, ChatGPT, and others — to your live Fishbowl database. An operator asks for what they want in plain language; ILC MCP reads Fishbowl, proposes the exact change, and writes it only after a person approves. An administrator controls who can connect and what they can do from a web admin console.
This section has two guides:
- User guide — for operators. Connect an AI client, ask for work, and approve the changes.
- Administrator guide — for administrators. Grant and revoke access, set the plan and allowances, and review activity.
Terminology
Section titled “Terminology”| Term | Meaning |
|---|---|
| ILC MCP | ILC’s service that connects an AI client to your Fishbowl. |
| Custom connector | The entry you add in your AI client that points at ILC MCP. |
| MCP server URL | The address ILC sends you to paste into the custom connector. |
| Admin console | The web app at /app where an administrator manages ILC MCP. |
| Operator | A person doing daily Fishbowl work through an AI client. |
| Administrator | A person who grants access and configures ILC MCP. |
| Connection | A single AI client granted access for one Fishbowl user. |
| Change set | A batch of proposed writes that an operator approves before it runs. |
Read-only and read-write
Section titled “Read-only and read-write”ILC MCP comes in a read-only tier and a read-write tier. Read-only grants
sql:read and docs:read — read your Fishbowl data, and read prior-session
notes plus search Fishbowl’s help. Nothing can write. The read-write tier adds
the ability to change Fishbowl data, always behind an approval step.
How writes stay safe
Section titled “How writes stay safe”Reads happen freely so ILC MCP can check the situation. Every write is proposed, then approved — nothing changes in Fishbowl until a person signs in and approves the change set. The limits that back this up are in the Administrator guide.
Runs inside Fishbowl alongside ILC’s CloudPages. Questions or a demo: see ILC MCP for Fishbowl.