Taksi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEST_MODE | No | Test modu (API çağrıları yerine mock data) | true |
| DEFAULT_CITY | No | Varsayılan şehir | istanbul |
| UBER_ENABLED | No | Uber entegrasyonunu etkinleştir | false |
| ITAKSI_API_KEY | No | iTaksi API anahtarı | |
| ITAKSI_ENABLED | No | iTaksi entegrasyonunu etkinleştir | false |
| UBER_CLIENT_ID | No | Uber Client ID | |
| BITAKSI_API_KEY | No | BiTaksi API anahtarı | |
| BITAKSI_ENABLED | No | BiTaksi entegrasyonunu etkinleştir | false |
| DEFAULT_CURRENCY | No | Varsayılan para birimi | TRY |
| DEFAULT_LANGUAGE | No | Varsayılan dil | tr |
| DEFAULT_LATITUDE | No | Varsayılan enlem (İstanbul Taksim) | 41.0362 |
| DEFAULT_LONGITUDE | No | Varsayılan boylam (İstanbul Taksim) | 28.9841 |
| UBER_CLIENT_SECRET | No | Uber Client Secret | |
| DEFAULT_COUNTRY_CODE | No | Varsayılan ülke kodu | TR |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taksi_turleri_getirB | Mevcut taksi türlerini ve özelliklerini listele |
| ucret_tahminiC | İki konum arası taksi ücreti tahmini hesapla |
| taksi_cagirC | Belirtilen konumlar arası taksi çağır |
| yolculuk_durumuC | Aktif yolculuğun durumunu ve şoför bilgilerini sorgula |
| yolculuk_iptalC | Aktif yolculuğu iptal et |
| yolculuk_gecmisiC | Geçmiş yolculukları listele |
| surucu_iletisimB | Aktif yolculukta şoförle iletişime geç (ara/mesaj) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: driver communication, booking, vehicle types, fare estimation, trip status, history, and cancellation. The descriptions specify unique actions and targets, making misselection unlikely.
All tool names follow a consistent Turkish verb_noun pattern (e.g., taksi_cagir, ucret_tahmini, yolculuk_durumu). The naming is uniform across all tools, using snake_case and descriptive terms aligned with the taxi service domain.
With 7 tools, the server is well-scoped for a taxi service, covering core operations like booking, pricing, status, and cancellation. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for a taxi service: it includes booking (taksi_cagir), pre-trip (taksi_turleri_getir, ucret_tahmini), in-trip (surucu_iletisim, yolculuk_durumu, yolculuk_iptal), and post-trip (yolculuk_gecmisi) operations, with no obvious gaps in the workflow.