# Laxis Tech Laxis MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp
Registry id: `mcp-registry/io.github.laxis-tech/laxis-mcp`
Status: auth-required (checked 2026-10-26T20:00:08.629Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 211
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "laxis-tech-laxis-mcp-server": {
      "type": "http",
      "url": "https://app.laxis.tech/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http laxis-tech-laxis-mcp-server https://app.laxis.tech/mcp
```

## Tools (4)

- `get_meeting`: Get one meeting's details: title, date, participants, keywords, and summary. Does NOT include the transcript text — use get_transcript for that, or search_meeti
- `get_transcript`: 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, cal
- `list_meetings`: List 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 
- `search_meetings`: Semantic 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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.