Gigi
Ask your AI assistant who you know.
Gigi turns your contacts, calendar history and confirmed profile context into a searchable professional network — the people you have actually met, emailed and worked with. This package brings that network to your assistant, and to your terminal.
You need a Gigi account. Nothing else.
Start here
If your AI assistant can run a command — Claude Code, Codex, Cursor, Grok, and most coding agents:
claude mcp add gigi -- npx -y @askgigi/cli mcp
That's it. Ask it "who do I know at Stripe?" and it will use your network instead of guessing.
If you'd rather use a terminal:
npm install -g @askgigi/cli
gigi login # opens a page to approve; takes about ten seconds
gigi help # every command, with an example you can copy
If your assistant takes a URL rather than a command, you don't need this package at all — paste
https://mcp.gigi.co/mcpinto its connector settings.
Things to ask
Once it's connected, these all work in plain language:
- Who do I know at Stripe?
- Find backend engineers I have actually met in person, closest first.
- Who in my network could introduce me to someone at a Series B fintech?
- Remind me who Ada is and how I know her.
From the terminal, the same questions look like this:
gigi context # what you can search, and how many people it reaches
gigi search --input '...' # one search; run `gigi help search` for the example
gigi more --input '...' # the next page
gigi paths --input '...' # who can introduce you to the people you name
gigi connect --input '...' # ask a contact to become a Key Person, or invite them
gigi requests # what is pending, both ways
gigi respond --input '...' # accept, decline, remind or cancel one of them
gigi suggest # who to add or invite next
A search takes twenty to sixty seconds — it reads your network rather than a keyword index — and tells you what it's doing while it works.
Signing in
gigi login
It prints a short code and a link. Open the link anywhere — your laptop, your
phone — approve it, and you're done. Press Enter and it opens the page for
you; --open skips the asking.
The machine running gigi never needs a browser of its own, which is what makes
this work inside an AI agent's sandbox.
Your session lives in ~/.config/gigi/credentials.json, readable only by you.
gigi logout revokes it properly, server-side, not just locally.
If you are a product signing in on someone's behalf
Say who you are, once, at login:
gigi login --client-name instinct
Every caller signs in as the same client, so without this Gigi cannot tell your
traffic from anyone else's and records the session as unknown. It is a label for
Gigi's own reporting: it grants nothing, it is not checked against anything, and
leaving it out is not an error. gigi status shows what the current session
declared.
When something goes wrong
Every failure prints one line of JSON with a name you can act on:
| It says | What to do |
|---|---|
authentication-required | Run gigi login. |
invalid-arguments | Run gigi help <command> — it prints a working example. |
device-code-expired | The code timed out. gigi login again. |
rate-limited | Sixty requests a minute, shared across everything you've connected. Wait a moment. |
search-timeout | The search ran long. Try a narrower one. |
tool-unavailable | Your account doesn't have that tool yet. gigi paths and gigi connect arrive with Gigi's second tool set. |
device-flow-unavailable | That server doesn't offer device login. Update the CLI, or connect over MCP instead. |
Stuck? [email protected].
What it will not do
It reads, on purpose: it searches, looks people up, reads profiles and finds
the paths to someone. What it can change, when you ask it to: send a Key People
request to a contact you name (gigi connect), exactly as the Connect button in
Gigi does — that contact is notified and decides — and act on a pending request
(gigi respond): accept or decline one you received, remind or cancel one you
sent, as the lists on your Network page do. It cannot send an introduction,
write a message, or change anything else in Gigi, and it only ever sees what you
can already see there.
gigi paths, gigi connect, gigi requests, gigi respond and gigi suggest need Gigi's second tool set on your account;
until it is there they answer tool-unavailable.
For scripts and agents
- stdout is exactly one line of JSON per command. Nothing else goes there.
- stderr carries progress and errors.
- Exit codes:
0worked,2your arguments were wrong,1everything else.
gigi help --json returns the whole command catalogue, examples included.
| Setting | What it does |
|---|---|
--server <url> / GIGI_MCP_SERVER_URL | Point at another Gigi. Defaults to production. |
--client-name <name> / GIGI_CLI_CLIENT_NAME | Optional, on gigi login only. Name the product driving this CLI, so Gigi can tell its traffic apart. Letters, digits, spaces, dots, underscores and hyphens, up to 40 characters. |
GIGI_CREDENTIALS_PATH | Where the session is stored. A .lock file beside it serialises renewals between concurrent gigi processes. |
GIGI_HTTP_TIMEOUT_MS | Per-request timeout, default 30000. Searches get their own, longer, budget. |
GIGI_DEBUG | Print a stack trace on an unexpected failure. |
MIT licensed. Built by the team at Gigi.