Corebee — AI Customer Support vs Quickchat AI MCP
A side-by-side look at the Corebee — AI Customer Support and Quickchat AI MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Corebee — AI Customer Support for support & service management work over a hosted endpoint; choose Quickchat AI MCP for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Corebee — AI Customer Support when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
Choose Quickchat AI MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SCENARIO_ID, API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | SCENARIO_IDAPI_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 24 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Corebee — AI Customer Support | View Quickchat AI MCP |
Tools & capabilities
Corebee — AI Customer Support tools
No tool names declared yet. Check the project README from the listing page.
Quickchat AI MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Corebee — AI Customer Support
{
"mcpServers": {
"corebee-ai-customer-support": {
"url": "https://corebee.ai/api/v1/mcp/stream"
}
}
}
Quickchat AI MCP
{
"mcpServers": {
"incentivai-quickchat-ai-mcp": {
"command": "uvx",
"args": [
"quickchat-ai-mcp"
],
"env": {
"SCENARIO_ID": "YOUR_SCENARIO_ID_HERE",
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Corebee — AI Customer Support is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Quickchat AI MCP belongs to Support & Service Management and uses a local stdio subprocess. Pick Corebee — AI Customer Support for support & service management work and Quickchat AI MCP for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Corebee — AI Customer Support has no declared pricing — check the project's own site. Quickchat AI MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add corebee-ai-customer-support and incentivai-quickchat-ai-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Corebee — AI Customer Support has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Quickchat AI MCP has 48/100 (Fair) with 3 views, 0 installs and 24 GitHub stars.