sn-community-events-mcp
Related Servers
Alternatives to sn-community-events-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for searching the ServiceNow Community forums with relevance-ranked results. Supports fetching posts as Markdown and configurable result counts.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server to interact with ServiceNow instances, enabling ITSM, CMDB, workflow, and knowledge search operations.MIT
- AlicenseAqualityCmaintenanceAn MCP server for interacting with a ServiceNow instance via its Table API, enabling CRUD operations on incident, request, and requested item tables, as well as generic operations on any table by name.22MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for searching and reading ServiceNow documentation from a local clone, enabling keyword/regex queries and full doc retrieval without external APIs.-
- AlicenseAqualityAmaintenanceAn MCP server that enables running commands against a ServiceNow instance via its REST APIs, including Table, Aggregate, Attachment, Import Set, Batch, CMDB, Service Catalog, Change Management, and Knowledge APIs.1968 npm8MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.7MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clear and singular, so an agent can unambiguously select it for any community events query.
The single tool name 'get_community_events' follows a clear verb_noun pattern. There are no other tool names to compare, so consistency is perfect within the server.
A single tool might feel thin, but this server's scope is narrowly defined around fetching ServiceNow community events. The tool itself is feature-rich with many optional filters and output options, so it earns its place.
For the stated purpose of retrieving community events, the tool covers all necessary operations: filtering by date, status, location, product, type, and optional full descriptions or CSV export. There are no obvious dead ends or missing capabilities for a read-only events retrieval server.