Laxis MCP Server

Laxis MCP Server

The Laxis MCP Server connects Laxis 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 just add one URL and your personal API key to your AI client. There is no local binary, Docker image, or npm package to manage.

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.

Prerequisites

1. A Laxis account — sign up at app.laxis.tech.
2. A personal API key (see below).
3. An MCP client that supports remote servers with a custom Authorization header — e.g. Claude Code, Cursor, VS Code, or Windsurf. (See Claude Desktop & claude.ai for those clients.)

Get your API key

1. Go to app.laxis.tech → Settings → Claude (MCP).
2. Click Generate API key. Copy the value — it looks like laxis_xxxxxxxx….

Treat this key like a password: it grants read access to your meetings. Regenerating the key immediately invalidates the previous one (and any Zapier zaps that share it), so update your connectors afterward. The same screen shows a ready-to-paste claude mcp add command for Claude Code.

The connection endpoint is always:

https://app.laxis.tech/mcp

with the header:

Authorization: Bearer YOUR_KEY

Install

Replace YOUR_KEY below with the key you generated.

Claude Code (recommended)

claude mcp add Laxis --transport http https://app.laxis.tech/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Then ask Claude something like "Use Laxis to summarize my last meeting."

Cursor

The one-click button adds the server with a placeholder key — after installing, open Cursor → Settings → MCP (or ~/.cursor/mcp.json) and replace YOUR_KEY with your real key. Or configure it manually:

{
  "mcpServers": {
    "Laxis": {
      "url": "https://app.laxis.tech/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

VS Code

Requires VS Code 1.101+. You'll be prompted for your API key on first use. To configure manually, add a .vscode/mcp.json to your workspace (this version prompts for the key and stores it securely instead of hard-coding it):

{
  "inputs": [
    {
      "type": "promptString",
      "id": "laxis_pat",
      "description": "Laxis personal API key",
      "password": true
    }
  ],
  "servers": {
    "Laxis": {
      "type": "http",
      "url": "https://app.laxis.tech/mcp",
      "headers": {
        "Authorization": "Bearer ${input:laxis_pat}"
      }
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "Laxis": {
      "serverUrl": "https://app.laxis.tech/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Claude Desktop & claude.ai (web)

Native one-click custom connectors in Claude Desktop and on claude.ai use OAuth, which is coming soon for Laxis (see Roadmap). Until then, connect Claude Desktop with the mcp-remote bridge (requires Node.js). Edit Settings → Developer → Edit Config (claude_desktop_config.json):

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

Restart Claude Desktop after saving.

Other clients

Any client that speaks Streamable HTTP to a remote MCP server works. Point it at:

• URL: https://app.laxis.tech/mcp
• Transport: Streamable HTTP
• Header: Authorization: Bearer YOUR_KEY

How it works

Your AI client ──(Authorization: Bearer laxis_…)──▶ Laxis MCP Server ──▶ Laxis API

The server is a thin, retrieval-only proxy in front of the Laxis API. It holds no signing keys: it exchanges your personal API key for a short-lived, user-scoped token, fetches the requested meeting data, and returns raw snippets. Your AI client does all the reasoning and answer-writing from those snippets. You only ever see your own meetings, and access stops the moment you regenerate or delete the key.

Roadmap

• OAuth 2.1 connector — one-click "Add custom connector" support for claude.ai (web) and Claude Desktop, with no API key to copy/paste.
• Listing on public MCP registries and directories 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