Skip to main content
Glama
Sign In
cognigy-ai-mcp-management-server

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

Related Servers

Alternatives to cognigy-ai-mcp-management-server

  • Cognify MCP Server

    S3YED
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables document ingestion and typed knowledge graph queries through Claude MCP tools, allowing agents to extract, store, and retrieve typed entities and relations from documents.
    2
    MIT

Related Servers

  • MCP Starter

    instructa
    A
    license
    D
    quality
    D
    maintenance
    A foundation for building custom local Model Context Protocol (MCP) servers that provide tools accessible to AI assistants like Cursor or Claude Desktop.
    1
    37
    MIT

  • tool-mcp-server

    maple-awa
    A
    license
    C
    quality
    D
    maintenance
    A Model Context Protocol server exposing 58 online tools (crypto, data, image, text, etc.) and workflow execution, enabling MCP clients like Claude Desktop to invoke them via natural language.
    58
    5 npm
    MIT

  • routine-mcp

    rskmanz
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
    4 npm
    -

  • OpenAI Agents MCP Server

    lroolle
    F
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.
    4
    10
    -
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.5/5.0

Scored across 138 tools

Disambiguation3/5

Most tools have distinct purposes, but several pairs overlap noticeably (e.g., score_utterance vs generate_nlu_scores both score utterances against NLU intents; create_package, package_snapshot, and promote_snapshot all package resources). Descriptions help, but with 138 tools the agent can still misselect among similar-sounding operations.

Naming Consistency5/5

Every tool follows a consistent snake_case verb_noun pattern (e.g., list_flows, get_node, create_intent, delete_knowledge_store). Minor variations like get_nodes vs get_node are natural, and no mixed conventions appear.

Tool Count1/5

138 tools far exceeds reasonable bounds for an agent-facing server, even given Cognigy.AI's broad platform. This extreme count creates a high cognitive load and increases selection errors, matching the rubric's 50+ tools criterion for an extreme mismatch.

Completeness3/5

Coverage is broad across many resources (NLU, knowledge, contacts, snapshots, packages, functions, LLMs), but notable gaps exist: no create_flow/update_flow/delete_flow, no create_endpoint/update_endpoint/delete_endpoint, and no update_flow_settings. These missing core CRUD operations for central resources limit end-to-end management workflows.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources