crisp-plugin-mcp
Related Servers
Alternatives to crisp-plugin-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes app-registered tools as an MCP server for OpenClaw, forwarding actual tool execution back to the app over a WebSocket bridge.-
- AlicenseNot gradedqualityCmaintenanceA local stdio MCP server that lets admins and token holders query and modify PingCode content — projects and dictionaries, work items with comments and relations, and Wiki pages — through eleven fixed tools backed by the official PingCode public-cloud REST API. Writes are limited to creating/updating work items, adding comments and relations, and creating Markdown pages, with dry-run previews and enterprise (client credentials) or personal access token authentication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables external AI applications to access MCP tools by providing a user-hosted HTTPS endpoint that forwards requests to a paired desktop client.MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, mints agent keys, and shares a unified tool library across multiple AI harnesses.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to access remote and local MCP servers plus HTTP APIs through a single MCP endpoint, with per-consumer scoped tokens, tool-level permissions, and encrypted secret management.5AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
TDQS
Scored across 42 tools
Most tools target clearly distinct resource+action pairs, and descriptions actively disambiguate the tricky ones (e.g. list_latest_conversations vs search_conversations, list_helpdesk_pages vs list_helpdesk_tree). The main risk is the parallel set_conversation_* vs update_people_profile_* families, which operate on different resources but look similar at a glance.
Nearly all tools follow a snake_case verb_noun pattern (list_, get_, update_, create_, delete_, search_). Minor deviations exist: 'change_conversation_state' and 'move_conversation_inbox' use different verbs than the set_/update_ families for analogous metadata operations, and 'send_conversation_message_text' has an unusual noun ordering.
42 tools is heavy for a single MCP server and exceeds the 25+ threshold where surface area becomes a burden. While the domain is broad (helpdesk, conversations, CRM, workspace), several granular getters/setters (title, metadata, content, email, phone) could be consolidated.
Coverage is strong across Knowledge Base CRUD, conversation lifecycle (list/search/get/messages/send/state/inbox), CRM profiles, and workspace info. Gaps remain: no create/delete for conversations or people profiles, and no operator management beyond listing.