Skip to main content
Glama
TheOctMind

Super Fireberry MCP

by TheOctMind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Super Fireberry MCP

No user-submitted related servers found.

    Related Servers

    • Method CRM MCP Server

      avisangle
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server for Method CRM API integration. It enables LLMs to interact with Method CRM data through tools for tables, files, users, events, and API key management.
      3
      MIT

    • analytics-mcp

      bhavya998
      A
      license
      A
      quality
      C
      maintenance
      A production-grade MCP server for enterprise sales analytics, enabling LLM clients to query, analyze, and visualize sales data from a SQLite database through structured tools, resources, and prompts.
      6
      MIT

    • AI Business MCP Server

      sohaggain
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-style MCP server exposing six business tools (web search, database, CRM, email, calendar, analytics) to AI clients via a secure, authenticated interface, with mock mode and a reference agent client.
      MIT

    • Salesmate MCP Server

      arnav-chauhan-kgpian
      A
      license
      A
      quality
      C
      maintenance
      A production-ready MCP server that exposes the Salesmate CRM to Claude Desktop, enabling search, update, and creation of contacts, deals, tasks, notes, and activities.
      8
      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 5 tools

    Disambiguation5/5

    Each tool addresses a clearly distinct layer: object metadata, field metadata, record search, record mutations, and relationship traversal. Even though query and get_related_records both return records, their purposes are separated by general filtered search versus direct linked-record navigation.

    Naming Consistency3/5

    The get_objects, get_fields, and get_related_records tools follow a consistent get_ prefix, but query is a bare noun/verb and manage_record uses a generic 'manage' verb. The naming is readable but mixes conventions rather than following a uniform verb_noun pattern.

    Tool Count5/5

    Five tools is a well-scoped count for a CRM MCP server. Each tool covers a major capability—discovery, metadata, search, mutations, and relationships—without unnecessary fragmentation or overwhelming breadth.

    Completeness4/5

    The tool set covers metadata discovery, record creation/updating/deletion, complex search, and relationship traversal, which covers core CRM workflows. Minor gaps exist, such as no explicit single-record fetch and no relationship mutation tools, but query and manage_record can likely work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources