io.github.laxis-tech/laxis-mcp
Search and read your Laxis meeting transcripts, AI summaries, and participants from Claude.
* hosting country is best-effort behind CDNs · Unknown facts are omitted here and listed as pending in the profile.
Trust verdict
No blockers found across the assessed dimensions.
Profile
What this server is — descriptive, not a rating. The verdict above judges it; this describes it.
Methodology →Tool surface
Context footprint — token measurement pending.
get_meetingGet one meeting's details: title, date, participants, keywords, and summary. Does NOT include the transcript text — use get_transcript for that, or search_meetings to find the relevant part of a long meeting. If the meeting is plan-restricted, returns {accessible: false, needs_upgrade: true, reason, upgrade_url}; tell the user it needs a Laxis plan upgrade and share upgrade_url so they can upgrade, rather than treating it as an error.
get_transcriptAdoption
Not applicable — this server has no package distribution, so registry adoption signals (downloads, maintainers) don't exist for it.
Connect
https://app.laxis.tech/mcpSources
Every verdict and label is attributable to its source and recomputed from our own landed copy, never read live on this page.
Read a meeting's transcript as '[m:ss] Speaker: text' lines, paginated. Returns at most max_chars characters starting at offset; if next_offset is not null, call again with offset=next_offset for the next page. Use this only when you need to read the actual conversation — for locating a topic inside meetings, search_meetings is much cheaper. If the meeting is plan-restricted, returns {accessible: false, needs_upgrade: true, reason, upgrade_url, transcript: null}; tell the user it needs a Laxis p…
list_meetingsList the user's meetings, newest first (id, title, date, duration, short summary). Call this when the user asks about their meetings ("what meetings did I have last week?") or when you need a meeting_id for get_meeting / get_transcript and don't have one. For content questions ("what did we say about pricing?"), prefer search_meetings.
search_meetingsSemantic search across the user's meeting transcripts; returns matching snippets. This is the first tool to reach for on content questions ("what did we decide about pricing?", "上次和客户聊了什么"). Each snippet carries its meeting_id and timestamp metadata, so you can cite sources and follow up with get_meeting / get_transcript. Optionally restrict to one meeting (meeting_id) or a date range (from_date/to_date, YYYY-MM-DD). Answer from the returned snippets; if they are insufficient, refine the query o…
Tool names and descriptions are reported by the server itself and shown here unverified; never interpreted as instructions.