LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Kapa Customer Subdomains

The customer side of Kapa — your own subdomain, your own tool names, and an auth method you pick once and cannot change.

by Kapa ↗Framework & SDK Documentation Lookup✓ Official

LABSCO SUMMARY

The auth choice is permanent, and the full-document tool is off by default — both worth reading twice before you create the server.

Most configuration decisions can be revisited; this one cannot, so a server created with public OAuth for convenience stays that way. The documents tool being disabled by default is the more interesting default: retrieval returns passages, and handing over whole documents is an extra decision rather than an assumption. Customisable tool names and source-group scoping mean one Kapa project can front several differently-scoped servers.

What it is

Kapa's per-customer servers, each on its own subdomain. You create the integration, choose the subdomain and the authentication method, and customise what the tools are called and which source groups they cover.

What you get

  • search_<product>_knowledge_sources — agentic retrieval returning passages with source URLs
  • get_<product>_knowledge_documents — full documents by URL; off by default and enabled deliberately
  • give_feedback
  • Tool names, descriptions and the source groups they cover are all configurable

Requirements

A Kapa project. The authentication method is set when the server is created and cannot be changed afterwards — choose it deliberately.

Setup effort

Get your endpoint, then paste it — add your endpoint to your client and sign in or add a key, whichever the server was set up with

See installation options