Quickchat AI MCP logo

Quickchat AI MCP

by incentivai

Connects Quickchat AI agents to MCP-compatible apps for Knowledge Base access and open-ended conversations.

Install Quickchat AI MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "incentivai-quickchat-ai-mcp": {
      "command": "uvx",
      "args": [
        "quickchat-ai-mcp"
      ],
      "env": {
        "SCENARIO_ID": "YOUR_VALUE_HERE",
        "API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx quickchat-ai-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The incentivai/quickchat-ai-mcp MCP server exposes a Quickchat AI Agent to compatible AI applications through Model Context Protocol. It uses a scenario ID and, when enabled, an API key to connect the client to a configured Quickchat AI agent and its Knowledge Base. Reach for it when an agent needs to consult Quickchat content or exchange messages with a conversational agent from Claude Desktop, Cursor, Windsurf, or another MCP client. Configuration and MCP metadata are managed in the Quickchat AI dashboard.

Use cases

  • Connect a Quickchat AI Knowledge Base to Claude Desktop
  • Ask a configured Quickchat AI Agent questions from Cursor
  • Share a public MCP configuration without exposing an API key
  • Review AI-to-AI conversation transcripts in Quickchat Inbox

Key features

  • Expose Quickchat AI Agents through MCP
  • Access a configured Knowledge Base
  • Support open-ended agent conversations
  • Manage MCP metadata from the Quickchat dashboard
  • View interaction transcripts in Quickchat Inbox

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

22/22 checks healthy over the last 84d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · quickchat-ai-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars24Stargazers on the source repository.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Quickchat AI MCP works

What incentivai/quickchat-ai-mcp MCP server does

The incentivai/quickchat-ai-mcp MCP server connects a Quickchat AI Agent to applications that support the Model Context Protocol. It gives an AI application access to the agent's configured Knowledge Base, capabilities, and conversational behavior rather than exposing a fixed, narrowly defined utility.

This is useful when an organization has already configured an agent in Quickchat AI and wants another AI application to interact with it. The connected application can send messages to the Quickchat agent, while the Quickchat AI dashboard remains the place to manage the agent's knowledge, settings, MCP name, description, and optional command information.

The project documentation names Claude Desktop, Cursor, VS Code, and Windsurf as example client applications. Compatibility with other clients depends on their MCP support and configuration process.

How it works

After creating a Quickchat AI account and configuring an agent, activate MCP from the Quickchat AI application. The MCP setup supplies a scenario ID and an API key when authentication is enabled. An MCP-compatible client then starts the local package and passes those values as environment variables.

The incentivai/quickchat-ai-mcp MCP server uses the scenario ID to identify the Quickchat AI configuration. The API key protects access when the Quickchat MCP integration requires one. Quickchat's MCP page provides the client configuration snippet with the relevant MCP name and values.

The interaction is not limited to a preselected static tool. Instead, the client can communicate with the configured Quickchat AI Agent through its conversational interface. Conversations can be viewed in Quickchat Inbox, although the recorded transcript represents the interaction between the two AI systems and may not exactly match the end user's original messages.

Setup and configuration

Create a Quickchat AI account, start the available trial, and configure the agent's Knowledge Base, capabilities, and settings. Activate MCP in the Quickchat AI dashboard, then provide its name, description, and optional command. These details help client applications determine when the MCP should be used.

Install uv first. For Claude Desktop or Cursor, run the package with uvx using the package name quickchat-ai-mcp. The client configuration includes:

  • SCENARIO_ID: the Quickchat AI scenario identifier.
  • API_KEY: the Quickchat AI API key when the MCP integration requires authentication.

To share the MCP with other users without exposing a secret, disable the Quickchat MCP page's “Require API key” option and distribute a configuration containing only the scenario ID. The documentation explicitly warns against publishing the Quickchat API key.

Tools and capabilities

The incentivai/quickchat-ai-mcp MCP server provides:

  • Access to the configured Quickchat AI Knowledge Base.
  • Conversation with a Quickchat AI Agent through an MCP-compatible client.
  • Agent behavior governed by Quickchat AI capabilities and settings.
  • MCP metadata management through the Quickchat AI dashboard.
  • Conversation visibility through Quickchat Inbox.

Limitations and notes

Client setup varies outside the documented Claude Desktop and Cursor examples. Public configurations can omit the API key only after the Quickchat MCP integration is configured not to require one. The repository does not state a software license or provide standalone service pricing details.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Quickchat AI MCP

Install uv, then configure the client to run `uvx` with the `quickchat-ai-mcp` package.

Yes. The README provides Claude Desktop configuration using `uvx`, `SCENARIO_ID`, and `API_KEY`.

Yes. Cursor is documented as a supported example and uses the same package and environment variables.

Yes, if you turn off the Quickchat MCP page's “Require API key” option. The shared configuration should then contain the scenario ID without the API key.

It connects an MCP-compatible AI application to a configured Quickchat AI Agent, including its Knowledge Base, capabilities, and conversational behavior.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQuickchat AI MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/incentivai-quickchat-ai-mcp?style=directory)](https://allmcps.com/mcp/incentivai-quickchat-ai-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/incentivai-quickchat-ai-mcp"><img src="https://allmcps.com/api/badge/incentivai-quickchat-ai-mcp?style=directory" alt="Quickchat AI MCP on AllMCPs" /></a>