CB Insights MCP Server
OfficialThe CB Insights MCP Server enables AI agents to interact with CB Insights' ChatCBI LLM through the Model Context Protocol (MCP) standard for querying business intelligence data.
Key Capabilities:
Send messages to ChatCBI: Submit queries to receive intelligent, AI-generated responses with business insights
Maintain conversation context: Continue existing conversations by providing a chat ID from previous interactions, or start fresh sessions without one
Access comprehensive responses: Receive structured data including the message content, related references, source citations, suggested follow-up questions, and conversation titles
Query business intelligence: Leverage CB Insights' data through natural language queries
Integration & development: Designed for AI agent frameworks with support for testing and debugging using the MCP inspector tool
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CB Insights MCP ServerWhat are the latest trends in fintech startups?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CB Insights MCP Server
Deprecation notice: This repository, serving as an example implementation of a simple self-hosted MCP server that acts as a pass-through to the CB Insights API, is deprecated as of January 2026. CB Insights is pleased to offer a fully supported MCP server at mcp.cbinsights.com, which can be invoked programmatically or through clients like ChatGPT, Claude, and Microsoft Copilot.
The CBI MCP Server provides an interface for developers to interact with CB Insights ChatCBI LLM through AI Agents.
Tools
ChatCBI
Send a message from an agent to ChatCBI and return the response.
Input parameters:
message: The content of your message to ChatCBIchatID(optional): A unique identifier for the chat session, obtained from a previous response. If included, the conversation is continued. Otherwise, a new conversation is started.
Returns JSON object containing the following fields:
chatID: Identifies the conversation. If chatID was provided in the request, this will be the same.message: ChatCBI response to the message.relatedContent: List of related references.sources: List of sources used to generate the response.suggestions: List of suggested follow-up questions.title: Title of the chat
For more information see Using ChatCBI
Related MCP server: ElevenLabs MCP Server
Setup
The CBI MCP Server uses uv to manage the project.
Environment variables are set via the .env file:
CBI_CLIENT_ID&CBI_CLIENT_SECRETOAuth Client ID and Secretsee CB Insights API Authentication for usage and how to obtain them
CBI_MCP_TIMEOUT(default: 120)CBI_MCP_PORT(default: 8000)
Usage
With Claude Desktop
Update the claude_desktop_config.json file using the following command:
mcp install server.pyThis will add the following configuration:
{
"mcpServers": {
"cbi-mcp-server": {
"command": "/path/to/.local/bin/uv",
"args": [
"--directory",
"/path/to/cloned/cbi-mcp-server",
"run",
"server.py"
]
}
}
}Debugging
The inspector can be used to test/debug your server.
mcp dev server.py Available Tools
1 toolChatCBICRead-only
When using this tool, provide clear, specific queries for the best results. You can continue conversations with ChatCBI by including the chat ID from previous interaction.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | ||
| chat_id | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true and openWorldHint=true, indicating safe read operations with open-ended capabilities. The description adds valuable context about chat continuation (multi-turn conversations) and query specificity requirements, which goes beyond what annotations provide. No contradiction with annotations exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately concise with two focused sentences. The first sentence provides usage advice, the second explains chat continuation. No wasted words, though it could be more front-loaded with the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a chat tool with 2 parameters, 0% schema coverage, no output schema, and no sibling tools, the description is insufficient. It doesn't explain what the tool does, what 'CBI' refers to, expected response format, or error conditions. The annotations help but don't compensate for the description's gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate but fails to explain parameter meanings. It mentions 'chat_id' for continuing conversations, giving some context for that parameter, but doesn't explain what 'message' represents or its format. The description adds minimal value beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description fails to state what the tool actually does - it only provides usage advice ('provide clear, specific queries') and mentions chat continuation capability. The name 'ChatCBI' suggests a conversational interface, but the description doesn't explicitly state this is a chat/query tool. It's tautological in that it mentions 'using this tool' without explaining its function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage guidance about query specificity and chat continuation, but doesn't explain when to use this tool versus alternatives (though there are no sibling tools). It mentions including chat_id for continuing conversations, which gives context about multi-turn interactions, but lacks explicit when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
ChatCBI
TDQS
With only one tool, there is no possibility of ambiguity or confusion between tools. The tool has a single, clear purpose: interacting with the ChatCBI system.
A single tool inherently has perfect naming consistency. There are no other tools to compare against, so no inconsistency can exist.
One tool is too few for a server with a broad purpose like 'CB Insights MCP Server', which suggests access to a data/analytics platform. A single chat interface tool feels thin and incomplete for this domain scope.
The server appears to provide access to CB Insights data/analytics, but only offers a single chat interface tool. This is severely incomplete—missing core operations like data retrieval, report generation, search, or specific query endpoints that would be expected for such a platform.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Create and manage AI agents that collaborate and solve problems through natural language interacti…
AI agents use CalmBoard MCP to access board data, tasks, insights, and project workflows.
- UproarOAuthchat.uproar
Chat where AI agents are first-class members, with their own identity and permissions.
1 Connect AI agents to CloudBees Unify: feature flags, CI/CD, release orchestration, and security
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceAllows users to integrate their custom Quickchat AI Agents into various AI applications (Claude Desktop, Cursor, VS Code, etc.) through the Model Context Protocol, enabling AI-to-AI interactions.24MIT
- AlicenseNot gradedqualityDmaintenanceEnables seamless integration with ElevenLabs Conversational AI to manage agents, tools, and knowledge base sources. It supports RAG indexing, webhook integration, and document management for building advanced voice-enabled AI agents.MIT
- AlicenseBqualityDmaintenanceEnables users to interact with Cube's AI agent for real-time analytics and data exploration through a chat interface. It supports generating data visualizations, performing SQL queries, and analyzing trends using natural language.13813MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with the Coherence Network platform, allowing them to browse ideas, record contributions, and access governance features via natural language.3Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cbinsights/cbi-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server