Connect an MCP client

TKP exposes an MCP server at:

{APP_URL}/mcp

Any MCP-compatible agent (a coding assistant, a chat client, a LangGraph agent, your own application) can connect to it and get tools for searching, reading, and citing your libraries. Every request against /mcp is authenticated and scoped exactly like a REST API request: through a credential that carries its own interfaces and abilities (the credential must include the mcp interface), resolved to one tenant, one set of library permissions.

There are two ways to authenticate:

• API key: create a Personal Access Token in the admin panel and give it to your client as a static bearer token. Simplest to set up; works with any client that can send a custom header.
• OAuth: the client discovers TKP's OAuth server automatically and registers itself, then a browser sign-in authorizes it. No token to copy around, and access shows up as a Connected App you can review or revoke without touching your agent's configuration. Preferred if your client supports it.

Once connected, see Example clients for configuration snippets for specific tools.