Skip to main content
Glama
hyperspell

hyperspell-mcp

Official
by hyperspell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hyperspell-mcp

No user-submitted related servers found.

    Related Servers

    • 0nMCP

      Crypto-Goatz
      A
      license
      Not graded
      quality
      D
      maintenance
      A universal AI API orchestrator that connects to 17+ services (Stripe, Slack, GitHub, etc.) and enables natural language task execution, multi-step automation, and complex orchestration across them without coding.
      228 npm
      1
      MIT

    • 0nMCP

      0nork
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Universal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.
      228 npm
      5
      -

    • Bellink MCP Server

      barflotek
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to over 30 business tools like Gmail, Slack, and Airtable through a single unified interface. It enables users to perform actions across multiple platforms using natural language without managing individual API integrations.
      24 npm
      MIT
    • Open Enterprise AI MCP Server by enthrium

      Open Enterprise AI MCP Serverofficial

      enthrium
      F
      license
      Not graded
      quality
      A
      maintenance
      Connects AI coding assistants like Claude Code, Cursor, and Windsurf to enterprise data sources (databases, files, APIs, etc.) via a single binary, with 45+ connector categories and built-in memory tools.
      1
      -
    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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: adding content (files/memories), retrieving collections/documents, and searching. No overlap exists, as tools target specific resources and actions like 'Add File' vs. 'Add Memory' or 'Get Collection' vs. 'Get Document'.

    Naming Consistency3/5

    Naming is mixed with inconsistent patterns: 'Add File' and 'Add Memory' use verb-noun but with capital letters, while 'Get Collection', 'Get Document', 'List Collections', and 'Search Hyperspell' use verb-noun with varying capitalization and one tool including the server name. This makes it readable but lacks a uniform convention.

    Tool Count5/5

    With 6 tools, the count is well-scoped for a document management server, covering core operations like adding, retrieving, listing, and searching without being too sparse or bloated. Each tool earns its place in the workflow.

    Completeness4/5

    The toolset covers essential CRUD-like operations for a document repository: adding content, retrieving collections/documents, and searching. Minor gaps exist, such as no update or delete tools, but agents can likely work around this for basic usage without significant failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources