tmap_mcp

Created By
bm1120a year ago
tmap rest api 기반 mcp server 구축
Overview

What is tmap_mcp?

The tmap_mcp project is a server built on the Tmap REST API that provides the Model Context Protocol (MCP) server functionality, allowing AI tools like Cursor Editor to directly call Tmap API features.

How to use tmap_mcp?

To use tmap_mcp, you need to set up the MCP server by installing the required packages and configuring your Tmap API key. You can then run the server and connect it with the Cursor Editor for enhanced functionality.

Key features of tmap_mcp?

  • Location search (POI search, address search)
  • Geocoding and reverse geocoding
  • Pedestrian and car route guidance
  • Real-time congestion information
  • Time machine route guidance
  • Public transport route guidance and summary
  • Additional Tmap API functionalities

Use cases of tmap_mcp?

  1. Searching for points of interest (POIs) based on keywords.
  2. Providing real-time navigation for pedestrians and vehicles.
  3. Integrating with AI tools for enhanced location-based services.

FAQ from tmap_mcp?

  • What are the system requirements for tmap_mcp?

You need Python 3.6 or higher and a Tmap API app key.

  • How do I install the necessary packages?

Use the command pip install pymcp requests to install the required packages.

  • Can I use tmap_mcp without the Cursor Editor?

Yes, but the full functionality is best utilized with the Cursor Editor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bm1120
Star
0
Language
Python
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago