Plugin Engine vs Cognigy AI MCP Management Server
A side-by-side look at the Plugin Engine and Cognigy AI MCP Management Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Plugin Engine for conversational ai work as a local process; choose Cognigy AI MCP Management Server 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?
Choose Plugin Engine when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
COGNIGY_API_BASE_URL, COGNIGY_API_KEY. - You want tools like
create_ai_agent, update_ai_agent, setup_llm.
Choose Cognigy AI MCP Management Server when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
COGNIGY_BASE_URL, COGNIGY_API_KEY, COGNIGY_DEFAULT_PROJECT_ID. - You want tools like
list_projects, list_flows, get_flow.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 61/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | COGNIGY_API_BASE_URLCOGNIGY_API_KEY | COGNIGY_BASE_URLCOGNIGY_API_KEYCOGNIGY_DEFAULT_PROJECT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 18 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 18 | 138 |
| Full listing | View Plugin Engine | View Cognigy AI MCP Management Server |
Tools & capabilities
Plugin Engine tools 18
create_ai_agentCreate a complete AI Agent with auto-provisioned flow, job node, and REST endpointupdate_ai_agentUpdate persona, guardrails, job config (role, procedures, LLM, temperature)setup_llmCreate an LLM resource (GPT-4, Claude, Mistral, etc.) with automatic connection validationtalk_to_agentSend a message to an AI Agent and get its response (uses Endpoint Test Mode, so it is not counted as billable)list_resourcesList projects, agents, flows, endpoints, LLMs, knowledge stores, and moreget_resourceGet detailed information about a single resourcedelete_resourcePermanently delete a resourcemanage_knowledgeCreate knowledge stores, add sources (URL, text, file), list chunks for RAGcreate_toolAdd a tool (HTTP, knowledge, email, MCP, A2A) to an agent's job nodeupdate_toolUpdate an existing tool node's configurationmanage_webchatCreate or configure a Webchat v3 endpoint for website deploymentmanage_flow_nodesCreate, update, delete, or list flow nodes for conversation logic- +6 more on the listing page
Cognigy AI MCP Management Server tools 138
list_projectsLists all Cognigy.AI projects accessible by your API key. Use this to discover available projects before working with flows, intents, or other resources.list_flowsLists all flows in a Cognigy.AI project. Flows are conversation logic containers. Use this to discover flows before reading or modifying them.get_flowGets detailed metadata about a specific Cognigy.AI flow. Returns flow configuration, locale info, and timestamps. Use this to inspect a flow before modifying it.get_flow_settingsGets the settings/configuration of a Cognigy.AI flow. Returns NLU settings, thresholds, and other flow-level configurations. Use this before updating flow settings.get_latest_log_entriesGets the latest execution log entries from a Cognigy.AI project. Use this for debugging flow execution, viewing errors, or monitoring agent behavior.get_nodesLists all nodes in a Cognigy.AI flow. Nodes are the building blocks of conversation logic (Say, Question, If, Code, etc.). Use this to explore flow structure before reading specific nodes or modifying the flow.get_nodeGets detailed configuration of a specific node in a Cognigy.AI flow. Returns the node's type, label, config fields, and settings. Use this to inspect node behavior before modifying it.search_nodesSearches for nodes in a Cognigy.AI flow by text content. Finds nodes containing the search term in their configuration (messages, conditions, code, etc.). Use this to locate specific content within large flows.get_node_descriptorsGets all available node types (blueprints) that can be created in a Cognigy.AI flow. Returns node type definitions including their fields, appearance, and constraints. Use this to understand what nodes can be added to a flow.list_intentsLists all intents in a Cognigy.AI flow. Intents are the NLU triggers that match user utterances to flow logic. Use this to explore NLU configuration before training or modifying intents.get_intentGets detailed configuration of a specific intent in a Cognigy.AI flow. Returns the intent's conditions, rules, confirmation sentences, and settings. Use this to inspect NLU behavior before modifying.list_endpointsLists all endpoints in a Cognigy.AI project. Endpoints are channel connectors (Webchat, REST, Voice, etc.) that expose flows/agents to users. Use this to discover deployed channels.- +126 more on 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.
Plugin Engine
{
"mcpServers": {
"cognigy-plugin-engine": {
"command": "npx",
"args": [
"-y",
"-p",
"@cognigy/plugin-engine@latest",
"cognigy-setup"
],
"env": {
"COGNIGY_API_BASE_URL": "YOUR_COGNIGY_API_BASE_URL_HERE",
"COGNIGY_API_KEY": "YOUR_COGNIGY_API_KEY_HERE"
}
}
}
}
Cognigy AI MCP Management Server
{
"mcpServers": {
"tsvetang2-cognigy-ai-mcp-management-server": {
"command": "npx",
"args": [
"cognigy-ai-mcp-management-server"
],
"env": {
"COGNIGY_BASE_URL": "YOUR_COGNIGY_BASE_URL_HERE",
"COGNIGY_API_KEY": "YOUR_COGNIGY_API_KEY_HERE",
"COGNIGY_DEFAULT_PROJECT_ID": "YOUR_COGNIGY_DEFAULT_PROJECT_ID_HERE"
}
}
}
}
Frequently asked questions
Plugin Engine is categorized under Conversational AI and uses a local stdio subprocess. Cognigy AI MCP Management Server belongs to Conversational AI and uses a local stdio subprocess. Pick Plugin Engine for conversational ai work and Cognigy AI MCP Management Server 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.
Plugin Engine is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Cognigy AI MCP Management Server is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 cognigy-plugin-engine and tsvetang2-cognigy-ai-mcp-management-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Plugin Engine has a quality signal of 61/100 (Good) with 0 views, 0 installs and 18 GitHub stars. Cognigy AI MCP Management Server has 60/100 (Good) with 3 views, 0 installs and 2 GitHub stars.