Laxis MCP Server

Search and read your Laxis meeting transcripts, AI summaries, and participants from Claude. Exposed over MCP by the laxis mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Laxis is the next-generation AI meeting note taker and voice dictation tool built for professionals. It records, transcribes, and summarizes any conversation directly from your computer — no "bot" ever joins the call — and works seamlessly with Zoom, Google Meet, Microsoft Teams, Webex, Slack Huddles, and more.

Its toolset

Everything the assistant can do here goes through one of these:

• list_meetings — Browse your recent meetings — title, date, duration, status, and a short summary (metadata only)
• search_meetings — Semantic search across your transcripts; returns the most relevant transcript snippets
• get_meeting — Full details for one meeting — participants, AI summary points, and metadata
• get_transcript — The full, paged transcript text, formatted as [m:ss] Speaker: text
• Cursor — The one-click button adds the server; open Cursor → Settings → MCP and click Sign in (or Needs login) next to Laxis to authorize. Or
• Windsurf — Add to ~/.codeium/windsurf/mcp_config.json, then authorize when prompted:

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Laxis's toolset — list_meetings, search_meetings, get_meeting and 3 more — is a fair guide to whether it matches your workflow. It is maintained by laxis-tech; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Laxis's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the laxis mcp server does with a few real requests.