iletiMerkezi MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ILETIMERKEZI_API_KEY | Yes | Your API key from panel.iletimerkezi.com → Settings → Security → API Access. | |
| ILETIMERKEZI_API_HASH | Yes | Your API hash from panel.iletimerkezi.com → Settings → Security → API Access. | |
| ILETIMERKEZI_MANIFEST_URL | No | Override the manifest URL for staging/preview environments. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsB | The send-sms endpoint delivers an SMS to one or many mobile numbers in a single request. Each request is treated as an order; the response returns an orderId you can use to retrieve delivery reports or cancel scheduled orders. One order per request, one sender (header) per order. Reference: https://www.iletimerkezi.com/en/docs/api/send-sms |
| cancel_orderA | The cancel-order endpoint cancels an order created via send-sms with a sendDateTime in the future, before it is dispatched to the carrier. Only orders that have not started sending can be cancelled; once the order enters the send pipeline, the cancel window has closed and the request returns 455. Reference: https://www.iletimerkezi.com/en/docs/api/cancel-order |
| get_reportA | The get-report endpoint returns the delivery report for an order created via send-sms. One response carries the overall order status, summary counters (total / delivered / undelivered / waiting), timestamps, sender, order price, and per-recipient delivery status. Large orders paginate via page + rowCount. Reference: https://www.iletimerkezi.com/en/docs/api/get-report |
| get_reportsA | The get-reports endpoint returns the aggregate summary list of all SMS orders created within a given date range. For each order the response carries counters (total / delivered / undelivered / waiting), timestamps, and sender; per-recipient breakdown is not included — for that, call get-report for the specific order. This endpoint backs the Reports → Bulk SMS History screen in the panel. Typical use cases: dashboards, periodic analytics, queries like "list orders from the last week". Reference: https://www.iletimerkezi.com/en/docs/api/get-reports |
| get_balanceA | The get-balance endpoint returns the TL balance remaining on your account and the number of standard SMS messages that balance can fund. It has no side effects and consumes no credits, making it the safest call for verifying authentication and checking remaining budget before a campaign. Reference: https://www.iletimerkezi.com/en/docs/api/get-balance |
| get_senderA | The get-sender endpoint returns the list of sender IDs (headers) registered and approved on your account. The order.sender field of send-sms only accepts values from this list; using anything else is rejected. The call has no side effects and consumes no credits. Reference: https://www.iletimerkezi.com/en/docs/api/get-sender |
| get_blacklistA | The get-blacklist endpoint returns the list of phone numbers that you have blocked on your account. Numbers on this list are skipped during send-sms delivery. The call has no side effects and consumes no credits. Reference: https://www.iletimerkezi.com/en/docs/api/get-blacklist |
| add_blacklistA | The add-blacklist endpoint adds one phone number to your account's blacklist so it is skipped by send-sms. Idempotent: re-adding the same number returns 200 instead of an error. One number per request. Reference: https://www.iletimerkezi.com/en/docs/api/add-blacklist |
| delete_blacklistA | The delete-blacklist endpoint removes a phone number from your account's blacklist. After removal, send-sms can deliver to that number again. One number per request; not idempotent — removing a number that is not on the list returns an error. Reference: https://www.iletimerkezi.com/en/docs/api/delete-blacklist |
| iys_registerA | The iys-register endpoint creates İYS (İleti Yönetim Sistemi) consent records — the legally required Turkish national registry for commercial electronic messaging. Consents (or rejections) collected via web forms, signed contracts, call-center confirmations, etc. are submitted to iletiMerkezi through this endpoint and forwarded to the national İYS registry. Up to 5000 recipients per request. İYS registration is mandatory for any commercial SMS sent in Turkey. Without a valid consent record, the corresponding send-sms call with iys: "1" is rejected with code 468 / 469 / 470. Reference: https://www.iletimerkezi.com/en/docs/api/iys-register |
| iys_checkA | The iys-check endpoint returns the current İYS (İleti Yönetim Sistemi) consent status for a given recipient. Use it to verify a record submitted via iys-register has been processed, to check ONAY (consent) / RET (rejection) before a commercial send, or to produce audit reports. The call has no side effects and consumes no credits. Reference: https://www.iletimerkezi.com/en/docs/api/iys-check |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iletimerkezi/iletimerkezi-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server