Skip to main content
Glama
riker-t

Ramp Developer MCP Server

by riker-t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Ramp Developer MCP Server

No user-submitted related servers found.

    Related Servers

    • @octri/mcp

      OctriDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.
      179 npm
      MIT

    • OwlPay MCP Server

      OwlTing
      A
      license
      B
      quality
      D
      maintenance
      Enables LLMs to search and retrieve OwlPay documentation directly through natural language queries. Accelerates system integration by providing instant access to OwlPay API documentation and guides.
      1
      1
      MIT

    • code-context

      jieyefriic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to automatically scan, store, and query API endpoints from codebases, providing instant lookup and semantic search to reduce context switching and token consumption.
      1
      MIT

    • stores-dev-mcp

      unlearned
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides STORES API documentation to AI clients, enabling natural language queries about endpoints, authentication, and more.
      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.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_endpoint_schema retrieves technical API specifications, ping tests connectivity, search_documentation finds documentation content, and submit_feedback collects user feedback. The descriptions explicitly differentiate their functions, eliminating any ambiguity in tool selection.

    Naming Consistency3/5

    The naming conventions are mixed: get_endpoint_schema and search_documentation follow a verb_noun pattern, but ping is a single verb and submit_feedback uses a verb_noun structure. While all names are readable and descriptive, the inconsistency in style (e.g., ping vs. get_endpoint_schema) prevents a higher score.

    Tool Count4/5

    With 4 tools, the count is reasonable for a developer-focused server, covering API schema retrieval, documentation search, connectivity testing, and feedback submission. It feels slightly thin for a full API integration suite but well-scoped for core developer assistance tasks, with each tool earning its place.

    Completeness3/5

    The tool set covers key developer needs like schema lookup and documentation search, but there are notable gaps for actual API interaction (e.g., no tools to create, update, or delete resources like bills or cards). This limits agents to informational tasks without execution capabilities, which may cause workarounds or failures in broader integration workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources