Skip to main content
Glama
jshsakura

mfa-servicenow-mcp

by jshsakura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mfa-servicenow-mcp

No user-submitted related servers found.

    Related Servers

    • savia-mcp

      puchocapo95-svg
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes SAVIA, a legacy travel-industry ERP with no public API, as tools an AI assistant can use. It uses Playwright to operate the browser, enabling read-only extraction of information like screenshots, text, and tables.
      -

    • auth-vault

      borysttk
      A
      license
      B
      quality
      C
      maintenance
      MCP server for secure credential management, browser-based login automation, and TOTP/2FA auto-solving. Encrypts credentials with AES-256-GCM and automates login flows via Playwright.
      32
      2
      MIT

    • mcp-browser-automation

      ritesh-jain
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for generic browser automation using Playwright. Enables MCP clients to navigate pages, inspect elements, execute JavaScript, capture screenshots, and monitor console logs and network traffic via a headless Chromium instance.
      7
      5 npm
      ISC

    • kilogent-browser

      codebridger
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 32 tools

    Disambiguation3/5

    Many tools are distinct by domain (logs, schema, attachments, workflows, scripted REST), but several portal/server-code tools overlap heavily: get_widget_bundle, get_portal_component_code, download_portal_sources, download_app_sources, get_metadata_source, and search tools all retrieve related source. Descriptions often explicitly disambiguate (e.g. sn_query as last resort, manage_workflow legacy-only), but an agent still has to choose carefully among multiple source-fetching paths.

    Naming Consistency3/5

    Most names follow verb_noun or manage_* patterns, but the set mixes sn_ abbreviations, noun-first names like sn_schema/sn_health, and several verb families (get_, search_, download_, manage_, analyze_, trace_). The conventions are readable but not fully predictable across all 32 tools.

    Tool Count2/5

    32 tools is heavy for a single MCP server and exceeds the 25+ threshold where count typically becomes a burden. While ServiceNow is broad, several tools cover overlapping retrieval/search/portal-source workflows rather than clearly separate tasks, suggesting the surface could be consolidated.

    Completeness3/5

    The surface covers many ServiceNow dev/admin areas: schema, query/aggregation, server code, portal sources/pages/widgets, logs, workflows/flows, deployments, script includes, and attachments. However, lifecycle coverage is uneven: portal pages/widgets largely support read/analysis/download/diff rather than create/update/delete, Flow Designer is read-only, and deployment verification/export lacks an obvious apply/import operation.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources