Connect

Connect Lookout to Claude Code

Lookout is a standard remote MCP server. You add it once, approve access in your browser, and it shows up as a set of tools inside Claude Code. Lookout is in private beta, so access is invite-scoped — but the command, endpoint, and auth flow below are final and won't change.

1 · Add the server

Run this in your terminal:

claude mcp add lookout --transport http --url https://lookout.neurobaselabs.com/mcp

This registers Lookout as an HTTP-transport MCP server pointed at the frozen endpoint https://lookout.neurobaselabs.com/mcp. Nothing is stored yet — registration just tells Claude Code where the server lives.

2 · Authorize once (OAuth 2.1 + PKCE)

The first time Claude Code calls a Lookout tool, your browser opens a consent screen. Approve it and you're done. Under the hood:

  • Authorization uses OAuth 2.1 with PKCE — the standard, no client secret to leak.
  • Lookout receives a short-lived, scoped access token. No API key is ever written to disk.
  • Your identity is derived from that token on every call — never from anything you type into a prompt.
  • Revoke access in one click from your Lookout settings; the token dies immediately.

3 · Confirm it's wired

Ask Claude Code to list your meetings — the fastest way to confirm the connection:

> Use Lookout to list my most recent meetings.

  -> lookout.list_meetings(limit: 5)

If your recent meetings come back, you're connected. If the list is empty right after connecting, your first ingestion may still be threading — instant backfill of your past meetings runs automatically, and it's free. Full tool reference: /docs/tools.

Private beta.The connect flow is live for design-partner teams; broader access is rolling out. The command and endpoint above are final and won't change. Works anywhere MCP does — the same pattern applies in Claude Desktop, Cursor, and Windsurf.