Skip to main content
Glama
mnicole-dev

@mnicole-dev/erezo-mcp-server

by mnicole-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @mnicole-dev/erezo-mcp-server

No user-submitted related servers found.

    Related Servers

    • addevent-mcp-server

      UtahREIA
      F
      license
      A
      quality
      B
      maintenance
      MCP server that wraps the AddEvent Calendar & Events API v2, allowing Claude to create, search, retrieve, update, and delete events, calendars, and RSVP attendees, plus list timezones.
      16
      -

    • eranfinish/ezatwork-mcp

      eranfinish
      F
      license
      A
      quality
      D
      maintenance
      MCP server for EZ@Work — manage clients, projects, time entries, and invoices from Claude through natural conversation. OAuth 2.1 with Google sign-in, multi-currency support.
      5
      -

    • clio-mcp

      lawyered0
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Clio Manage legal practice management software that enables Claude and other MCP clients to read and write Clio data including contacts, matters, and activities directly from chat.
      8
      MIT

    • pipedriver

      vaibhavpandeyvpz
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Pipedrive API v2, enabling management of deals, persons, organizations, products, activities, and pipelines through natural language in MCP clients like Cursor and Claude Desktop.
      47 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

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools are mostly distinct with clear CRUD actions for contacts and events. The only potential confusion is between list_contacts and search_contacts, as both allow searching contacts, but list_contacts is more comprehensive with filters and pagination while search_contacts is a quick search. This is a minor overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern using snake_case, such as list_contacts, get_event, register_event, and get_me. The pattern is uniform and predictable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for its apparent purpose of contact and event management. Each tool serves a distinct function, and the count fits within the ideal 3-15 range.

    Completeness5/5

    The contact domain has full CRUD plus search, and the event domain covers listing, retrieval, registration, and unregistration. get_me provides user context. No obvious missing operations for the intended workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources