
Cognigy Ai Mcp Management Server
io.github.TsvetanG2Published by GitHub account TsvetanG2v0.2.1Updated Oct 24, 2026
MCP server for Cognigy.AI - 132 tools to build, configure & operate conversational AI agents
Overview
Local MCP server that lets an assistant build, configure, test and operate Cognigy.AI conversational AI agents through 132 Management API tools.
- What you can do
- Manage projects, flows, nodes, intents and NLU training, including scoring and audit checks. Run playbooks and regression tests, and inject or reset conversation sessions. Create, restore, diff and promote snapshots, and create, merge, upload or download packages. Configure LLMs, NLU connectors, Knowledge AI stores and sources, functions and extensions. Handle contact profiles, analytics, audit logs, live-agent handover and organization-wide search. Track long-running async tasks and paginate list results.
- When to use it
- For developers, solution architects and partners who build on Cognigy.AI and want to script agent changes, run NLU training and regression tests, or promote snapshots and packages across environments from an AI assistant instead of the Cognigy UI.
- Requirements
- Node.js 20 or higher, plus the separately installed @cognigy/rest-api-client peer dependency. A Cognigy.AI account with API access (Trial, SaaS or on-premises). Environment variables COGNIGY_BASE_URL and COGNIGY_API_KEY are required; COGNIGY_DEFAULT_PROJECT_ID is optional. Network access to the Cognigy API endpoint.
Installation
In SourceWeft
- Open Cognigy Ai Mcp Management Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Cognigy.AI Management MCP Server
[CI] [npm version] [npm downloads] [node] [License: MIT] [Glama Score] [MCP Registry] [MCP Badge]
[cognigy-ai-mcp-management-server]
Model Context Protocol server for managing Cognigy.AI virtual agents through the Management API
This is an independent, open-source MCP server and is not affiliated with, endorsed by, or sponsored by Cognigy or NiCE. It requires your own valid Cognigy.AI account and API key, used in accordance with Cognigy's commercial license terms. "Cognigy" and "Cognigy.AI" are trademarks of their respective owners.
What is this?
cognigy-ai-mcp-management-server is a local MCP server that enables AI coding assistants (Claude, Cursor, etc.) to build, configure, test, and operate Cognigy.AI conversational AI agents programmatically.
Instead of clicking through the Cognigy UI, you can now:
- Create and manage flows, nodes, and intents via natural language
- Run NLU training and regression tests automatically
- Deploy snapshots and packages across environments
- Configure LLMs, Knowledge AI, and integrations
Built for: Developers, solution architects, and SI partners who build on Cognigy.AI.
Requirements
- Node.js 20.0.0 or higher
- Cognigy.AI account with API access (Trial, SaaS, or on-premises)
- API Key generated from Cognigy UI (My Profile → API Keys)
Installation
Important: The @cognigy/rest-api-client package is licensed under "Cognigy Proprietary License". By installing it, you agree to Cognigy's license terms.
Configuration
Set environment variables before running:
Common Base URLs:
MCP Client Configuration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Claude Code
Add to .mcp.json in your project root:
Cursor
Add to .cursor/mcp.json:
Available Tools
This server provides 132 MCP tools organized by domain:
Key Features
- Safe by default: All mutating tools use
dryRun: trueby default - Async-aware: Long-running operations poll until completion
- Security: API keys only in memory, secrets automatically redacted
- Pagination: All list operations support
limitandskip
Development & Testing
Live API Testing
Build
Regenerate Types (optional)
If you need to update the generated types from a newer Cognigy API:
Important: Dependencies
This package requires @cognigy/rest-api-client as a peer dependency. This means:
- You must install it separately (see Installation above)
- You accept Cognigy's license terms by installing their package
- We do not bundle or redistribute any Cognigy code
You are responsible for:
- Reviewing and accepting Cognigy's proprietary license terms
- Having appropriate rights to use the Cognigy API
- Keeping your API credentials secure
The Cognigy REST API client is the official SDK maintained by Cognigy GmbH and is published on npm under "Cognigy Proprietary License".
License
This MCP server is released under the MIT License. See LICENSE for details.
Note: The MIT license applies only to this MCP server code. Dependencies (particularly @cognigy/rest-api-client) are subject to their own licenses.
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Follow existing code patterns (Zod schemas, dryRun flags, etc.)
- Add tests for new tools
- Run
npm test && npm run buildbefore committing - Submit a Pull Request
Development Guidelines
- All tools must have Zod input validation
- Mutating tools must support
dryRunflag (default: true) - Tool descriptions should be LLM-friendly (1-2 sentences)
- Never log or expose API keys/secrets
- Test against mock server before live API
Support
- Issues: GitHub Issues
- Cognigy Docs: docs.cognigy.com
- MCP Spec: modelcontextprotocol.io
Built with Model Context Protocol SDK
Source: README.md at commit e647397
Tools
0Version history
3- v0.2.1LatestOct 5, 2026
- v0.2.0Oct 4, 2026
- v0.1.4Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts