LABSCO SUMMARY
There is a working OAuth path here that the documentation does not tell you about.
The documented route is a personal access token pasted into a config. The endpoint also advertises full dynamic client registration, which means a compliant client can authorise itself with nothing to paste — better security, undocumented. Worth trying before falling back to a static token. Undocumented behaviour can change without notice, so treat it as a convenience rather than something to build on.
What it is
Kolva's endpoint over their meeting and document workspace. Their documentation describes five capability areas in prose without naming tools.
What you get
One semantic search across meeting transcripts, notes, tasks and uploaded documents; quick capture, where a note you dictate is saved in Kolva; meeting summaries, decisions and action items; tasks and projects created, completed and re-planned; and a morning briefing — a single call that summarises the day ahead.
Requirements
A personal access token as a bearer header, per their documentation. The server also supports a full OAuth 2.0 flow with PKCE and dynamic client registration, which their docs do not mention.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Finding what was discussed
Search transcripts, notes and documents together rather than separately.
02
Connecting without a static token
The endpoint supports dynamic client registration even though the docs only mention a token.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- A Kolva personal access token (Authorization: Bearer), or an OAuth 2.0 sign-in
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://kolva.io/mcpRequirements
- Authorization: Bearer <YOUR_PERSONAL_ACCESS_TOKEN>; an OAuth 2.0 sign-in also works
