Chatbase vs Inbed
A side-by-side look at the Chatbase and Inbed MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ChatbaseConversational AIManage Chatbase agents, sources, conversations and help-desk tickets.40FairAuth: not declaredVerdict: choose Chatbase for conversational ai work; choose Inbed for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Chatbase when
- You need dedicated capabilities in the Conversational AI domain.
Choose Inbed when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Chatbase | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 40/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 25 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Chatbase | View Inbed |
Tools & capabilities
Chatbase tools
No tool names declared yet. Check the project README from the listing page.
Inbed 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.
Chatbase
No confirmed install command for Chatbase yet — follow the setup steps linked from its listing page rather than a guessed package name.
Inbed
{
"mcpServers": {
"inbed": {
"command": "npx",
"args": [
"-y",
"mcp-inbed-dating"
]
}
}
}
Frequently asked questions
Chatbase is categorized under Conversational AI and uses an install path we have not confirmed yet. Inbed belongs to Conversational AI and uses a local stdio subprocess. Pick Chatbase for conversational ai work and Inbed for conversational ai.
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. Chatbase has no confirmed install command yet — follow its own setup instructions.
Chatbase has no declared pricing — check the project's own site. Inbed has no declared pricing — check the project's own site. 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 chatbase and inbed as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatbase has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Inbed has 47/100 (Fair) with 0 views, 0 installs and 25 GitHub stars.