Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Laxis

by laxis-techversion 0.1.0i★ –iRuns in the cloud
Registry nameio.github.laxis-tech/laxis-mcp

Install

Overview

Description from the maker (original English)

Search and read your Laxis meeting transcripts, AI summaries, and participants from Claude.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http laxis https://app.laxis.tech/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "laxis": {
      "url": "https://app.laxis.tech/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "laxis": {
      "type": "http",
      "url": "https://app.laxis.tech/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret required HTTP header
    Laxis personal API key as a Bearer token (e.g. 'Bearer laxis_...'). Generate one at app.laxis.tech -> Settings -> Claude (MCP).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account laxis-tech, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7257 servers in this category
  • Published to the registry more recently than 23% of the other 7257 servers in this category
  • Basic checks equal to or better than 100% of the other 7257 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Laxis safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Laxis MCP Server

The Laxis MCP Server connects Laxis — the AI meeting note taker and voice dictation tool for professionals — to Claude and other AI tools through the Model Context Protocol. Your assistant can search and read your meeting transcripts, summaries, and participants directly in chat — turning every conversation you've recorded into context your AI can reason over.

Remote, hosted server — nothing to install or run. Laxis hosts the server

for you. You add one URL to your AI client and **sign in with your Laxis

account** — no local binary, Docker image, or npm package, and no API key to

copy or paste.

What is Laxis?

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.

  • 🎥 Botless meeting recording & transcription — record and instantly transcribe any meeting straight from your computer for a private, professional, and seamless experience. High-accuracy AI handles multiple speakers and technical jargon with ease.
  • 🎙️ AI dictation — voice to text, anywhere — speak instead of type. Laxis turns your voice into clean, perfectly formatted text up to 3× faster than typing, automatically removing filler words ("um," "uh") and adding punctuation. Perfect for drafting emails, notes, and messages by voice.
  • 🌐 Real-time translation — Laxis transcribes and translates conversations live, so you can follow and capture cross-language discussions as they happen.
  • ✍️ Personalized AI summaries — don't just get a transcript. Laxis combines your own real-time notes with the meeting transcript to generate insights that reflect your specific context and priorities.
  • 📊 50+ professional report templates — turn hours of conversation into structured documentation in seconds, including Sales Discovery, Project Updates, User Interviews, and Candidate Screenings.
  • ✅ Automated action items — Laxis automatically identifies and extracts tasks, ensuring nothing falls through the cracks.
  • 💬 Real-time AI copilot — chat with Laxis before, during, and after meetings to get real-time insight.
  • 🔄 Seamless CRM & tool integration — automatically sync meeting insights, action items, and customer data directly into Salesforce, HubSpot, Jira, Slack, and your favorite productivity tools.
  • 🔒 Enterprise-grade security — your data is encrypted and private, protected to the highest industry standards.

Sales teams use Laxis to update their CRM instantly and never miss a customer requirement; product managers turn user interviews into actionable PRDs; consultants deliver standardized client reports; recruiters capture every detail of candidate interviews. This MCP server brings all of that recorded knowledge to your AI assistant.

Use cases

  • Recall decisions and commitments — *"What did we agree on pricing in my last call with Acme?"*
  • Catch up fast — *"Summarize my meetings from this week and list the action items."*
  • Find the exact moment — *"Find where the customer mentioned their renewal date."*
  • Prep for the next call — *"Who attended the Q3 planning meeting and what did we promise to follow up on?"*

Tools

All tools are read-only. The server returns raw snippets from your meetings; your AI client generates the answer. It never writes to your account, makes LLM calls of its own, or touches data that isn't yours.

ToolPurpose
list_meetingsBrowse your recent meetings — title, date, duration, status, and a short summary (metadata only).
search_meetingsSemantic search across your transcripts; returns the most relevant transcript snippets.
get_meetingFull details for one meeting — participants, AI summary points, and metadata.
get_transcriptThe full, paged transcript text, formatted as [m:ss] Speaker: text.

How you connect

You only need a [Laxis account](https://app.laxis.tech). Add the endpoint to your AI client and it will open your browser to sign in with Laxis (OAuth 2.1

  • PKCE) the first time it connects — approve once and you're done. Access tokens

refresh automatically, and you can revoke a client's access anytime from Laxis → Settings → Claude (MCP).

The connection endpoint is always:

https://app.laxis.tech/mcp

We no longer recommend personal API keys. Signing in with OAuth is more

secure (no long-lived secret to copy, store, or leak) and just as quick. API

keys remain available only for tools that can't sign in interactively — see

Connecting without a browser.

Install

Pick your client. In every case you connect with the URL above and sign in with Laxis when prompted — there's no key to paste.

Claude Desktop & claude.ai (web) — custom connector (recommended)

In Claude Desktop or on claude.ai go to Settings → Connectors → Add custom connector, paste the URL below, and complete the "sign in with Laxis" flow.

https://app.laxis.tech/mcp
Claude Code
claude mcp add Laxis --transport http https://app.laxis.tech/mcp

Then run /mcp in Claude Code and choose Authenticate to sign in with Laxis. Ask something like *"Use Laxis to summarize my last meeting."*

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 configure it manually in ~/.cursor/mcp.json:

{

"mcpServers": { "Laxis": { "url": "https://app.laxis.tech/mcp" } } }

VS Code

Requires VS Code 1.101+. After installing, VS Code prompts you to sign in with Laxis on first use. To configure manually, add a .vscode/mcp.json:

{

"servers": { "Laxis": { "type": "http", "url": "https://app.laxis.tech/mcp" } } }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json, then authorize when prompted:

{

"mcpServers": { "Laxis": { "serverUrl": "https://app.laxis.tech/mcp" } } }

Other clients

Any client that speaks Streamable HTTP to a remote MCP server and supports the MCP OAuth flow works. Point it at:

  • URL: https://app.laxis.tech/mcp
  • Transport: Streamable HTTP
  • Auth: OAuth 2.1 (the client discovers the sign-in flow automatically)

Connecting without a browser (API key)

Not recommended. Use this only for tools that can't complete an

interactive OAuth sign-in — headless scripts, CI, or automations such as

Zapier. A personal API key is a long-lived secret: anyone who has it can read

your meetings until you revoke it.

  1. In Laxis, go to Settings → Claude (MCP) → Advanced and generate a personal API key (laxis_…).
  2. Send it as a bearer token on every request:
   Authorization: Bearer laxis_…

For a desktop client that lacks native OAuth, you can bridge with mcp-remote and the header:

{

"mcpServers": { "Laxis": { "command": "npx", "args": [ "-y", "mcp-remote", "https://app.laxis.tech/mcp", "--header", "Authorization: Bearer laxis_…" ] } } }

Treat the key like a password. Regenerating it immediately invalidates the previous one (and any automations that share it), so update those afterward.

How it works

Your AI client ──OAuth sign-in──▶ Laxis (authorize + consent)

│ └──Bearer access token──▶ Laxis MCP Server ──▶ Laxis API ──▶ your meetings

The server is a thin, retrieval-only proxy in front of the Laxis API. It validates your OAuth access token, exchanges it for a short-lived, user-scoped upstream token (it never forwards your client's token to the API), fetches the requested meeting data, and returns raw snippets. Your AI client does all the reasoning and answer-writing. You only ever see your own meetings, and access stops the moment you revoke the connection (or, in API-key mode, the key).

Roadmap

  • Listing in Anthropic's connector directory and on public MCP registries, for one-click discovery.

Support

  • Questions / bugs: open an issue.
  • Product help: laxis.com / in-app support.
  • Security: see SECURITY.md — please report privately, not via public issues.

License

MIT © Laxis

Ask PopNx