Onboarding request - cognigy-ai-mcp-management-server to be added to Github Registry

[TsvetanG2]

Hi team,

Following the guidance in #1257 (onboarding to github.com/mcp is still a manual curation step, with version sync from the OSS registry afterwards), I'd like to request onboarding for a server that's already published and validated on the open source registry.

Server details

Registry name	io.github.TsvetanG2/cognigy-ai-mcp-management-server
Version	v0.1.4
Repository	https://github.com/TsvetanG2/cognigy-ai-mcp-management-server
npm	cognigy-ai-mcp-management-server
Transport	stdio
License	MIT

What it does

It exposes the Cognigy.AI management REST API (agents, flows, endpoints, lexicons, NLU, snapshots, deployments, playbooks) as 132 granular MCP tools, so an agent can build and operate a Cognigy project end to end without leaving the client.

Why it may be worth a slot

NiCE ships an official Cognigy MCP server with a consolidated ~16-tool surface. This one takes the opposite approach deliberately: one tool per API operation, so tool selection carries the semantics instead of a dispatch parameter. The two are complementary rather than duplicates, and the granular surface is the one that works better for multi-step authoring workflows. Happy to expand on the tradeoff if that's useful for the review.

Maturity signals

• Published to the OSS registry, schema-valid, semver + maintained CHANGELOG
• Listed on MCP.so and Glama
• SECURITY.md, Dependabot, CodeQL, CONTRIBUTING.md in place
• Fixture-based CI plus live-API trial runs; documented tool reference (TOOLS.md) and a SKILL.md for client-side usage
• Read-only vs. mutating operations are separated and documented; no credentials are bundled — auth is supplied via environment variables

Happy to provide anything else the curation process needs — security notes, usage numbers, or a demo. Thanks for the work on the registry.

[TsvetanG2]

@trent-j hey, as far as I know you are the person who can answer that or at least give a hint :)