MCP
MCP (Model Context Protocol) is a standard way for AI assistants to use tools. Genie works with MCP in two directions. As an MCP server, Genie lets assistants such as Claude Desktop, Claude Code, Cursor or VS Code search your knowledge bases and ask Genie questions. As an MCP client, Genie lets its own agents call tools from other systems you connect, with an approval step where you want one.
Genie as an MCP server
Each workspace can publish one or more MCP endpoints. Each endpoint has its own address, token, knowledge bases and tools, so you can give each team or assistant only what it needs: for example, a read-only endpoint on Human resources for the HR team's assistants, and a separate endpoint with write tools for the people who maintain the documents.
Create an endpoint
You need the Admin or Owner role.
- Open Settings → MCP server (in the Publish & integrations group).
- Click New endpoint.
- Basics: enter a Name, for example
HR documents, and optionally a Description. Keep Enabled on. - Knowledge-base scope: under Accessible knowledge bases, choose the knowledge bases the endpoint may use. Leave it empty for every knowledge base in the workspace.
- Exposed tools: tick the tools the assistant may call (see the table below). Read-only tools are ticked for you; write tools are not.
- Ask settings: choose the Default agent that answers the
asktool. Leave it empty to use the built-in quick answer. - Rate limit: set Max calls per minute for the endpoint (default 60).
- Click New endpoint. The Endpoint ready, save the token window shows the Token, the Endpoint URL and ready-made Client configuration.
- Copy the token now and store it safely: Genie shows it only once. Then click Finish.
website-docs/public/screenshots/en/mcp-server.png| Tool group | Tools | What the assistant can do |
|---|---|---|
| Retrieval & reading | list_knowledge_bases, search_knowledge, grep_chunks, list_documents, read_document | List knowledge bases and documents, search passages by meaning or by exact words, and read a document |
| Question answering | ask | Get a cited answer from the endpoint's default agent, and ask follow-up questions in the same conversation |
| Wiki | wiki_search, wiki_read_page, wiki_index | Search and read the wiki of knowledge bases that have one |
| Writes (enable with care) | add_document, update_document, delete_document | Add a document from Markdown text or a web address, change it, or delete it for good |
Connect an assistant
Use the Endpoint URL and the token in the assistant's MCP settings. The endpoint URL looks like https://genie.contoso.test/mcp/<endpoint ID>. Replace <YOUR_TOKEN> with your token.
For Cursor, VS Code, Claude Desktop and other assistants that support Streamable HTTP, add this to their mcpServers configuration:
{
"mcpServers": {
"genie-hr-documents": {
"url": "https://genie.contoso.test/mcp/6c0e2a4b-91f3-4d7a-b5e8-3f1d2c9a7e40",
"headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
}
}
}For Claude Code, run one command in the terminal:
claude mcp add --transport http genie-hr-documents https://genie.contoso.test/mcp/6c0e2a4b-91f3-4d7a-b5e8-3f1d2c9a7e40 --header "Authorization: Bearer <YOUR_TOKEN>"For assistants that only support local (stdio) servers, bridge through mcp-remote. This needs Node.js on the user's computer:
{
"mcpServers": {
"genie-hr-documents": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://genie.contoso.test/mcp/6c0e2a4b-91f3-4d7a-b5e8-3f1d2c9a7e40", "--header", "Authorization: Bearer <YOUR_TOKEN>"]
}
}
}To check the connection, ask the assistant to list the Genie knowledge bases it can see.
Manage an endpoint
Open the endpoint's menu in the list:
- Connection info shows the endpoint URL and the client configuration again, without the token.
- Disable and Enable turn the endpoint off and on.
- Rotate token issues a new token. The old one stops working at once, so update every assistant that uses it.
Deleting an endpoint disconnects its assistants immediately.
What an assistant can see
- Only the knowledge bases in the endpoint's scope, and only their unrestricted documents. Documents with document permissions never appear.
- Only the ticked tools. A tool that is not ticked is refused even if the assistant calls it by name.
askalways runs the endpoint's default agent; the assistant cannot choose another one. It does not search the web, query Databases or Power BI, or run code.- Calls above Max calls per minute get a rate-limit error.
Connect MCP tools to agents
An MCP service is a tool server from another system, for example your ticketing or CRM system, that Genie's agents may call while they answer. You need the Admin or Owner role.
Add an MCP service
- In the sidebar, open Toolbox, then the MCP Service tab.
- Click Add Service.
- Connection: enter the Service Name and the Service URL, choose the Transport Type (SSE or HTTP Streamable), and under Authentication choose the Auth Method:
- None / Custom Header: no sign-in, or a fixed header you add;
- API Key / Token: a key or token that the service gave you;
- OAuth 2.0 (authorize on first connect): each person signs in to the service with their own account the first time an agent uses it.
- Click Save and continue. Genie connects to the service and lists its tools.
- Tools and usage: for each tool, switch Enabled off for tools agents must never call, and switch Require approval on for tools that change data or send something out.
- Under Usage instructions, describe what the service is for and when to use it, or click Generate with AI and review the text. Agents read these instructions to decide when to use the service.
- Click Save.
The MCP service must be reachable from Genie over the network. Genie connects over SSE or Streamable HTTP only; local (stdio) MCP servers are not supported. If the service runs on your internal network, ask your Genie provider how Genie can reach it.
Give an agent the service
- Open the agent in the agent editor. MCP services are available to agents that use tools.
- Go to MCP Services and choose All (every MCP service of the workspace) or Selected, then pick the services under Select MCP Services.
- Save the agent.
Approve a tool call
When an agent wants to call a tool that has Require approval on, the answer pauses and the chat shows a review card with the service, the tool and the Arguments. The person who asked:
- checks the arguments, and can edit them;
- clicks Approve & run to run the tool, or Reject to refuse it.
If nobody decides before the countdown on the card ends, the call is cancelled and the agent continues without it. For an OAuth service the card shows Authorize the first time instead: the person signs in to the service in a new window, and the call resumes.
Good to know
- Endpoint tokens give access to your documents. Give each assistant or team its own endpoint, and rotate the token if it leaks.
- Turn on write tools only for endpoints used by people who are allowed to change the documents.
delete_documentdeletes for good. - An MCP endpoint does not act as a person: it sees the same documents for everyone who uses it.
- Switching a tool's Enabled off is stronger than requiring approval: agents do not see that tool at all.
- Questions asked through MCP count toward the workspace's monthly budget, if your workspace has one.