Connecting AI Assistants

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:

1. Your browser opens an authorization page on Kit
2. If you belong to multiple accounts, you select which one to connect
3. Kit issues a token scoped to that account
4. 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 connections use two permission scopes:

Scope	What It Allows
mcp	Read-only access — list jobs, view templates, browse applications, search talent pool and video transcripts, search docs
mcp_write	Write access — advance or reject applications, create templates, invite team members, invite talent pool candidates to jobs

Claude Desktop and Claude Code request both scopes by default. You can see which scopes each connected client has on the settings page.

Managing Connected Clients

The MCP Setup page shows all connected clients with:

• App name — The MCP client that connected
• Scopes — Permissions granted
• 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
• Test with “What job postings do I have?” in your AI assistant
• Verify the connection appears in Connected Clients