AI Assistant Integration

Overview

Genchi collects anonymous confidence signals from your team, anchored to named initiatives. Team members cast a two-second check-in; the Owner sees the trend. The point is early warning before status turns red.

The AI assistant integration puts that signal where engineering leaders increasingly already are. Instead of opening a dashboard, you ask:

Genchi answers with the team's current anonymous confidence signal, its trend over the last six check-ins, how many people have checked in, and any blockers that have been raised.

The integration uses the Model Context Protocol (MCP), an open standard for connecting AI assistants to external systems. Any MCP-compatible assistant can connect — the same connector works with Claude, ChatGPT, and others as they adopt the standard.

What You Can Ask

Once connected, natural questions work. The assistant decides which Genchi tool to call.

You ask	Genchi returns
"What initiatives am I on?"	Every initiative you can see, lowest confidence first, with deadlines and your role on each.
"How is the payments migration tracking?"	Current confidence, the trend across the last six check-ins, and how many of the team have checked in.
"What's blocking the platform rebuild?"	Blockers currently raised, with who raised each and when.
"Give me this week's update on Project Atlas."	The weekly summary: current confidence against last week's, the trend, and blockers from the past seven days.
"Create an initiative for the Q4 API migration."	A new initiative with you as Owner and a weekly Friday check-in.
"Why am I not getting check-ins in Slack?"	Your Slack connection status and what to do about it.

Connecting Genchi to an AI Assistant

You need a Genchi account first. If you do not have one, create one free — Genchi is free for teams under 10 people.

The connector endpoint

If your assistant asks for a server URL, this is it:

Steps

1. In your AI assistant, add Genchi as a connector. Depending on the assistant this is under Settings, Connectors, Integrations, or a similar menu.
2. The assistant will send you to a Genchi sign-in page. This page is on genchi.com — check the address bar.
3. Sign in with your Genchi email and password.
4. You will be returned to your assistant, connected.

You only do this once. The connection stays active until you revoke it, and does not require you to be signed in to Genchi in a browser afterwards.

Available Tools

The connector exposes six tools. Four read, two set things up.

Tool	Type	Purpose
genchi_list_initiatives	Read	Lists the initiatives you can see, with the current confidence signal for each.
genchi_get_confidence	Read	Current anonymous confidence signal and its trend over the last six check-ins for one initiative.
genchi_get_blockers	Read	Blockers currently raised against one initiative, with attribution.
genchi_get_weekly_summary	Read	The weekly summary for one initiative, including a comparison with last week.
genchi_create_initiative	Write	Creates a new initiative with you as Owner and a weekly Friday check-in.
genchi_connect_slack	Read	Reports whether a Slack workspace is connected and explains how to connect one.

Initiatives are identified by name, not by an internal ID. Matching is case-insensitive and partial, so "payments" finds "Payments Migration Phase 2". Where a name matches more than one initiative, Genchi lists the candidates and asks which you meant rather than guessing.

What the Assistant Can and Cannot See

It can see initiatives where you are the Owner, a team member, or an observer. For those: name, goal, deadline, aggregate confidence, six-check-in trend, participation counts, and blockers.

It cannot see initiatives you are not part of, other people's accounts, billing or subscription information, anything belonging to another company, or how any individual voted.

It can change exactly one thing: it can create a new initiative owned by you. It cannot delete or modify existing initiatives, change team membership, cast votes on anyone's behalf, or touch billing or account settings.

Anonymity

Genchi's core promise is that check-ins are visible but anonymous. People answer honestly because their individual answer is not attributable. That promise holds through the AI assistant integration without exception.

What the assistant receives is the aggregate: "the team's current confidence is 63%", "4 of 6 people have checked in", "the trend across the last six check-ins was 75%, 75%, 63%, 63%, 50%, 63%". It never receives the individual votes those figures are derived from.

This is enforced on Genchi's servers, not by the assistant. Individual votes are reduced to counts and averages before any response leaves our infrastructure — there is nothing for an assistant to disclose even if asked directly.

Blockers are the one exception, and deliberately so: a blocker is a comment someone chose to raise, and comments are attributed in Genchi by design. If you raise a blocker, your name is on it, in the app and through the assistant alike.

Managing and Revoking Connections

Inside Genchi, go to Admin → AI Assistants to see which assistants are connected, when each was connected, and when each was last used.

• My Assistants shows your own connections. Disconnect any of them at any time.
• All Assistants is visible to administrators and shows every connection across the company, with the person each belongs to. Administrators can revoke any of them.

Revocation is immediate. The assistant loses access on its very next request — there is no cached-access window. You can also disconnect from within the assistant itself, which has the same effect.

Technical Details

Item	Value
Server endpoint	https://genchi.com/api/mcp
Transport	Streamable HTTP
Authorization	OAuth 2.1 with PKCE (S256 required)
Authorization server	https://genchi.com
Protected resource metadata	https://genchi.com/.well-known/oauth-protected-resource/api/mcp
Authorization server metadata	https://genchi.com/.well-known/oauth-authorization-server
Client identification	Client ID Metadata Documents, or Dynamic Client Registration at https://genchi.com/api/mcp/register
Scopes	genchi:read, genchi:write. offline_access is honoured for refresh tokens.
Access token lifetime	1 hour, renewed automatically
Refresh token lifetime	30 days, rotated on each use

Security

• Per-user authorization. Each connection is granted by an individual signing in and approving it, and is scoped to that person's own visibility.
• Tokens are hashed, not stored. Access and refresh tokens are held as one-way SHA-256 hashes. A copy of our database would not yield working credentials.
• Short-lived access with rotating refresh. Access tokens last one hour. Each renewal issues a new refresh token and invalidates the old one, so a stolen refresh token stops working as soon as the legitimate client next renews — and the reuse attempt is detectable.
• Audience binding. Tokens are bound to this specific endpoint and rejected if presented anywhere else.
• PKCE is mandatory. Only the S256 method is accepted. Authorization codes are single-use and expire within minutes.
• Redirect validation. Authorization codes are only ever delivered to a redirect URI the client has registered in advance, matched exactly.
• Immediate revocation. Revoked connections are refused on the next request, with no cached-access window.

Full detail is in our Security Policy. How data is handled is covered in our Privacy Policy.

Test Instructions for Reviewers

A test account with realistic initiatives, check-in history, and blockers can be provided on request — email support@genchi.com. Alternatively:

1. Create a free Genchi account at app.genchi.com/create-account and verify the email address.
2. Sign in and create an initiative with a name, a goal, and a deadline. Add a second one so name-disambiguation can be exercised.
3. Cast a check-in against each initiative so there is signal to report. In the web app, open the initiative and use the Check-In tab.
4. Add the connector at https://genchi.com/api/mcp in your assistant, and complete the OAuth flow when prompted.
5. Ask the assistant to list your initiatives. It should return a table, lowest confidence first.
6. Ask how one of them is tracking. It should return the confidence figure, the six-check-in trend, and participation counts — and no individual votes.
7. Ask about an initiative name that matches both of yours partially. It should list the candidates and ask which you meant.
8. Ask it to create an initiative. Confirm it appears in the web app with a weekly Friday cadence and you as Owner.
9. In Genchi, go to Admin → AI Assistants and confirm the connection is listed. Disconnect it, then ask the assistant another question — it should be refused.

Troubleshooting

The assistant says it has no Genchi tools. Check that the connector is enabled for the conversation as well as added to your account — most assistants require both. Some assistants only pick up connectors when a conversation starts, so try a new conversation.

Sign-in fails on the Genchi page. The connector uses your normal Genchi email and password. If you signed up with Google or Atlassian and have never set a password, use "Forgot password" at app.genchi.com to set one.

"Please verify your email address before connecting." Your Genchi account exists but has not been verified. Check your inbox for the verification link, or request a new one from the Genchi sign-in page.

An initiative is missing. The connector only returns initiatives where you are the Owner, a team member, or an observer. Archived and completed initiatives are excluded. Ask the Owner to add you if you should have access.

"No signal yet" against an initiative. Nobody has cast a check-in against it. Confidence appears once the first check-in is recorded.

Contact

For questions, test accounts, or review support, please contact:
support@genchi.com