Kitemesh Documentation

English

Francais

English

Francais

Appearance

MCP ​

What MCP is for ​

MCP connects external Model Context Protocol servers so their tools can be made available to agents. It is useful when a team already has MCP-compatible tools and wants to reuse them in Kitemesh.

MCP tools are discovered from a connection, then enabled, scoped, and reviewed before they are used in chat.

Add a connection ​

  1. Open Configuration.
  2. Select the MCP tab.
  3. Click Add MCP.
  4. Choose a Connector.
  5. Fill in Name, Description, and MCP server URL.
  6. Select Authentication: No auth, Bearer token, or Basic.
  7. Select vault secrets when authentication needs credentials.
  8. Choose the Shared with scopes.
  9. Save the connection.

After saving, use Test to check the connection, then Discover to load the tools exposed by the server.

Managed connectors ​

Some connectors can be managed from the Managed connectors area. When Connect is available, Kitemesh starts the provider connection flow and returns to the MCP tab after the account is connected.

Items marked Soon are visible for orientation but cannot be connected yet.

Connection statuses ​

The connection list can show these statuses:

  • Draft
  • Testing
  • Active
  • Degraded
  • Disabled
  • Needs review

If a connection is Degraded or Needs review, test it again and rediscover tools before relying on it in a chat.

Review discovered tools ​

After discovery, each tool can be reviewed from Discovered tools.

For each tool, you can set:

  • Risk: Read, Write, Delete, or Unknown
  • Validation: whether user approval is required before execution
  • Enabled: whether the tool is available

Keep validation enabled for tools that write data, delete data, or affect a sensitive system.

Use MCP tools in chat ​

When an MCP tool is enabled and shared with the selected group or model, it can appear in chat. From Chat settings, use Exclude MCP tools to keep a specific conversation from using tools that are not relevant.

What to verify ​

  • An active team is selected.
  • The connection is enabled and has the expected sharing scopes.
  • The required vault secrets exist and are current.
  • Test succeeds after changes.
  • Discover has been run after the server changed.
  • Each tool has the right risk label and validation setting.