Connecting AI Assistants
Connect Claude Desktop, Claude Code, or other MCP clients to manage your hiring workflows with AI.
Why It Matters
MCP (Model Context Protocol) lets AI assistants like Claude interact directly with your Kit account — listing job postings, reviewing templates, inviting team members, and more. Instead of copy-pasting between your browser and an AI chat window, the assistant reads and acts on your real data.
What You Need
- A Kit account with admin access
- An MCP client: Claude Desktop, Claude Code, or any MCP-compatible app
Setup
Navigate to Integrations > MCP Setup. You’ll see your MCP Server URL and ready-to-copy configuration for each client.
Claude Code (CLI)
Run this in your terminal:
claude mcp add --transport http kit https://startupkit.app/api/v1/mcp
Or add to your .mcp.json config file:
{
"mcpServers": {
"kit": {
"type": "http",
"url": "https://startupkit.app/api/v1/mcp"
}
}
}
Claude Desktop
Add this to your Claude Desktop configuration file:
{
"mcpServers": {
"kit": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://startupkit.app/api/v1/mcp"]
}
}
}
Claude Desktop uses mcp-remote to handle the OAuth flow via a local proxy.
Authorization Flow
When your MCP client connects for the first time:
- Your browser opens an authorization page on Kit
- If you belong to multiple accounts, you select which one to connect
- You choose which modules the assistant can access — and whether each is read-only or read & write
- Kit issues a token scoped to that account and those modules
- The client stores the token and refreshes it automatically
Tokens expire after 2 hours and are auto-refreshed. You don’t need to re-authorize unless you revoke access.
Scopes
MCP access is granted per module. Each module has a read scope and (except Compensation Research) a write scope:
| Module | Read Scope | Write Scope | What It Covers |
|---|---|---|---|
| Hiring | hiring_read |
hiring_write |
Job postings, applications, reviews, talent pool, templates, and Career Portal tools |
| CSiRT | csirt_read |
csirt_write |
Vulnerability reports, triage, researcher messages, bounties, program setup |
| Outreach | outreach_read |
outreach_write |
Campaigns, prospects, email drafts, metrics |
| Compensation Research | compensation_read |
— | Salary benchmarks, market trends, role comparisons (read-only) |
| Team | team_read |
team_write |
Members and invitations |
The base mcp scope is always granted. It covers the global tools only: docs search, pricing plans, echo, and the PDF sanitizer.
The Consent Screen
When you authorize a connection, the consent screen walks you through:
- Pick the account — if you belong to multiple accounts, choose which one to connect
- Choose module access — each module appears as a row with a Read | Read & write segment. Writes are off by default; switch a module to Read & write only if the assistant should take actions, not just look. Modules with risky write tools show a warning line explaining what you’re enabling.
Modules your account doesn’t have are hidden from the consent screen. Tools from modules you didn’t grant are invisible to the assistant — they never appear in its tool list.
Connections authorized before module scopes have full access; revoke and reconnect to limit them.
To change what a connection can do, revoke it on the MCP Setup page and connect again — the new consent replaces the previous grant.
Managing Connected Clients
The MCP Setup page shows all connected clients with:
- App name — The MCP client that connected
- Scopes — Per-module access granted, shown as chips (R for read, RW for read & write)
- Authorized at — When the connection was made
- Last used — When the client last called a tool
Click Revoke to disconnect a client. The client will need to re-authorize to connect again.
Quick Checklist
- Navigate to Integrations > MCP Setup
- Copy the config for your MCP client
- Run or paste it into your client’s configuration
- Authorize the connection when your browser opens — pick the account and choose module access (Read or Read & write) on the consent screen
- Test with “What job postings do I have?” in your AI assistant
- Verify the connection appears in Connected Clients