MCP TMAP Server
Enables configuration management through environment variables, used for storing and retrieving API credentials.
Provides the runtime environment for the MCP server, requiring version 3.13 or higher.
Used for dependency management through the pyproject.toml file, defining the project's dependencies.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP TMAP Server find transit routes from Gangnam Station to Jamsil Station"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP TMAP
The MCP connects to the TMAP API.
It currently supports the following APIs:
Transit route
Full text geocoding
Prerequisites
Before you begin, ensure you have the following installed:
Python: Version 3.13 or higher
uv: You can find installation instructions here.
SK Open API: You need API credentials (app key) from the SK open API.
Related MCP server: MCP Naver Maps
Configuration
Create a
.envfile: Create a file in the project root.Add API Credentials: Edit the
.envfile and add your SK open API credentials.SK_OPEN_API_APP_KEY="YOUR_APP_KEY_HERE"Please verify the exact environment variable names required by checking
src/mcp_tmap/tmap_client.py.
Running the MCP
Sync Dependencies: Navigate to the project root directory in your terminal and run the following command. This will create a virtual environment (if one doesn't exist) and install all dependencies specified in
pyproject.toml.uv syncRun:: You can run the MCP server using
uv.uv run src/mcp_tmapFor development,
source .venv/bin/activate mcp dev src/mcp_tmap/server.py
Available Tools
2 toolsfullTextAddressGeocodingC
Converts the given address to coordinates (geocoding).
Args address (str): address to convert.
Returns: a list of coordinates
newLat: latitude
newLon: longitude
newLatEntr: latitude of the entrance
newLonEntr: longitude of the entrance
Inputs: address (required).
publicTransitRoutesB
Retrieves public transportation routes from start to destination.
Args: startLon (str): longitude of the starting point (WSG84). startLat (str): latitude of the starting point (WSG84). destLon (str): longitude of the destination (WSG84). destLat (str): latitude of the destination (WSG84). language (int): language of the route; 0 for Korean and 1 for English. searchTime (str, optional): Sets the time for the route to be searched. Used as information to indicate whether transportation is in operation. See [service] in the response for the operation status.
Returns: route information
itineraries: route details
fare: total fare
totalTime: in seconds
transferCount:
totalWalkDistance: in meters
totalDistance: in meters
totalWalkTime: in seconds
legs: legs in the route
distance: in meters
sectionTime: in seconds
mode: transportation mode
route: transportation route
start: starting point of the leg
end: destination of the leg
Inputs: destLat (required), destLon (required), startLat (required), startLon (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one is for geocoding addresses to coordinates, and the other is for retrieving public transit routes between coordinates. There is no overlap in functionality, making it impossible to confuse them.
The naming is inconsistent: 'fullTextAddressGeocoding' uses camelCase, while 'publicTransitRoutes' uses a different style with mixed lower and upper case. There is no clear pattern, and the verb usage differs ('fullTextAddress' vs. 'publicTransit'), making it chaotic.
With only 2 tools, the server feels thin for a mapping/transit domain. It lacks basic operations like reverse geocoding, route alternatives, or transit schedule details, making it under-scoped for typical navigation or location-based tasks.
The server is severely incomplete for a mapping/transit service. It misses essential operations such as reverse geocoding, route optimization, transit stop information, or map data retrieval. The two tools provide only a narrow slice of functionality, leading to significant gaps in agent workflows.
Maintenance
Related MCP Connectors
The Google Maps MCP server is a fully-managed server provided by the Maps Grounding Lite API that connects AI applications to Google Maps Platform services. It provides three main tools for building LLM applications: searching for places, looking up weather information, and computing routes with details like distance and travel time. The server acts as a proxy that translates Google Maps data into a format that AI applications can understand, enabling agents to accurately answer real-world location and travel queries.
This MCP server provides seamless access to Malaysia's government open data, including datasets, w…
Geo-based flight search MCP server. Find more flights between any two places on earth
An MCP server for Georgian public data, read from the organizations that publish it.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA server that enables AI models to access Kakao Map features (place search, address lookup, route finding) and Daum search services (web, image, blog, cafe) through Model Context Protocol.18MIT
- AlicenseBqualityDmaintenanceA server that connects to Naver Maps and Search APIs, enabling geocoding and local search functionality for Korean locations.22MIT
- AlicenseAqualityBmaintenancemcp-server-public-transport is an open-source, locally hosted server providing an interface for accessing public transport data across Europe.1343 PyPI9PythonMIT
- FlicenseNot gradedqualityBmaintenanceThis MCP server provides accessibility risk assessment for Seoul subway trips, considering wheelchair, stroller, and other mobility constraints. It offers tools to check station facilities, elevator status, and calculates risk scores for routes based on a deterministic engine.-