Skip to main content
Glama
Chaeyun06

네이버 길찾기 MCP 서버

by Chaeyun06
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to 네이버 길찾기 MCP 서버

No user-submitted related servers found.

    Related Servers

    • Naver MCP Server

      pfldy2850
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides access to Naver OpenAPI services, enabling users to search blogs, news, books, images, and other content through standardized Model Context Protocol interfaces.
      114
      MIT

    • MCP Google Map Server

      cablate
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that provides Google Maps API integration, allowing users to search locations, get place details, geocode addresses, calculate distances, obtain directions, and retrieve elevation data through LLM processing capabilities.
      7
      3,246 npm
      459
      MIT

    • MCP Naver Maps

      yunkee-lee
      A
      license
      B
      quality
      D
      maintenance
      A server that connects to Naver Maps and Search APIs, enabling geocoding and local search functionality for Korean locations.
      2
      2
      MIT

    • Geocoding MCP Server

      geocoding-ai
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol server that provides geocoding services by integrating with the Nominatim API, allowing AI assistants to perform location-based lookups.
      2
      481 npm
      3
      MIT

    • Google Maps MCP Server

      Moe03
      A
      license
      C
      quality
      D
      maintenance
      Provides access to Google Maps API functionality including geocoding, place search, direction routing, and distance calculations through a structured MCP interface.
      4
      2 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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: directions for routing, geocode for address-to-coordinates, reverse_geocode for coordinates-to-address, and search_places for location search. There is no overlap in functionality, making tool selection straightforward.

    Naming Consistency5/5

    All tools follow a consistent 'naver_' prefix and snake_case naming pattern (e.g., naver_directions, naver_geocode). This uniformity enhances readability and predictability across the toolset.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a navigation and mapping domain. Each tool serves a core function (routing, geocoding, reverse geocoding, place search), and there are no redundant or missing tools for this purpose.

    Completeness5/5

    The toolset provides complete coverage for basic navigation workflows: converting addresses to coordinates, coordinates to addresses, finding places, and getting directions. There are no obvious gaps, as these tools support end-to-end routing tasks.

    Resources