Skip to main content
Glama
frlorenzon

MCP Sienge Node

by frlorenzon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Sienge Node

No user-submitted related servers found.

    Related Servers

    • omie-mcp

      thiagoorodrigues
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Omie API to list products, consult clients, and create budgets
      15 npm
      MIT

    • MCP Server Node

      BIGBANGMARKET
      A
      license
      Not graded
      quality
      C
      maintenance
      A Node.js MCP server with user, task, and calculator tools. Supports Bearer token authentication and Docker/Cloudtype deployment.
      4 npm
      MIT

    • mcp-sei-cbm

      hugocoliveira
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for integrating and automating the SEI (Sistema Eletrônico de Informações) with direct user/password authentication, enabling process management, document reading, advanced search, and unit switching.
      -

    • MCP Server Node

      YogiboKorea
      A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js MCP server example with user management, task management, and calculator tools. Supports authentication via bearer token and can be deployed locally or via Docker.
      4 npm
      MIT

    • octo-mcp-server

      bscarberry
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server built with Node.js and Express that supports remote deployment via HTTP and SSE. It provides a modular framework for building and scaling tools while serving multiple clients concurrently.
      -

    • Siigo MCP Server

      crisgon0295
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides full integration with the Siigo API, enabling access to Colombian accounting software features including products, customers, invoices, quotations, purchases, credit notes, vouchers, payment receipts, journals, webhooks, and more.
      44
      80 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    The two authentication tools (testar_conexao and verificar_autenticacao) are similar but explicitly cross-referenced to clarify their distinct purposes: one tests real API access, the other inspects configuration. The remaining three tools each target a clearly unique aspect (quotas, process explanation, and loading purchasing tools), so overall ambiguity is low.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: testar_conexao, verificar_autenticacao, consultar_cota, explicar_processo_compras, carregar_compras. This uniform structure makes the set predictable and easy to navigate.

    Tool Count5/5

    With 5 tools, the server is well within the ideal 3-15 range. Each tool serves a distinct purpose—auth testing, auth config, quota checking, process explanation, and loading purchase tools—so the count is appropriate for a focused Sienge integration server.

    Completeness2/5

    The tool set lacks direct CRUD or query operations for core Sienge resources like purchase orders, suppliers, or invoices, which are essential for a purchasing-focused server. The description of explicar_processo_compras explicitly states that not every stage of the procurement process is covered, and carregar_compras hints at additional tools that are not actually exposed, leaving significant functional gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources