Integration overview
This section is for the IT staff who connect Genie to the company's other tools: your own applications through the API, your intranet through the website widget, and AI assistants through MCP. Your Genie provider runs Genie for you, so there is no server to install and nothing to configure on a machine: you set everything up in Genie's Settings and in the tool you connect.
Choose a way to connect
| You want to | Use | Who sets it up | Page |
|---|---|---|---|
| Call Genie from your own application or script | The API, with an API key | A workspace Owner creates the key | API keys and the API |
| Put a Genie chat window on an intranet page | The website widget | A workspace Admin | Website widget |
| Let Claude, Cursor or another AI assistant search your knowledge bases | Genie as an MCP server | A workspace Admin | MCP |
| Let Genie's agents use tools from another system | MCP services | A workspace Admin | MCP |
Microsoft Teams and Zalo are set up by your workspace admins; see Teams, Zalo and the website widget.
Find the integration settings
- In Genie, open Settings.
- In the Publish & integrations group, choose API, Website widget or MCP server.
These pages are for the workspace's Admins and Owners; other members do not see the group. Only an Owner sees API.
Your Genie address
The examples in this section use the Contoso demo company: Genie runs at https://genie.contoso.test and the intranet at https://intranet.contoso.test. Replace them with your own addresses. Your Genie address is the one your users open in the browser.
- The API is under
/api/v1, for examplehttps://genie.contoso.test/api/v1. - MCP endpoints are under
/mcp/, for examplehttps://genie.contoso.test/mcp/<endpoint ID>. - The widget script is
https://genie.contoso.test/genie-widget.js.
What a connected tool can see
An API key, a website widget visitor and an MCP client do not act as a person. Genie treats them as guests of the workspace:
- They see unrestricted documents only. A document that has document permissions is never searched, quoted or cited for them.
- They reach only the knowledge bases you allow: the key's knowledge bases, the widget's agent, or the MCP endpoint's scope.
- They cannot query Databases or Power BI, and Genie does not run code for them.
Good to know
- API keys, widget channel keys and MCP tokens give access to your company's documents. Store them like passwords, give each application its own, and delete one as soon as it is no longer used.
- Questions asked through the API, the widget and MCP count toward the workspace's monthly budget, if your workspace has one.
- Conversations started through an API key are visible in Genie only to that application, not to the workspace's admins. Website widget conversations can be read by the workspace's Admins and Owners (see Who reads channel conversations).
- If your company only allows certain networks, API keys and MCP endpoints are held to the list when a system administrator ticked API keys and MCP endpoints on the platform list, and API keys also when Also apply to API keys used in this workspace is on for the workspace (see Network and antivirus). Call Genie from an allowed network.
- The complete API and endpoint reference is not on this site. Ask your Genie provider for it.