Skip to main content
Glama
jitheshb83

jb_gateway_mcp

by jitheshb83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jb_gateway_mcp

No user-submitted related servers found.

    Related Servers

    • exfu-multiaccount by ExFu

      exfu-multiaccountofficial

      ExFu
      F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI assistants access Gmail, Drive, Docs, and Calendar across multiple Google accounts, routing each request by a human-readable account alias. It supports reading, searching, and writing with per-account tagging while keeping OAuth credentials secure and separate.
      -

    • claude-2-mail

      omkargs
      A
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server for reading/sending email via Gmail and managing Google Calendar events, enabling an AI agent to handle email and calendar operations through natural language.
      MIT

    • multi-mail-mcp

      claygeo
      F
      license
      A
      quality
      C
      maintenance
      Local-first MCP server for agents that need to work across multiple Gmail and Microsoft 365 accounts without cloud token storage.
      6
      -

    • google-services-mcp

      nabheet
      A
      license
      B
      quality
      A
      maintenance
      MCP server that gives AI agents direct access to Google services including Gmail, Calendar, Drive, and more, with multi-account OAuth support. Enables reading and sending email, managing calendar events, and interacting with Google files through natural language.
      60
      22 npm
      1
      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

    B3.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Every tool is explicitly scoped by a domain prefix and a specific action; Gmail, Calendar, Drive, and Bank operations do not overlap. The two transaction-listing tools are differentiated as summary versus detailed.

    Naming Consistency5/5

    Tools consistently follow a <domain>.<verb>_<object> pattern (e.g. gmail.list_messages, drive.read_file, bank.get_balance). The standalone ping is a minor conventional exception but fits the gateway smoke-test role.

    Tool Count5/5

    Thirteen tools is a reasonable size for a multi-service gateway covering Gmail, Calendar, Drive, and banking data. Each tool contributes a distinct operation without bloat.

    Completeness3/5

    The read side is well covered, but the write/update side is incomplete: calendar events can be created but not updated or deleted, and Drive has no upload/update capability. Gmail and bank functionality are adequate for their apparent read/limited-action scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources