fonzip-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FONZIP_BASE_URL | No | API base URL | https://fonzip.com/api/v2 |
| FONZIP_CLIENT_ID | No | Fonzip API client id | |
| FONZIP_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
| FONZIP_USER_AGENT | No | User-Agent header value. Do not leave empty. | fonzip-mcp/<version> |
| FONZIP_MAX_RETRIES | No | Number of retries for 429 and 5xx errors | 3 |
| FONZIP_SCHEMA_MODE | No | Schema mode: 'full' or 'compact' | full |
| FONZIP_TOKEN_CACHE | No | Token cache path. Set to 'off' to disable caching. | ~/.cache/fonzip-mcp/tokens.json |
| FONZIP_ACCESS_TOKEN | No | Ready token. If provided, the client_credentials flow is skipped. | |
| FONZIP_CLIENT_SECRET | No | Fonzip API client secret |
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 |
|---|---|
| fonzip_systemA | Hesap ve sistem bilgileri: baglantiyi dogrulayan kurum bilgisi (me), odeme sistemleri, banka hesaplari ve pazarlama kanallari. Kurulumu dogrulamak veya diger tool'larda kullanilacak ID'leri bulmak icin buradan baslayin. |
| fonzip_usersB | Uyeler/bagiscilar (kisiler): listeleme ve arama, detay, olusturma, guncelleme, silme; kisinin zaman tuneli, etiketleri, bagislari, aidatlari, biletleri ve form cevaplari. |
| fonzip_donationsC | Bagislar: listeleme (tarih araligi zorunlu), detay, olusturma, silme, rapor; bagis kategorileri; mikro bagislar; bagis sayfalari ve formlari. |
| fonzip_monthly_donationsC | Duzenli (aylik) bagislar: tutar degisiklik talebi olusturma/yanitlama, kart guncelleme talebi gonderme, duzenli bagisi iptal etme. |
| fonzip_membership_duesB | Aidatlar ve borclar: aidat aboneliklerini listeleme/detay/silme, borc (debt) olusturma, guncelleme, durum degistirme ve silme. |
| fonzip_eventsB | Etkinlikler: etkinlik olusturma, guncelleme, durum degistirme, silme; bilet tanimlari; bilet satislari ve satis detaylari. |
| fonzip_fundraisingC | Bagis toplama: kampanyalar (fundraising campaign), kampanya etkinlikleri (fundraising event) ve takimlar (fundraising team) ile takimlara bagli kampanyalar. |
| fonzip_formsB | Ozel formlar ve form cevaplari: form listesi, cevap listesi, cevap detayi ve bir cevaba yanit yazma. |
| fonzip_ecardsB | E-kartlar: kart ve kart kategorisi yonetimi, e-kart satis islemlerini listeleme, detay ve silme. |
| fonzip_tagsB | Etiketler: kurum genelindeki etiketleri listeleme, olusturma, guncelleme ve silme. |
| fonzip_templatesC | E-posta/mesaj sablonlari: listeleme, detay, olusturma, guncelleme ve silme. |
| fonzip_webhooksB | Webhook'lar: kayitli webhook'lari listeleme, detay, olusturma, guncelleme, test bildirimi gonderme ve silme. |
| fonzip_communication_permissionsA | Iletisim izinleri (e-posta/SMS/telefon): bir adres veya numaranin izin durumunu sorgulama, guncelleme ve degisenleri listeleme. |
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 13 tools
Each tool maps to a distinct resource area such as users, donations, forms, webhooks, or templates, making selection relatively straightforward. Some overlap exists between donation pages/forms and custom forms, and between general events and fundraising events, but the descriptions clarify the intended boundaries.
All tools follow the same fonzip_<resource> snake_case naming convention, using plural nouns for resource domains. This creates a highly predictable and consistent pattern, even though the names are noun-based rather than verb_noun phrases.
Thirteen tools is well within the ideal range for a donor-management and fundraising platform. Each tool represents a meaningful domain and contributes to the overall scope without feeling bloated or redundant.
The tool surface covers the major donor lifecycle: users, donations, recurring donations, dues, events, fundraising campaigns, forms, communication permissions, templates, webhooks, and system configuration. Minor gaps exist, such as no explicit listing operation for recurring donations and limited sales operations for tickets and e-cards, but most essential workflows are supported.