Skip to main content
Take action on your AI visibility without leaving your AI assistant. The Kime MCP server connects tools like Claude, ChatGPT, Cursor, and Claude Code — or any client that supports the Model Context Protocol (MCP) — directly to Kime, so you can work your action plan, create and update actions, and launch new prompts to track, all from a conversation. You’re connected to the same data the dashboard shows, so the context is always there when you need it. Dig into visibility, competitors, sentiment, and sources to understand the story behind an action — then act on it right away.

What you can do

Work your action plan

Pull the actions Kime ranks by predicted impact, create new ones, and move them forward — your assistant confirms before it writes.

Launch & track prompts

Add prompts in bulk to start tracking, then review how each one performs.

Track visibility & competitors

See how you show up across every AI model and where you stand against competitors on visibility, placement, and share of voice.

Understand AI perception

Explore sentiment, the keywords driving tone, and the sources AI models cite when they mention your brand.

Setup guides

1

Open the Claude Desktop app

Launch Claude on your desktop.
2

Open Connectors

Go to CustomizeConnectors.
3

Add a custom connector

Click the + sign to add a connector, then select Add custom connector.
4

Enter the Kime URL

Call it Kime and enter this URL: https://mcp.kime.ai/mcp
5

Connect

Press Add, and then Connect.
The first time you ask Claude about Kime data, it will prompt you to securely sign in.
For full setup steps and troubleshooting across every client, see Connect AI assistants.

Example questions

Ask in plain language. Here are some prompts to get you started: Visibility & performance
  • “How has our visibility changed over the last 30 days?”
  • “Which AI models mention us the most?”
  • “Compare our visibility in ChatGPT versus Gemini this month.”
Competitors
  • “Which competitors have the highest share of voice?”
  • “Where do competitors show up but we don’t?”
  • “Compare our placement against [competitor] over the last 14 days.”
AI perception
  • “What’s our sentiment score across AI models right now?”
  • “Break our sentiment down by factor and show the strongest negative excerpts.”
  • “Which keywords drive negative sentiment about our brand?”
  • “Summarize how AI models currently describe us.”
Sources & citations
  • “Which domains get cited most when our brand comes up?”
  • “What sources are behind the most positive mentions of us?”
Take action
  • “What should we work on next to improve our AI visibility?”
  • “List our open actions and create one to publish a comparison page versus [competitor].”
  • “Mark the [competitor] comparison action as in progress and add a note with the angle.”
  • “Add these 10 prompts and start tracking them.”

Authentication

Kime uses OAuth — there’s nothing to paste or store. The first time your assistant uses a Kime tool, it opens a secure sign-in window where you log in and approve access. After that, your session persists across conversations. Access always respects your Kime account: an assistant can only see the organizations and workspaces you can, and acts within your existing permissions. The consent screen identifies which application is requesting access, and you can switch accounts if needed.

Read and write access

Most tools are read-only. Visibility, sentiment, sources, competitor benchmarks, prompts, and actions all pull existing data without changing anything. A smaller set of tools help you act on what you find:
  • Work your actions — pull the prioritized action plan Kime surfaces, create new actions, update their status, and add comments as you make progress.
  • Create prompts — add prompts in bulk and start tracking them across your models.
Write tools are clearly flagged, so your client asks for confirmation before anything runs. You grant the matching permissions when you connect, and changes always stay within your existing Kime access.

Supported platforms

The Kime MCP server works with any client that supports the Model Context Protocol, including Claude, ChatGPT, Cursor, Claude Code, VS Code (GitHub Copilot), and Windsurf.

Requirements

A Kime account with at least one active workspace, and an MCP-compatible AI tool.