> ## Documentation Index
> Fetch the complete documentation index at: https://help.kenekt.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Model Context Protocol (MCP)

> Connect an AI assistant such as Claude to your Kenekt portal, so your team can search stock, manage lists and holds, and export your library just by asking.

## What is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is an open standard for connecting AI assistants
to the tools and data people already use. Instead of every assistant needing its
own custom integration, a service offers one MCP server, and any assistant that
supports MCP can plug into it. Claude, ChatGPT, Cursor and a growing list of
other assistants support it.

## The Kenekt MCP

Kenekt MCP is the MCP server for your portal. Once someone on your team connects
their assistant to it, they can ask it to search your stock, build and share
lists, check deals and fees, and place holds. Staff can also manage and export
the construction library.

The assistant sees exactly what the person who connected sees in the portal,
priced through their own login.

## What you can do with Kenekt MCP

| Area | Example request |
| - | - |
| Search stock | "Find 4-bedroom house and land packages under \$750k in Logan." |
| Lists | "Put the best three in a list called Shortlist and give me share links." |
| Deals and fees | "Which of my deals still have fees owing?" |
| Holds | "Place a hold on lot 12 at Flagstone for my buyer." |
| Brochures and research | "Get me the brochure for the cheapest one, and the rental yield for that suburb." |
| Library (staff) | "Export our whole library into Google Sheets, one sheet per section." |
| Agent engagement (staff) | "Who hasn't logged in for 30 days?" or "What has Jane been looking at this week?" |

See the [prompt library](/help-guide/08-integrations/08-mcp/01-prompt-library) for
prompts you can copy, grouped by task, and [staff prompts](/help-guide/08-integrations/08-mcp/02-staff-prompts)
for managing stock, the construction library and your team.

| Who | What the assistant can do |
| - | - |
| Everyone | Search packages and check availability, open package details and brochures, create and share lists, review your deals, holds and fees, send enquiries, look up suburb research, and see what is new since a date |
| Everyone, if allowed at approval | Place and release holds on packages |
| Administrators and staff | Manage stock (projects, lots, packages and developments), the construction library (designs, facades, prices, inclusions and commission rates), user groups, and photos and documents, export the whole library, and read agent engagement (who is active, who has gone quiet, what an agent viewed and searched for, and when they signed in) |

Staff tools are only available on agencies that hold their own stock.

## Turn it on

Kenekt MCP is off until an administrator turns it on.

<Steps>
  <Step title="Open the Kenekt MCP connector">
    In the Kenekt app, open **Agency Settings**, then **Connectors**, then **Kenekt MCP**.
  </Step>

  <Step title="Enable the MCP server">
    Switch on **Enable the MCP server**. The page then shows your connector URL:
    your portal address followed by `/mcp`, for example
    `https://portal.yourcompany.com.au/mcp`.
  </Step>

  <Step title="Share the URL with your team">
    Anyone who can log in to your portal can connect with it. Staff find the URL
    under **Connectors** once it is on. Agents do not see the connector page, so
    send them the URL.
  </Step>
</Steps>

<Warning>
  Turning Kenekt MCP off disconnects everyone straight away. If you turn it back
  on, each person has to connect again.
</Warning>

## Connect your assistant

These steps use Claude. Other assistants that support MCP have a similar option
to add a custom connector or MCP server by URL.

<Steps>
  <Step title="Add a custom connector">
    In Claude, go to **Settings**, then **Connectors**, then **Add custom connector**.
  </Step>

  <Step title="Paste your connector URL">
    Paste the URL from the Kenekt MCP page and add it.
  </Step>

  <Step title="Log in and approve">
    Your portal opens. Log in as yourself, then approve the connection. The
    approval screen lists what the assistant will be allowed to do, and asks
    separately before allowing holds.
  </Step>
</Steps>

A connector added on claude.ai also appears in the Claude desktop and mobile apps,
so you only add it once. If you work with more than one supplier on Kenekt, add
each supplier's connector. Every answer names the supplier it came from.

## Export your library to Google Sheets

Staff can have their assistant copy the whole construction library into Google
Sheets. In Claude, connect the Google Drive connector as well as Kenekt, then ask:

> Using the Kenekt connector, export our whole library (designs, prices, facades
> and inclusions) into Google Sheets, one sheet per section, named "Kenekt
> Library - \<section>". Include every row, and tell me how many rows each
> sheet has so I can check nothing was missed.

<Tip>
  For a one-off copy you can skip the assistant: **Export Library** in the
  Construction Library downloads the same data as an Excel file that opens in
  Google Sheets. See [Exporting the library](/help-guide/05-construction-library#exporting-the-library).
</Tip>

## Staying in control

* **The assistant acts as you.** It can only see and do what your own login allows.
* **Confirm before anything changes.** In your assistant's connector settings,
  keep tools that change data or place holds on **ask every time**, so nothing
  happens without your confirmation. Staff should never auto-approve tools that
  delete.
* **Deletes are checked twice.** A permanent delete shows a preview first and
  only goes ahead after a second confirmation.
* **Promoted to staff?** Disconnect and reconnect the connector to pick up the
  staff tools.
* **Changing your portal address** breaks existing connections. Everyone needs to
  add the connector again with the new URL.
* **See what was done.** Administrators can review every request made through
  MCP under **Recent invocations** on the Kenekt MCP page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.