A
licenseNot graded
qualityD
maintenanceEnables AI assistants to interact with ServiceNow instances for data retrieval, record management, and workflow execution via the ServiceNow API.
MIT
Fluent MCP Server
by modesty
Related Servers
Alternatives to Fluent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and development tools to interact with ServiceNow instances through the Model Context Protocol, supporting incident, change, problem, CMDB, service catalog, knowledge base, and custom table operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and development tools to interact with ServiceNow instances through a standardized interface, supporting comprehensive API coverage for incident, change, CMDB, and more.MIT
- AlicenseAqualityAmaintenanceEnables AI coding agents to build, evaluate, and validate ServiceNow Next Experience UI Framework components and projects, helping keep component code and now-ui.json manifests in sync while using live instance API metadata.11232 npm9MIT
- AlicenseAqualityDmaintenanceEnables natural language interaction with ServiceNow instances for managing incidents, changes, CMDB, service catalog, users, groups, and knowledge base via MCP.4126 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with ServiceNow instances through the ServiceNow API, supporting record management, service catalog operations, change management, and more via natural language.MIT
TDQS
A3.9/5.0
Scored across 17 tools
Disambiguation3/5
Most lifecycle tools are clearly distinct (init, build, pack, deploy, clean), but the documentation/help cluster—explain_fluent_api, get-api-spec, get-instruct, get-snippet, and sdk_info—has overlapping purposes that could cause misselection. The descriptions do include cross-references, which helps, but an agent still has to choose among several similar look-up tools.
Naming Consistency2/5
The core lifecycle tools mostly follow a verb_fluent_noun pattern (build_fluent_app, deploy_fluent_app, download_fluent_app), but conventions are mixed across the set: several get-* tools use hyphens with no 'fluent' component, fluent_transform reverses the pattern, check_auth_status omits 'fluent', and sdk_info is a bare noun. This mixing of underscore, hyphen, and noun-only names is inconsistent.
Tool Count4/5
At 17 tools, this sits slightly above the ideal 3-15 range, but the server covers a broad domain: app initialization, building, packaging, deployment, downloads, transforms, CI/CD, testing, authentication, and documentation. The count feels justified by the scope rather than padded.
Completeness5/5
The tool surface covers the full Fluent/ServiceNow app development lifecycle: init, dependencies, build, pack, deploy, clean, download, transform, query, CI/CD, test, and auth. There are no obvious dead ends, and documentation/help tools round out the workflow. The set appears complete for its stated domain.
Maintenance
ActivityActive
ResponsivenessNo issues