KiteGTM for Claude, ChatGPT and Codex
Kite is an introductions platform. It gets you into phone or video meetings with qualified people who have a reason to do business with you.
Who it helps: Businesses that want to meet the right people to achieve a business goal.
This plugin connects Claude, Claude Code, ChatGPT and Codex to your KiteGTM workspace, so you can ask about
that work and act on it where you already work.
It connects to one address, https://api.kitegtm.com/mcp, and signs you in through KiteGTM the first
time: you sign in the way you usually do, then press Allow. You can disconnect it at any time in
KiteGTM under Settings, AI apps.
What the words mean
- A mission is how Kite pursues your objective: who to reach, what an Introduction must show, and
the work in between.
- A buyer fit is a person Kite pursues. It is a verified match, not a sign of interest.
- An Introduction is a person who has agreed to talk and whom nothing on record rules out. A
condition you require that is not yet confirmed is confirmed on the call; one on record as not met
rules the person out. You get the person, their company, the context, the conversation, what is
known and still to confirm, and the next step. A meeting is optional. A reply, a referral or a
booking alone is not an Introduction.
- The connector's tools call these records opportunities. Each one says whether it is an
Introduction now and, if so, what is still to confirm on the call.
- Monthly Reach is the number of unique people Kite can source into your missions each month. Sends,
follow-ups and replies do not use it, and unused Reach does not carry over. Every Introduction is
included, with no separate fee or cap; a particular number is not guaranteed.
What it can do
- Read: your missions, the companies and decision-makers in each, buyer fits, email, LinkedIn and
SMS conversations, opportunities and whether each is an Introduction, results for a date range
(including Introductions), recent activity, your credit balance, your email, LinkedIn and SMS
campaigns and the people in them, your contacts and your contact imports. Find a person in your
workspace by name, email or company. Or ask a question in plain words.
- Mission recommendations: see the missions Kite recommends, refresh or dismiss them, and set one
up for review. Setting one up starts nothing: you get a link to review and start it in KiteGTM.
- Draft replies: a reply is saved as a draft on the conversation, with exactly the text given.
Nothing is sent from here: you review it and press Send in KiteGTM.
- Act: pause or resume a mission's search; pause, resume or stop pursuing a person; mark someone
as a qualified opportunity on your own judgement (this alone does not make them an Introduction) and
record an opportunity's outcome; import a CSV or Excel file into your contact book, which sends no
messages; preview adding contacts to a campaign; remove contacts from a campaign; pause a campaign.
- Campaign enrollment stays with you: an AI app cannot enroll people into a campaign. It returns a
request to review the list and complete enrollment in the signed-in KiteGTM app, where consent,
suppression and duplicate checks apply.
- Not here: buying credits, changing your plan or Monthly Reach, payment methods and your
subscription stay in KiteGTM, and no purchase or upgrade link is shown in your AI app. So do
creating, editing, starting, resuming and deleting campaigns, and enrolling people into them.
Versioned permissions
Versioned permissions for AI app connections: available when your workspace has it turned on. Until
then, and for every connection made before, everything above stays exactly as it is.
- You choose what a connection may do when you press Allow, and the connection stays in the
workspace you allowed it for. To give an existing connection these choices, connect it again from
your AI app.
- Actions you confirm in KiteGTM. Sending a reply, starting or resuming a mission, resuming a
person, recording an outcome and adding contacts to a campaign are prepared by the app and happen
only after you confirm that exact action in KiteGTM, signed in to that workspace. Starting a mission
uses Monthly Reach as people are sourced into it.
- Longer work. The app can hand Kite a task. Kite keeps it even if the chat closes.
- Disconnecting stops future access; it does not erase what the app already received.
Where people come from, and opt-outs
- People come from KiteGTM's business-contact data, whose details are compiled from public
professional and business sources and business-contact sourcing and verification services, or from
contacts you bring yourself (a CSV or Excel import, or your CRM). The
privacy policy sets out the legal basis for
holding and sharing that data. Kite works through the email, LinkedIn and SMS you connect.
- Anyone can be removed from KiteGTM's data by emailing [email protected]. Our team handles the
request manually, removes active sourced-contact copies, and keeps a minimal suppression record to
prevent future sourcing and outreach across KiteGTM workspaces. This is separate from one
customer's do-not-contact list.
- Every cold email carries a one-click unsubscribe. A reply asking to stop, on email, LinkedIn or SMS,
puts the person on your workspace's do-not-contact list for the channels KiteGTM can link to that
identity; a request KiteGTM is unsure about is held for you to decide.
- Customer SMS campaigns require recorded consent. The first text says "Reply STOP to opt out", and
STOP suppresses outreach through the channels linked to that identity.
- You can add people to your do-not-contact list yourself. Every send, on every channel, checks it.
Install
Claude Code
claude plugin marketplace add inkris-apps/kitegtm-plugin
claude plugin install kitegtm@kitegtm
Or add the server alone: claude mcp add --transport http kitegtm https://api.kitegtm.com/mcp, then
run /mcp to sign in.
Codex
codex plugin marketplace add inkris-apps/kitegtm-plugin
Then install KiteGTM from /plugins. Or add the server alone with
codex mcp add kitegtm --url https://api.kitegtm.com/mcp and codex mcp login kitegtm.
Claude and ChatGPT
Add KiteGTM from the Claude connector directory or the ChatGPT plugin directory. Until it is listed,
add a custom connector with the address above.
Guide, privacy and support
For maintainers
The current version is recorded in both plugin manifests below. The repository is the plugin: Claude Code and Codex install it from this
repository's main branch through its marketplace files, so a push to main (wt ship) publishes it.
| File | Purpose |
|---|
.claude-plugin/plugin.json | Claude Code plugin manifest (name, version, description) |
.claude-plugin/marketplace.json | Claude Code marketplace kitegtm |
.codex-plugin/plugin.json | Codex and ChatGPT plugin manifest, with its listing text |
.agents/plugins/marketplace.json | Codex marketplace kitegtm |
.mcp.json | The connector, https://api.kitegtm.com/mcp |
skills/kitegtm/SKILL.md | How the assistant should use the connector and its vocabulary |
assets/ | Logo and composer icon |
- The tools themselves live in the backend (
ops-service/app/gateway_mcp.py); this repository only describes and
connects to them. Keep this README, SKILL.md and both manifests in step with what the live connector does.
- Releasing: installed copies are kept by version, so every change to what is installed (the manifests,
.mcp.json, the skill or the assets) needs a new version in both plugin.json files. wt ship writes it (Kite
versioning: the plugin keeps its own number until the Kite version passes it, then takes the Kite number); never
edit it by hand, and the pre-commit hook refuses a task that does. Run claude plugin validate . and
claude plugin validate .claude-plugin/plugin.json before landing.
- Work happens on
claude/<slug> or codex/<slug> branches cut from landed and lands through wt, like the
other KiteGTM code repositories. There is no CI. Git history and release tags record earlier versions;
the tag kite-v1.0.0 marks the Kite 1.0.0 baseline.
- Before releasing, verify the installed plugin's skill and connector tool list together. Available tools depend on
the connected account and scopes; a source declaration alone does not prove a client exposes it. In a test workspace,
check finding a person and all five recommendation tools, including preparation's review link and no-start boundary.
Verify Introduction reporting keeps conditions to confirm separate from conditions known not to be met.
