Skip to main content
Glama
RowelLewis

intacct-docs

by RowelLewis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to intacct-docs

No user-submitted related servers found.

    Related Servers

    • @octri/mcp

      OctriDev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.
      7
      179 npm
      MIT

    • Janus MCP

      DeanWard
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to understand and interact with OpenAPI specifications, providing deep insight into API structures for faster and more accurate API integration.
      9
      7 npm
      1
      MIT

    • mcp-swagger

      awssam
      A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      3 npm
      2
      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

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a distinct focus: endpoint docs, endpoint search, schema retrieval, tag/schema listings, example generation, health, and spec quality. There is minor overlap between search-endpoints and get-endpoints-by-tag, and between get-endpoint-docs and generate-example, but descriptions make the differences clear.

    Naming Consistency4/5

    Most tool names consistently follow a verb_noun pattern with lowercase hyphenation, such as get-endpoint-docs, list-tags, and search-endpoints. A few exceptions like health and spec-quality-report break the pattern slightly, but the overall style is predictable and readable.

    Tool Count5/5

    Nine tools is an appropriate size for a documentation server. The toolset covers discovery, retrieval, schema access, example generation, and operational health without feeling bloated or sparse.

    Completeness5/5

    The toolset provides a complete workflow for API documentation consumers: discovering endpoints, retrieving endpoint details, exploring schemas, listing categories, and generating examples. The addition of health and spec-quality-report tools extends the surface sensibly rather than leaving obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources