The manager connector: your incidents, from your phone

Point Claude (mobile or desktop) or ChatGPT at your Landfall organization and ask, in plain language, what an engineer would otherwise have to summarize for you: what's burning right now, what happened last month, whether we've seen this before, and what's waiting on a decision. It is a read-only lens: nothing you ask can approve, execute, page, or change anything.

What you'll need

• A Landfall account that is a member of the organization: the connector signs you in with whatever method your organization already uses, and a departed member loses access immediately.
• An AI assistant that supports remote MCP connectors (Claude and ChatGPT both do).

1. Add the connector

1. Copy your organization's connector address

   It is your API base URL plus your organization's slug: https://api.landfalls.ai/o/<your-org>/mcp

2. Add it in your assistant's connector settings

   In Claude: Settings → Connectors → Add custom connector. In ChatGPT: Settings → Connectors. Paste the address: registration and discovery are automatic.

3. Sign in and consent

   Your browser opens Landfall's ordinary sign-in for that organization, then a consent screen listing exactly what the connector may read. The credential it mints is short-lived, pinned to that one organization, and revocable at any time.

Don't know your organization's slug? Use the single, org-agnostic address

https://api.landfalls.ai/mcp works for any Landfall organization: no slug to look up or paste. Add it exactly the same way; after you sign in, Landfall asks which organization to connect to (skipped automatically if you belong to only one). It is the same connector underneath, with the same read-only guarantees, just reached without already knowing your organization's address. This is also the address a directory-style, one-click install would eventually use.

2. What you can ask

• Now: “What incidents are ongoing?” · “How bad is the checkout incident, and who's on it?” · “What's waiting on a decision?” Served by the live incident list, the manager brief, and the open decisions view. The brief includes a paragraph written to be forwarded to stakeholders as-is.
• The past: “What incidents did we have last month?” · “How was the CDN outage closed out?” Closed and resolved investigations are listed newest first, over any time window, and a closed incident's brief leads with the outcome: when it closed, and how.
• The organization's memory: “Have we had payments problems before?” · “What do we know about our CDN vendor?” Answered from organizational memory built out of past incidents' corroborated facts. Every entry carries a confidence label, and anything the team later judged wrong is excluded.

What it can never do

The connector advertises no write capability beyond a single optional acknowledgement (“leadership has seen this”) that changes no incident state. It cannot approve a remediation, page anyone, change severity, or post into the war room; those live in the war room itself, behind Landfall's human-approval gate. Every answer names incidents by their human-readable id (like Acme 42); raw identifiers never appear.

Scoped sharing

A connection can also be pinned to a single incident (https://api.landfalls.ai/o/<your-org>/i/<number>/mcp), useful for sharing exactly one investigation with someone who should see nothing else. A pinned connection sees that incident only, and the organization-wide history and memory reads are refused for it.