Skip to main content
Glama
satyamsh04

custom-mcp-server

by satyamsh04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to custom-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP OpsBridge

      SaADii09
      F
      license
      B
      quality
      B
      maintenance
      Unified MCP server exposing 12 DevOps tools across GitHub, PostgreSQL, Slack, and Google Calendar for AI agents, with rate limiting, input validation, and per-service scoped tokens.
      30
      -

    • etsy-mcp

      alveyautomation
      A
      license
      A
      quality
      D
      maintenance
      A production-grade MCP server that enables AI assistants like Claude to read Etsy shop data—listings, orders, inventory, and stats—through eight read-only tools, using OAuth and automatic pagination.
      8
      MIT

    • mcp-server

      ElJijuna
      A
      license
      Not graded
      quality
      C
      maintenance
      A thin TypeScript MCP server that exposes engineering tools (Bitbucket, Jira, Confluence, ArgoCD) to MCP-compatible editors via a single API key per developer, delegating all service interactions to an internal backend.
      221 npm
      MIT

    • s3-mcp-server

      debadatta30
      F
      license
      Not graded
      quality
      C
      maintenance
      A remote, OAuth2-authenticated MCP server that provides read-only S3 tools (list buckets, list objects, check public access, get bucket size) designed to run on ECS Fargate with Auth0 as the identity provider.
      -

    • Slack MCP Server

      kamolc4
      A
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.
      21,724 npm
      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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: annotation_status for task status, dynamo_read/write for database, s3_download/upload for storage, slack_notify for messaging. No overlap.

    Naming Consistency4/5

    Most tools follow verb_noun pattern (dynamo_read, dynamo_write, s3_download, s3_upload, slack_notify), but 'annotation_status' is an outlier as a noun phrase.

    Tool Count5/5

    6 tools is well-scoped for a server covering annotation, database, storage, and Slack integration. It feels neither too few nor too many.

    Completeness3/5

    Each service has basic operations but lacks deletions, updates, and lists. For annotation only status is provided. This leaves notable gaps for typical workflows, but the server may be intentionally scoped.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources