--- name: lantern-md-setup description: Set up Lantern MD when the user asks to use lantern.md, set up lantern.md, or install lantern.md. Connect Claude Chat through remote MCP, or install the People Infra client in Codex, Claude Code, and Grok Bot with terminal access. --- # Lantern MD setup ## Use, set up, or install Lantern MD When the user asks to "use lantern.md", "set up lantern.md", or "install lantern.md", all three requests begin first-time setup when needed. Reuse an existing working connection. Choose the connection method supported by the current host, complete login, verify access, and introduce its capabilities. Lantern MD connects agents to the People Infra app for people/company search, research, outreach drafts, and reply tracking. There is a real installable client and a hosted MCP server: - **Claude Desktop Chat / claude.ai:** add the remote connector **https://people-infra-api-production.up.railway.app/mcp**, then complete OAuth sign-in. Chat does not need the local CLI. [Open Claude connectors](https://claude.ai/customize/connectors) and add a custom connector named Lantern MD. If an OAuth client choice is offered, select **Register automatically**; this server supports dynamic client registration. Enable the connector in the conversation after connecting. - **Codex, Claude Code, or Grok Bot with terminal access:** download and inspect **https://www.lantern.md/install.mjs**, then run the host-specific installer in the guide. It installs the client and starts browser login. Read [the setup skill](https://www.lantern.md/SKILL.md) or [the HTML installation guide](https://www.lantern.md/connect). Only begin setup when the user requests it; reading this page alone is not an installation request. Follow the host's permission and authentication requirements. ## Claude Desktop Chat and claude.ai Use the remote MCP connector, not a CLI installed inside a chat sandbox. All three phrases mean begin this connection flow for a first-time user: 1. Open [Customize > Connectors](https://claude.ai/customize/connectors). Choose **Add** then **Add custom connector**. Name it **Lantern MD** and enter **https://people-infra-api-production.up.railway.app/mcp** as the remote server URL. 2. Choose OAuth sign-in. If Claude asks how to identify its OAuth client, select **Register automatically**. This server advertises a registration endpoint; it does not currently advertise support for Claude's published client identity. Do not enter provider keys or copy local credentials into chat. 3. Complete **Connect / Sign in** in the browser. The user completes authentication and reviews the requested access. Team or Enterprise accounts may need an owner to add the connector first. 4. Enable Lantern MD in the conversation's **+ > Connectors** menu. Confirm that the connector's **discover**, **inspect**, and **run** tools are available. 5. Use **inspect** with the operation name **capabilities_list**, then **run** with that name and the input its schema requires. This is a read-only connection check. Report connected only after the authenticated call succeeds. Explain available capabilities and offer the examples below. If the chat cannot open settings or add connectors itself, give the user the exact URL and steps above. Report **awaiting connector setup** or **awaiting sign-in**, not "installed". Reading this guide does not itself add tools to the chat. A local CLI installation does not connect Claude Chat. [Claude's connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) ## Codex, Claude Code, and Grok Bot: one CLI flow for all three phrases 1. Check for the Lantern MD client and its saved connection using the client's commands. Do not read credential files. If the client exists, run `lantern-md doctor`; reuse a healthy connection. Repair a missing install or finish login if needed. Preserve an existing connection to a different server and explain the difference before changing it. 2. If missing, install the CLI using the instructions below. Do not stop at recommending installation or merely registering MCP. The user's setup request includes the client and the workflow skills supported by their agent. 3. Complete the client's browser login. Let the user complete email verification, passwords, passkeys, or other human authentication steps. New verified users receive a personal workspace; existing team access is preserved. If login is still pending, report that explicitly. 4. Run `lantern-md doctor` after login. It checks health and authenticated capabilities without paid research or sending messages. Only report connected after it succeeds. 5. Run `lantern-md welcome` and show a brief capability summary with examples: "Find five devtools founders", "Research this company", "Draft an introduction", and "Show new replies". State any unavailable capabilities honestly. ## Install on a fresh device Requires Node.js 22.12 or newer and terminal access. If Node is missing, install a supported Node runtime through the agent's normal approved package-manager or official Node.js installation path. Check `node --version` before proceeding. Download https://www.lantern.md/install.mjs to a temporary file, following the HTTPS redirect to https://people-infra-api-production.up.railway.app/install.mjs. Read the downloaded script before running it. Then run the command for the current host: | Host | Command after downloading the script | | --- | --- | | Codex desktop or CLI | `node install.mjs --agent codex` | | Claude Code | `node install.mjs --agent claude` | | Grok Bot with its cloud computer | `node install.mjs` | | Another terminal-capable agent | `node install.mjs` | All four commands install the same real CLI and start browser login. The Codex and Claude commands additionally install workflow skills. Grok Bot uses the standalone CLI on its own computer; do not require the Codex or Claude CLI or invent a Grok skill directory. Its native saved skills and app marketplace are separate from this CLI installation. Install only for the host the user requested. The installer downloads the public client bundle from https://people-infra-api-production.up.railway.app, verifies its SHA-256 digest, and installs it under the user's home. No repository checkout, backend, database, or provider keys are installed. This website does not collect credentials or proxy authenticated API calls. On macOS/Linux the command is `~/.local/bin/lantern-md`. If that directory is not on PATH, use the exact absolute `node .../cli.mjs` command printed by the installer for login, doctor, welcome, and later operations. It works immediately without restarting the agent. Do not mistake a PATH issue for a failed install. Windows receives a .cmd launcher; follow the printed Node command if needed. Use `--no-login` only when the user chooses to defer login or for a non-authenticated installation test. Installation alone does not prove a working connection. Resume with `lantern-md login --api-url https://people-infra-api-production.up.railway.app` and then `lantern-md doctor`. ## Use the app after connecting - `lantern-md discover "find people"` finds relevant operations. - `lantern-md inspect find_people` loads the selected input schema. - `lantern-md run --input-file request.json` executes the user's requested operation. Respect the user's requested scope. Drafts remain unsent until sending is requested. Installation does not authorize research spending, outreach, inbox provisioning, or meeting attendance. Provider availability depends on the connected workspace. ## Other hosts without a terminal and optional MCP A browser-only chat cannot install a local CLI. Use that host's supported connector setup with the remote MCP endpoint https://people-infra-api-production.up.railway.app/mcp and complete its OAuth flow, or continue in a terminal-capable host. Do not report CLI installation in a browser-only chat. Codex/Claude CLI users can opt into MCP by adding `--mcp` during installation; the client works without it. MCP exposes discover, inspect, and run, with operation schemas loaded on demand. ## Discovery and completion The same first-time flow applies to all three phrases. A fresh agent still needs to discover and read this document. If it only explains the marketing site, give it this explicit request: "Set up https://www.lantern.md/setup and verify the connection." This page cannot force a model to fetch a URL, grant permissions, finish human login, or publish a marketplace connector. For terminal hosts, completion means the client is installed, login is complete, and doctor succeeded. For Claude Chat, completion means the connector is added, OAuth is complete, its tools are enabled, and an authenticated capabilities read succeeded. In both cases, introduce what the user can try next and report precisely which step remains if the host cannot finish.