Claude Desktop

Claude Desktop can connect to TKP through a remote connector. Use the address of your TKP application, such as https://tkp.example.com, wherever the examples show {APP_URL}.

Connect with browser sign-in

In Claude Desktop's connector settings, add a custom remote connector with this URL:

{APP_URL}/mcp

Complete the OAuth sign-in in your browser and authorize read access to a library. Return to Claude Desktop, enable the connector for your conversation and ask it to list your TKP libraries. The connector controls and availability depend on your Claude account and organization policy.

Connect with a token through a bridge

If you need to use a Personal Access Token instead, the following configuration uses the community mcp-remote bridge. It runs locally and forwards Claude Desktop's MCP requests to TKP over HTTP, attaching the token.

This method requires Node.js with npx. Open Claude Desktop's local MCP configuration, claude_desktop_config.json, and add the following server entry. Merge it into an existing mcpServers object rather than replacing your other servers. Replace {APP_URL} and <token> before saving.

{
  "mcpServers": {
    "tkp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "{APP_URL}/mcp",
        "--header",
        "Authorization: Bearer <token>"
      ]
    }
  }
}

Restart Claude Desktop after editing the file. Confirm that TKP's tools are available, then ask it to list your libraries. Keep this configuration private because it contains your token. The bridge is third-party software; consult its mcp-remote documentation before using it in an environment with restricted dependencies.