# Accept Language Parser MCP for AI Agents AI Agent Connect > Accept Language Parser handles complex HTTP headers to figure out exactly which language a user wants. It takes messy strings with quality weights and turns them into a clean, ordered list so your app can serve the right content every time. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_GefvSpcYnjkW02BvoNUlHjU2kd5JY1rRrk73aseR/ai-agent-connect - **Tags:** http-headers, localization, language-detection, rfc-compliance, parsing, web-standards ## Description When you're building a global application, you can't just guess what language a user wants to see. You have to handle the headers sent by their browser, which often come back as a disorganized mess of tags and numbers. This Connector takes that raw data and does the heavy lifting for you. It follows the official standards to figure out which language has the highest priority, even when multiple options are provided with different weights. Instead of writing custom logic to sort through these strings, your agent can just hand off the header and get back a clean list of preferences. It's built for accuracy, making sure your localization logic doesn't break when it hits a weird edge case. By using this Connector within the Vinkius catalog, you get a reliable way to handle internationalization without worrying about the underlying RFC rules. It's about making sure a user in Brazil sees Portuguese while a user in the US sees English, even if their browser sends a complicated mix of both. This is especially useful for developers who need to ensure that their content serves the right audience the first time. You don't have to worry about whether a specific weight is valid or how to handle missing values. The tool handles the logic deterministically so your agent can focus on the actual work of serving content, like choosing the right translation file or routing the user to the correct regional endpoint. It takes the headache out of web standards and puts the focus back on your user experience. ## Tools ### parse_accept_language Converts a raw header string into a sorted list of languages with their respective quality weights. ## Prompt Examples **Prompt:** ``` What's the best language for this header: fr-CA,en;q=0.9? ``` **Response:** ``` Based on the header provided, the preferred language is: * **French (Canada)** (fr-CA) It has the highest priority. The fallback language is English (en) with a weight of 0.9. ``` **Prompt:** ``` Parse this: de,en-GB;q=0.7,ja;q=0.3 ``` **Response:** ``` Here is the prioritized list of languages from that header: 1. **German (de)** (Weight: 1.0) 2. **British English (en-GB)** (Weight: 0.7) 3. **Japanese (ja)** (Weight: 0.3) ``` **Prompt:** ``` How many languages are in: zh-CN,zh;q=0.9,en;q=0.8,ko;q=0.7,ar;q=0.6 ``` **Response:** ``` There are 5 languages detected in that header: * Chinese (Simplified) * Chinese * English * Korean * Arabic ``` ## Capabilities ### Sort languages by weight It automatically puts the highest priority language at the top of the list. ### Handle q-factors It correctly interprets the decimal weights used in standard web headers. ### Extract specific locales It pulls out the exact region and language codes from the raw string. ### Standardize header data It turns inconsistent browser strings into a uniform format for your backend. ### Simplify localization logic It removes the need for manual regex or string splitting in your code. ## Use Cases ### Global Routing A user hits a landing page; the agent parses the header to send them to the correct regional server instantly. ### Dynamic Content Loading A web app needs to know which translation file to fetch first based on browser settings for a seamless experience. ### Multi-tenant Localization An enterprise tool serves 50 countries and needs to prioritize languages accurately for each individual user. ### Automated Testing A QA script uses the tool to verify that the correct language is being served for various test headers across different regions. ## Benefits - Stop writing manual regex by using parse_accept_language to handle complex header strings without maintaining your own parsing logic. - Ensure RFC compliance because the Connector follows RFC 7231 for all q-factor calculations, keeping your app up to standard. - Improve UX for global users because the tool correctly identifies the highest-weighted preference so they see the right content immediately. - Reduce backend complexity by offloading the logic of sorting and weight calculation to the Connector so your main code stays clean. - Handle edge cases automatically as complex headers with multiple weights and missing values are handled deterministically every time. ## How It Works The bottom line is your agent gets a clean, prioritized list of languages instead of a messy header string. 1. Provide the raw Accept-Language string from a user's request. 2. The Connector parses the string against RFC 7231 standards. 3. You get a sorted list of languages ranked by user preference. ## Frequently Asked Questions **Can the Accept Language Parser handle multiple languages?** Yes, it identifies every language in the header and sorts them by weight so you can see the full list of user preferences. **Does it support standard web weights?** Yes, it's fully compliant with RFC 7231 for q-factors, ensuring it works correctly with all modern browsers. **How do I use Accept Language Parser for my website?** You just pass the browser's header string to the tool to get a sorted list of preferences, which you can then use to load the correct content. **Will it work for all regions?** It parses the standard language codes used by almost all modern browsers and operating systems globally. **What happens if there are no weights?** If the header has no weights, the tool defaults to the order provided in the string while still keeping the output clean and uniform. **Is it faster than writing my own code?** Yes, it's a deterministic parser that handles all the standard edge cases instantly, saving you the time of writing and testing your own logic. **What is a quality weight (q-factor)?** A value from 0 to 1 indicating preference. `q=1` (default) is highest priority. `q=0` means the language is explicitly not accepted. **Does it handle regional subtags?** Yes. `pt-BR` is parsed as code=pt, region=BR. `en-US` as code=en, region=US. The region is separated from the language code automatically. **What if no quality value is specified?** Languages without an explicit q-value default to q=1 (highest priority), following the HTTP specification.