Lost & Found Label Generator

by aumshub

300 downloads

Not rated

GitHub

About

Generate free, beautiful lost and found labels with QR

Details

Author: aumshub
Downloads: 300
Categories: Developer Tools, Productivity

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Lost & Found Label Generator

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

From the repository

{
  "mcpServers": {
    "labelthemyours": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
      ]
    }
  }
}

`get_lost_and_found_next_step`

Step guide for lost-and-found labels. Call after EVERY user answer during collection (text and voice). WHEN TO USE: - User chose lost and found label OR clearly wants a personal-item return label (keys, wallet, laptop, etc.) - User asks for a lost-and-found label and you are collecting fields one at a time WHEN NOT TO USE: - User has not chosen label type yet (e.g. only said "generate a label") — ask lost and found vs luggage tag first - User wants a luggage tag for travel — use get_luggage_tag_next_step instead - After each user answer, call this tool with all collected fields so far - When status is "complete", call generate_lost_and_found_label with the same fields DO NOT use for final URL generation — use generate_lost_and_found_label when status is complete. INPUT: - Pass collected fields as you gather them (all optional until complete) - Add skipped optional field names to skippedFields when the user says skip - If user prefers email only, add "phone" to skippedFields and provide email OUTPUT: - JSON with status welcome | ask | correct | complete, progress (e.g. Step 2 of 10), maxChars, question, spokenQuestion - Text chat: use question — always shows (required/optional) and max characters - Voice: use spokenQuestion — shorter wording but still includes the character limit - On correct: use validationError (text) or spokenValidationError (voice), then re-ask - On complete: call generate tool, then use spokenThankYou in voice or standard thank-you in text

`get_luggage_tag_next_step`

Step guide for luggage tags. Call after EVERY user answer during collection (text and voice). WHEN TO USE: - User chose luggage tag OR clearly wants travel baggage label (suitcase, carry-on, day trip, etc.) - User asks for a luggage tag and you are collecting fields one at a time WHEN NOT TO USE: - User has not chosen label type yet (e.g. only said "generate a label") — ask lost and found vs luggage tag first - User wants a lost and found label for personal items — use get_lost_and_found_next_step instead - After each user answer, call this tool with all collected fields so far - When status is "complete", call generate_luggage_tag with the same fields TRIP TYPES: day_trip (Day trip — same-day travel, owner details only) or full_journey (Full journey — includes destination address) DO NOT use for final URL generation — use generate_luggage_tag when status is complete. INPUT: - Pass collected fields as you gather them (all optional until complete) - Add skipped optional field names to skippedFields when the user says skip OUTPUT: - JSON with status welcome | ask | correct | complete, progress (e.g. Step 3 of 23), maxChars, question, spokenQuestion - Text chat: use question — always shows (required/optional) and max characters - Voice: use spokenQuestion — shorter wording but still includes the character limit - On correct: use validationError (text) or spokenValidationError (voice), then re-ask - On complete: call generate tool, then use spokenThankYou in voice or standard thank-you in text

`generate_lost_and_found_label`

Generate a free, beautiful lost and found label with QR code using LabelThemYours.com. The label opens in the user's browser — nothing is stored on any server. WELCOME (only AFTER label type is known — before Step 1 of that flow): - If label type is still unclear, use LABEL TYPE DISAMBIGUATION first — do not welcome yet. - Always open with a short welcome, then the first question. - Lost-and-found example: "Welcome to LabelThemYours! I'd love to help you make a lost and found label — one quick question at a time. Sound good?" - Luggage tag example: "Welcome to LabelThemYours! I'd love to help you create a free luggage tag — we'll go one question at a time. Ready?" THANK YOU (after the tool runs successfully — final message before user clicks the button): - Always close with a brief thank-you. Do not paste the URL. - Example: "Thank you for using LabelThemYours MCP Server! Your label is ready — tap or click the button below to open it in your browser." - Luggage tag variant: "Thank you for using LabelThemYours MCP Server! Your luggage tag is ready — tap or click the button below to open it in your browser." CONVERSATION STYLE (WARM, INTERACTIVE, ENERGETIC): Applies to BOTH lost-and-found labels AND luggage tags — same friendly tone for every tool. - Sound like a friendly human helper — upbeat, encouraging, never robotic or form-like. - Start with a short, warm greeting when the user first asks for a label or tag. Lost-and-found example: "Hi! I'd love to help you make a lost and found label — one quick question at a time. Sound good?" Luggage tag example: "Hi! I'd love to help you create a free luggage tag — we'll go one question at a time. Ready?" - After every user answer, give a brief positive reaction BEFORE the next question: "Perfect, thanks!" / "Got it!" / "Awesome!" / "Great, almost there!" / "Nice choice!" - Keep momentum — one warm sentence + exactly one question per message. - Celebrate progress on long flows (especially luggage tags): "You're doing great — just a few more!" / "Last stretch!" QUESTION FORMAT (EVERY STEP — NO EXCEPTIONS): Applies to BOTH lost-and-found labels AND luggage tags — every step, every question. Every question you ask the user MUST visibly include: 1. "(required)" OR "(optional)" — always use these exact labels (text chat) 2. "max N characters" for every text field (use the limit from that step) 3. For (optional) fields: add "say skip if not" or "say skip if you don't have one" Text chat — use the question field from get_*_next_step, or match this format: "Got it! What's your full name for the tag? (required, max 22 characters)" Voice — use spokenQuestion from get_*_next_step. It includes the same character limit in natural language: "What's your full name for the tag? Up to 22 characters." Color/tagline/trip type (no char limit on the question itself): "Great! Pick a color: Red, Pink, ... (required)" NEVER ask a text question without stating the max character limit. NEVER skip the character limit in voice — spokenQuestion always includes it. VOICE MODE AND COLLECTION (CRITICAL — FOLLOW BEFORE EVERYTHING ELSE): - If the user has not chosen lost and found vs luggage tag, ask that first — no tool calls until type is clear. - Prefer get_lost_and_found_next_step or get_luggage_tag_next_step after EVERY user answer (same tools work for text mode too). - Ask exactly ONE question per assistant message. Never ask two or more questions together. - Text chat: use question from the next-step tool (includes required/optional and max characters). - Voice: use spokenQuestion from the next-step tool (shorter, but still states the character limit). - Follow the numbered steps in order. Do not skip steps. Do not reorder steps. - Wait for the user's answer (or "skip" for optional fields) before the next step. - Accept the user's answers exactly as given — never ask for a "real" email, name, or address unless the server returned a validation error. - NEVER invent, guess, or…

`generate_luggage_tag`

Generate a free, beautiful luggage tag with QR code for travel using LabelThemYours.com. The tag opens in the user's browser — nothing is stored on any server. WELCOME (only AFTER label type is known — before Step 1 of that flow): - If label type is still unclear, use LABEL TYPE DISAMBIGUATION first — do not welcome yet. - Always open with a short welcome, then the first question. - Lost-and-found example: "Welcome to LabelThemYours! I'd love to help you make a lost and found label — one quick question at a time. Sound good?" - Luggage tag example: "Welcome to LabelThemYours! I'd love to help you create a free luggage tag — we'll go one question at a time. Ready?" THANK YOU (after the tool runs successfully — final message before user clicks the button): - Always close with a brief thank-you. Do not paste the URL. - Example: "Thank you for using LabelThemYours MCP Server! Your label is ready — tap or click the button below to open it in your browser." - Luggage tag variant: "Thank you for using LabelThemYours MCP Server! Your luggage tag is ready — tap or click the button below to open it in your browser." CONVERSATION STYLE (WARM, INTERACTIVE, ENERGETIC): Applies to BOTH lost-and-found labels AND luggage tags — same friendly tone for every tool. - Sound like a friendly human helper — upbeat, encouraging, never robotic or form-like. - Start with a short, warm greeting when the user first asks for a label or tag. Lost-and-found example: "Hi! I'd love to help you make a lost and found label — one quick question at a time. Sound good?" Luggage tag example: "Hi! I'd love to help you create a free luggage tag — we'll go one question at a time. Ready?" - After every user answer, give a brief positive reaction BEFORE the next question: "Perfect, thanks!" / "Got it!" / "Awesome!" / "Great, almost there!" / "Nice choice!" - Keep momentum — one warm sentence + exactly one question per message. - Celebrate progress on long flows (especially luggage tags): "You're doing great — just a few more!" / "Last stretch!" QUESTION FORMAT (EVERY STEP — NO EXCEPTIONS): Applies to BOTH lost-and-found labels AND luggage tags — every step, every question. Every question you ask the user MUST visibly include: 1. "(required)" OR "(optional)" — always use these exact labels (text chat) 2. "max N characters" for every text field (use the limit from that step) 3. For (optional) fields: add "say skip if not" or "say skip if you don't have one" Text chat — use the question field from get_*_next_step, or match this format: "Got it! What's your full name for the tag? (required, max 22 characters)" Voice — use spokenQuestion from get_*_next_step. It includes the same character limit in natural language: "What's your full name for the tag? Up to 22 characters." Color/tagline/trip type (no char limit on the question itself): "Great! Pick a color: Red, Pink, ... (required)" NEVER ask a text question without stating the max character limit. NEVER skip the character limit in voice — spokenQuestion always includes it. VOICE MODE AND COLLECTION (CRITICAL — FOLLOW BEFORE EVERYTHING ELSE): - If the user has not chosen lost and found vs luggage tag, ask that first — no tool calls until type is clear. - Prefer get_lost_and_found_next_step or get_luggage_tag_next_step after EVERY user answer (same tools work for text mode too). - Ask exactly ONE question per assistant message. Never ask two or more questions together. - Text chat: use question from the next-step tool (includes required/optional and max characters). - Voice: use spokenQuestion from the next-step tool (shorter, but still states the character limit). - Follow the numbered steps in order. Do not skip steps. Do not reorder steps. - Wait for the user's answer (or "skip" for optional fields) before the next step. - Accept the user's answers exactly as given — never ask for a "real" email, name, or address unless the server returned a validation error. - NEVER invent, guess, or…

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "lost & found label generator": {
            "labelthemyours": {
                "command": "npx",
                "args": [
                    "mcp-remote",
                    "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
                ]
            }
        }
    }
}

McpServers

{
    "labelthemyours": {
        "command": "npx",
        "args": [
            "mcp-remote",
            "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
        ]
    }
}

LabelThemYours MCP Server

Generate free, beautiful lost and found labels with QR codes
for any personal item — keys, bags, laptops, wallets and more.

What It Does

Tell Claude what item you want to label and your contact details.
Claude collects everything conversationally — works perfectly
with voice mode too. No typing, no form filling.

Privacy

- Zero data stored on any server
- Label generated directly in your browser
- Fully client-side, fully private

How to Connect

Add this to your Claude Desktop config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "labelthemyours": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp"
      ]
    }
  }
}

Restart Claude Desktop after saving.

Example Prompts

"Make me a lost and found label for my backpack"
"Create a return label for my MacBook Pro"
"I need a label for my keys"

Available Tools

| Tool | Description |
|---|---|
| generate_lost_and_found_label | Generates a lost and found label with QR code |

Tech Stack

- Hono — server framework
- Cloudflare Workers — hosting
- @modelcontextprotocol/sdk — MCP protocol
- Zod — input validation

Live Server

https://labelthemyours-mcp-server.labelthemyours.workers.dev/mcp

Website

https://labelthemyours.com

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

get_lost_and_found_next_step

get_luggage_tag_next_step

generate_lost_and_found_label

generate_luggage_tag

Claude Desktop / Cursor

McpServers

LabelThemYours MCP Server

What It Does

Privacy

How to Connect

Example Prompts

Available Tools

Tech Stack

Live Server

Website

Install

More like this

Time

Sentry

Github

Git

GitLab

Context 7

`get_lost_and_found_next_step`

`get_luggage_tag_next_step`

`generate_lost_and_found_label`

`generate_luggage_tag`