Connect Claude to Stori
Ask Claude what your candidates actually said and get their own words back with a timestamp; add notes, move people, open roles and schedule interviews from the same chat. Setup takes about a minute.
What the Connection Does
Teller, Stori's hiring agent, sits on every page of Stori. You do not have to be in Stori to use it. Stori connects to AI assistants through the Model Context Protocol (MCP), the open standard used by claude.ai, Claude Desktop, ChatGPT and a growing set of AI tools, so you can work in the assistant your team already uses, on the same data you see in the app:
- "Which of my jobs has the most interviewed candidates?"
- "Compare Daniel Lee and Marcus Bennett on building a design system from scratch, with quotes from their interviews."
- "On the Product Designer role, who has actually rebuilt a design system? Quote what they said."
- "Add a note on Kevin Lin and move him to the final stage."
- "What is our time to hire over the last six months?"
- "What did the assistant change today?"
Every answer about a candidate is grounded in their actual interview. When Claude quotes a candidate, the quote is real, cited, and carries a video timestamp so you can check it in one click. Ask about what a candidate did, not which competency they show: a Stori interview records what happened, in the candidate's own account, which is why the answer can be quoted.
When Stori orders a pool, it orders by the strength of role-relevant, checkable evidence. It identifies who should be considered, not who is best. The connection is decision support; you decide.
Setup (About a Minute)
The same steps are in Stori under Settings > Integrations > AI Apps, with Claude selected, and a button to copy the URL.
- Open claude.ai > Settings > Connectors (Claude Desktop has the same menu) and choose Add custom connector.
- Name it Stori and paste this URL:
https://www.onestori.com/api/mcp - Claude sends you to Stori's sign-in. Sign in with your company workspace account, the one you use for the Stori dashboard.
- Read the consent screen, which lists what you are allowing, and click Allow. Start a new chat and ask away.
If your sign-in also has a personal Stori, the consent screen asks which one to connect. Choose your company workspace. If it says there is no company workspace on the account, you have signed in with the wrong login; sign in with your company's Stori login instead.
What Claude Can and Cannot Do
A connected assistant can read:
- Your jobs and their candidate counts, and any role in full
- A job's pool, or a person found by name or email across every role
- Your candidates' interview transcripts, with quotes and timestamps
- A candidate's report, their Stori record, and the interview transcript word for word
- Candidates side by side, and a pool ordered by strength of evidence
- Your pipeline, funnel and hiring numbers, and your outreach results
- What interviews are booked, who can sit on a panel, and where offers stand
- Teller's proposals on each job, and your credit balances
Within the permissions your workspace has switched on, it can act:
- Add notes and tags, move candidates between stages, and reject a candidate with a written reason
- Create and edit roles, change a role's status, and decide on Teller's proposals
- Invite a candidate to interview and schedule the interview loop
- Draft an offer against the role's salary band and send it round the approval chain
- Source candidates from outside your pool, reveal a sourced person's contact details, and draft or send outreach
Every change is written to your audit log against the person whose connection made it, so "what did the assistant change today?" has an exact answer.
It cannot:
- See any other company's data: access is locked to your workspace at the moment you click Allow
- Send an offer to a candidate: that stays a deliberate act in the app
- Read pay from a list of offers: figures appear only when you ask about one offer
- Change workspace settings or create API keys: that is not available to sign-in connections
- Act without a signed-in member of your team having approved the connection
Behind the scenes: OAuth 2.1 with PKCE, short-lived rotating tokens stored only as hashes, and per-workspace isolation enforced on every request.
What You Approve and What Your Admin Controls
Two gates sit over every connection.
What you approve. The consent screen names each permission. Reading and everyday changes inside the workspace are included; revealing contact details, sending outreach and sending interview invitations are each opt-in, because they reach someone outside your company or spend credits.
What your admin allows. Under Settings > Integrations > AI Apps > What connected apps can do, workspace admins set a ceiling for every connected app and API key:
- Inside the workspace: Read the workspace and Update records, both on for a new workspace.
- Reaching outside it: Source candidates externally, Reveal contact details, Draft outreach, Send outreach, Invite candidates to interview and Change workspace settings, each off until an admin turns it on.
The ceiling wins over whatever a member approved. A tool whose switch is off is refused, and the assistant is told which switch to ask an admin about.
Managing and Disconnecting
Every active connection is listed under Settings > Integrations > AI Apps > Connected apps: which app, who connected it, when, when it was last used, and what it was approved for. Any member can disconnect their own connection; admins can disconnect anyone's. Disconnect takes effect at once: the app's tokens are revoked and its next request is refused.
Teller on Your Own AI Account
Teller in Stori works as soon as you sign in. If you would like Teller to run on your company's own ChatGPT, Claude, Gemini or Grok account, so you work the same way across apps, an admin pastes an API key from that provider under Settings > Integrations > AI Apps > Teller in Stori and clicks Connect. Stori reads which provider the key belongs to and checks it with them. From then on Teller runs on that account and the provider bills the usage. The key is encrypted and never shown again beyond its last four characters; Remove key puts Teller back on the chat that comes with Stori.
Developers and partner tools can also connect with a Stori API key instead of signing in. See Connect Any AI Assistant.