Lingo

Turn vague design requests like "make it pop" into precise design terms and a brief.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~237Tokens (tool definitions)
~873 BTypical response size
Minimal attention impact (0.19% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "lingo": {
      "url": "https://lingo.clawhard.com/mcp"
    }
  }
}

Remote endpoints

https://lingo.clawhard.com/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢lingo_translate_design_request(phrase, avoid_ai_look)

Use when a user (often not a designer) gives vague design feedback or a request such as "make it pop", "more premium", "cleaner", "less boring", "feels off" and you need specific, actionable design changes rather than guesses. Matches the phrase to design terms and returns what it usually means, concrete moves (spacing, contrast, type, color, hierarchy) and a ready-to-use design brief, with an option to avoid generic AI-looking choices. Example: {"phrase": "make it pop"}.

Input Schema

{
  "type": "object",
  "properties": {
    "phrase": {
      "type": "string",
      "description": "The vague request in plain words, e.g. \"it feels cheap and too busy\"."
    },
    "avoid_ai_look": {
      "type": "boolean",
      "description": "Add rules that steer away from the generic AI-made look. Default true."
    }
  },
  "required": [
    "phrase"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools