Iletimerkezi MCP Server

What iletimerkezi/iletimerkezi-mcp-server MCP server does

The iletimerkezi/iletimerkezi-mcp-server MCP server connects MCP-aware clients to the iletiMerkezi SMS API. It provides 11 tools covering outbound messaging, scheduled-order cancellation, delivery reporting, account inspection, sender management, blacklist operations, and Turkish İYS consent records.

The messaging tools can send SMS to individual or multiple recipients. The documented limits are 100 messages per second for transactional traffic and up to 50,000 recipients per bulk request. Delivery tools provide either details for one order, including recipient-level results, or order summaries for a date range of up to 10 days.

Account and compliance operations are also exposed. Agents can read the TL and SMS-credit balance, list approved sender headers, paginate through blocked numbers, add or remove blacklist entries, register batches of up to 5,000 İYS consent records, and check consent status for a recipient.

How it works

The server runs in local stdio mode and communicates with the MCP client over that process connection. Each MCP tool maps to an iletiMerkezi JSON API endpoint. Tool inputs and descriptions are derived from the provider’s API manifest rather than being maintained as separate handwritten schemas.

At startup, the server first checks a local manifest cache at ~/.cache/iletimerkezi-mcp/manifest.json. A cache remains valid for 24 hours. If needed, the server fetches the live manifest with a five-second timeout and updates the cache; if that fails, it uses the fallback manifest included in the npm package. This design allows published API schema changes to reach clients without an npm package update, subject to the cache period.

Setup and configuration

Install the package with npx -y @iletimerkezi/mcp-server and configure the server in the MCP client’s mcpServers settings. The iletimerkezi/iletimerkezi-mcp-server MCP server requires two environment variables: ILETIMERKEZI_API_KEY and ILETIMERKEZI_API_HASH.

Both credentials are obtained from the iletiMerkezi panel under Settings → Security → API Access. The API hash is supplied by the panel and should be copied as provided. API access must also be enabled under Settings → Security → Access Permissions; otherwise requests return HTTP 401.

The documented JSON configuration works with Claude Desktop, Cursor, Gemini CLI, and VS Code with Cline. Claude Code and Codex CLI also have dedicated commands for registering the same local process. After changing configuration, fully restart the client. get_balance and get_sender are suggested read-only checks for initial verification.

For staging or preview environments, set ILETIMERKEZI_MANIFEST_URL to replace the default manifest location. Local development uses npm install, npm run build, and npm test; the built server can be started with Node and the two credential variables.

Tools and capabilities

• send_sms: Send transactional or bulk SMS.
• cancel_order: Stop a future-scheduled order before dispatch.
• get_report and get_reports: Retrieve detailed or date-range delivery information.
• get_balance: Read TL and SMS-credit balances.
• get_sender: List approved sender headers.
• get_blacklist, add_blacklist, and delete_blacklist: Review and change blocked-number entries.
• iys_register and iys_check: Create and inspect İYS consent records.

Limitations and notes

The iletimerkezi/iletimerkezi-mcp-server MCP server currently ships only as a local stdio server. Hosted clients that require an HTTPS remote MCP endpoint cannot use it directly; hosted support is described as planned rather than currently available.

The SMS API account, credentials, permissions, sender approvals, message limits, and available credits remain external iletiMerkezi requirements. The server does not remove those provider-side constraints. Manifest freshness also depends on the 24-hour cache and the availability of the live manifest URL.

The project is licensed under MIT.