"Automating HTTP API Wrapping into MCPT Tool" matching MCP servers:

Enables interaction with XTRF translation management system through their Home Portal API. Provides access to XTRF's project management, translation workflow, and client portal functionalities via natural language interface.

An MCP (Multi-Agent Conversation Protocol) Server that enables AI agents to interact with Google's Cloud Translation API for translating text between languages.

Provides access to synonyms and antonyms for words through the API Ninjas Thesaurus API, enabling vocabulary enhancement and word exploration.

An MCP server that enables users to add translation keys to Lokalise projects using natural language through Cursor or standalone interfaces. It allows for the specification of project names, translation keys, default values, and target platforms.

Provides dictionary lookup functionality through the API Ninjas Dictionary API, allowing users to search for word definitions and meanings through natural language queries.

Model Context Protocol (MCP) server for the Royal Spanish Academy (RAE) API. It allows language models to interact with RAE's dictionary and linguistic resources.

Enables bidirectional lookup of Mi'kmaq and English words with definitions and examples, and provides tools for learning and dictionary statistics, integrating seamlessly with AI-powered IDEs.

Search Japanese onomatopoeia by scene, not by spelling. 161 entries with nuance explained in Japanese and English. Fully offline MCP server, no API key required.

AI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.

Integrates the levelang.app translation API with AI assistants to provide translations constrained to specific learner proficiency levels. It supports multiple languages and allows users to control translation styles and moods while dynamically discovering available language configurations.

Enables AI agents to conjugate verbs in 14 European languages via a hosted Rust API, requiring only a free API key.

Enables agents to speak Thai and English audio through local speakers, manage a playback queue, save speech to files, translate text into Thai, and OCR PDFs and images.

MCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.

prevents llm from overload, freeze and oscillation

An MCP server that provides LLM agents with full access to the Texterify translation management API. It enables users to search, create, update, and delete translation keys and their values directly through natural language within their development environment.

Enables law firms and legal professionals to turn Arabic and English contract files into structured, citable context, with clause segmentation, date conversion across Hijri and Gregorian calendars, party extraction, and anchor-based verification, all without API keys or network calls.

Translation QA for i18n locale files. Deterministic validators — missing keys, placeholder drift, collapsed plurals, glossary breaches — that need no API key, plus a review tool that hands translation pairs and judging criteria back to the calling agent, so meaning-level review runs on the model your client already has. Translation with your own LLM key is optional. JSON, Flutter .arb, Apple .

A Docker-based MCP server wrapping the Smartling CLI, enabling natural language management of translation projects, files, and glossaries.

Provides text translation capabilities powered by NiuTrans API with support for 455+ languages. Includes translation tools and language catalog resources for seamless integration with MCP clients.

Delegates replaceable grunt work (boilerplate, formatting, translation, long-document summarizing) from a premium agent to cheap models behind a local LiteLLM proxy, auto-routing each task by type. Delegated calls run in a separate process, so the subscription session and the API credentials never share an environment.