EDDI vs Plugin Engine
A side-by-side look at the EDDI and Plugin Engine MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
EDDIConversational AIConfig-driven engine that turns JSON into production-grade AI agents. Multi-agent orchestration, 12+ LLM providers, MCP/A2A protocols, RAG, persistent memory, and enterprise compliance (EU AI Act, GDPR, HIPAA). Built on Quarkus.49FairAuth: not declaredVerdict: choose EDDI for conversational ai work; choose Plugin Engine 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E EDDI | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 49/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | COGNIGY_API_BASE_URLCOGNIGY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 387 | 18 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View EDDI | View Plugin Engine |
Tools & capabilities
EDDI tools
No tool names declared yet. Check the project README from the listing page.
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
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.
EDDI
No confirmed install command for EDDI yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}
Frequently asked questions
EDDI is categorized under Conversational AI and uses an install path we have not confirmed yet. Plugin Engine belongs to Conversational AI and uses a local stdio subprocess. Pick EDDI for conversational ai work and Plugin Engine 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. EDDI has no confirmed install command yet — follow its own setup instructions.
EDDI has no declared pricing — check the project's own site. Plugin Engine 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 eddi and cognigy-plugin-engine as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EDDI has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 387 GitHub stars. Plugin Engine has 61/100 (Good) with 0 views, 0 installs and 18 GitHub stars.