Kabeen MCP server

The Model Context Protocol (MCP) is an open standard that lets AI assistants and agents securely access external data and tools. The Kabeen MCP server exposes your information system map — applications, servers, data objects, teams, usage, costs — to any MCP-compatible client.

The server is hosted by Kabeen: there is nothing to install or to run on your infrastructure.

Server address

Head to Setting up a client for the configuration to use with Claude, Cursor, VS Code and the other supported clients.

Authentication

The server implements the authenticated remote MCP specification. Connecting a client opens a browser window where you sign in to Kabeen and authorize the client to act on your behalf.

The session inherits your own permissions: an assistant connected with your account sees exactly the workspace, applications and financial data your role gives you access to, and nothing more. Roles and permissions are described in the Roles and permissions guide.

You can revoke a client at any time from your Kabeen account settings — the assistant loses access immediately.

What the assistant can do

The server exposes tools grouped into the following families.

Explore the map

• List and search applications, servers, data objects and workstations
• Fetch the detail page of a resource and its relationships
• Display the organization tree and the associated responsibilities
• Read application flows and the links between components

Analyze usage and costs

• Measure the adoption of an application (active users, time of use, satisfaction)
• Get a usage overview across the whole portfolio
• Summarize annual costs by scope (team, category, criticality)
• Review contracts attached to an application

Assess health and risk

• Read the health score of an application and its user sentiment
• Track technology obsolescence across the portfolio
• Run an impact analysis before decommissioning or migrating an application
• Trigger a deep analysis on a scope

Maintain the repository

• Create an application, a server or a data object
• Update the metadata of an existing record
• Link an application to a server or to a data domain
• Assign or change the owners of a resource
• Add a comment to an application

Qualify discovered applications

• List the candidate applications surfaced by auto-discovery
• Search the Kabeen catalog to qualify a proposal
• Inspect unmatched FQDNs and tenant accounts

Communicate

• Create an announcement targeted at a population of users

Write operations go through the same validation rules as the interface, and every change is recorded in the audit history.

Typical use cases

Prepare a rationalization review. Ask the assistant to list redundant applications in a category, cross-reference their cost and adoption, and draft the decommissioning shortlist.

Document an application from a specification. Point the assistant at a project document and let it create the application, attach its servers and data objects, and set the owners.

Answer a security questionnaire. Have the assistant collect criticality, hosting, data classification and contract details for a set of applications.

Assess the impact of a migration. Ask for every application, flow and team affected by decommissioning a server before you commit to a date.

Keep the map fresh. Have the assistant go through the applications discovered last week and qualify each one against the Kabeen catalog.

Good practices

• Start read-only: ask questions before letting an assistant write to the repository.
• Review write operations. Assistants are good at drafting records, less at judging business context.
• Prefer a dedicated account for automated agents so that their actions are identifiable in the audit history.
• Remember that the assistant only sees your tenant: it never answers about applications, teams or costs that do not exist in your workspace.

What's next

An HTTP API covering the same scope is on the roadmap. Talk to your Kabeen contact if you need programmatic access before it ships.