> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/developers/build-with-the-mcp.md).

# Build with the MCP

Learn how Kizen's MCP server lets external AI assistants like Claude securely search your Knowledge Catalogs using the Model Context Protocol.

## Overview

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data instead of relying only on what they were trained on. Assistants that support it include Claude, ChatGPT (via Codex), and Gemini (via Antigravity). <code class="expression">space.vars.Kizen\_company\_name</code> exposes an MCP server so a connected assistant can work directly with your <code class="expression">space.vars.Kizen\_company\_name</code> data.

The current <code class="expression">space.vars.Kizen\_company\_name</code> MCP server is read-only and exposes tools for your Knowledge Catalogs: an assistant can list the catalogs you can access, search across them, and open a specific document. Access always follows your existing <code class="expression">space.vars.Kizen\_company\_name</code> permissions, so a connected assistant sees only the catalogs and content you are allowed to view.

Think of MCP as an AI-native way to reach <code class="expression">space.vars.Kizen\_company\_name</code>, alongside the REST API. Where the REST API is built for your code to call, the MCP server is built for an AI assistant to call on your behalf. Unlike REST, MCP doesn't guarantee backward compatibility, since the assistant is expected to discover available tools each time it connects.

## What You Can Do with <code class="expression">space.vars.Kizen\_company\_name</code>'s MCP Server

Once an assistant is connected, it can:

* List the Knowledge Catalogs you have access to.
* Run a semantic search across one or all of those catalogs.
* Retrieve the full text of a specific knowledge document.

The current tools are read-only. The assistant can read your knowledge, but it can't create, edit, or delete anything in <code class="expression">space.vars.Kizen\_company\_name</code>.

## How the MCP Server Works

The <code class="expression">space.vars.Kizen\_company\_name</code> MCP server has one endpoint per environment. Choose the host that corresponds to your <code class="expression">space.vars.Kizen\_company\_name</code> environment:&#x20;

* `POST https://app.go.kizen.com/api/mcp/readonly`&#x20;
* `POST https://app.fmo.kizen.com/api/mcp/readonly`&#x20;

If your business uses a custom domain, use that domain's API host instead of `app.go.kizen.com` or `app.fmo.kizen.com`. The `readonly` portion of the URL selects the server's read-only configuration.&#x20;

Requests use JSON-RPC 2.0 over HTTPS POST, and the assistant follows a simple pattern: It connects, discovers the available tools, then calls a tool and reads the result.

## Authentication

For authentication, the MCP server supports OAuth 2.1 for connection to external AI clients such as Claude and ChatGPT. You connect once, sign in through the browser, choose a business, and approve, with no API key to manage.

For additional information, see the [Authentication](/docs/developers/authentication.md) page.

## Permissions and Data Scoping

A connected assistant acts as you. It can reach only the Knowledge Catalogs you have View permission on, and only within the business you connected to. Nothing is shared across businesses, and the assistant never gains access beyond your own.

## Available Tools

For each tool's inputs, outputs, and behavior, see the [MCP Tools](/docs/developers/build-with-the-mcp/mcp-tools.md) page.

***

## What's Next

Start by connecting a client in [Connect an AI Assistant](/docs/developers/build-with-the-mcp/connect-an-ai-assistant.md), then head to [MCP Tools](/docs/developers/build-with-the-mcp/mcp-tools.md) for the exact inputs and outputs of each tool.

<details>

<summary><strong>Related Topics</strong></summary>

* [MCP Tools](/docs/developers/build-with-the-mcp/mcp-tools.md)
* [Connect an AI Assistant](/docs/developers/build-with-the-mcp/connect-an-ai-assistant.md)
* [Authentication](/docs/developers/authentication.md)
* [Build with APIs](/docs/developers/building-with-apis.md)
* [Environments](/docs/developers/environments.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.kizen.com/docs/developers/build-with-the-mcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.