mcp-acronym-lookup

What is mcp-acronym-lookup?

A lightweight, configuration-driven MCP server that ingests a CSV file of acronyms and initialisms to expose a lookup tool that returns their full meanings and descriptions as JSON.

How to use mcp-acronym-lookup?

Set the required ACRONYM_FILE environment variable to the path of a three‑column CSV (acronym, full form, description). By default the server runs in stdio mode; pass the --sse <addr> flag (e.g., :8080) to run in SSE mode with endpoints at /mcp/sse and /mcp/message.

Key features of mcp-acronym-lookup

• Single tool resolves acronyms and initialisms from a CSV file.
• Returns all matching definitions as JSON.
• Case‑insensitive matching; ignores non‑alphabetic characters.
• Supports only one CSV file per server instance.
• Runs in stdio mode by default, with optional SSE mode.

Use cases of mcp-acronym-lookup

• Look up acronyms in a chat application using an AI assistant.
• Provide instant definitions for technical acronyms in documentation.
• Resolve custom initialisms from an internal glossary via any MCP client.
• Build a lightweight knowledge tool for domain‑specific abbreviations.

FAQ from mcp-acronym-lookup

What CSV format does mcp-acronym-lookup expect?

The CSV must have three columns in order: acronym, full form, and description. It should be UTF‑8 encoded and may include a header row.

How do I run mcp-acronym-lookup in SSE mode?

Use the --sse command‑line flag followed by an address (e.g., :8080). This exposes an SSE endpoint at /mcp/sse and a message endpoint at /mcp/message.

Are acronym lookups case‑sensitive?

No, matches are case‑insensitive. Input strings are sanitized by removing non‑alphabetic characters before lookup.

Can I use multiple CSV files with a single instance?

No, the server only supports one CSV file per instance.

What happens if multiple definitions exist for the same acronym?

All definitions that match the sanitized key are returned in a list.