Provides local MDict dictionaries to MCP clients via stdio and asks the MCP bridge to serve /path/to/mdicts with uvx.
Configuration
View docs{
"mcpServers": {
"cdpath-mdict-mcp": {
"command": "uvx",
"args": [
"mdict-mcp"
],
"env": {
"MDICT_DICTIONARY_DIR": "YOUR_PATH_TO_MDISTS"
}
}
}
}MDict MCP Server exposes your MDict dictionaries to MCP clients, enabling fast, local dictionary access through a lightweight MCP bridge. It lets clients like Claude Desktop or ChatWise query your dictionary data without exposing raw files directly, improving integration and performance for dictionary apps.
Connect with an MCP client by pointing the client at your local MCP server configuration. You provide the runner and environment it needs, and the client can request dictionary data through the MCP protocol. Use the standard local testing flow to verify that your MDict dictionaries are accessible, then scale by running the same setup as a background service.
Prerequisites you will rely on are the MCP tooling and the MDict utilities already referenced in your project’s dependencies. Before you start, ensure you have a working environment where MCP tooling can run and your dictionaries are prepared in a directory you can reference.
1) Prepare your dictionary directory. Create a directory path that will contain your MDict dictionaries, for example /path/to/mdicts/. This path will be used by the MCP server as an environment variable.
2) Configure the MCP server runner for your client. You will provide a small MCP server configuration that runs the MCP bridge with the MDict dictionaries. Use the following patterns to configure the client side: the MDict MCP runner is launched through the uvx launcher with the mdict-mcp task, and you set MDICT_DICTIONARY_DIR to the dictionary directory.
3) Test the local setup. Run the local test command to verify the MCP server starts and serves your dictionaries.
uv --directory $HOME/Developer/mdict-mcp run mdict-mcp
# Or, with the explicit environment and command for your client setup
# Claude Desktop style configuration uses uvx with a dictionary dir set in env
# env MDICT_DICTIONARY_DIR=/path/to/mdicts/ uvx mdict-mcp
# For a direct local test, you can also rely on the provided test command if you follow the same directory structure.- The environment variable MDICT_DICTIONARY_DIR must point to the directory containing your MDict dictionaries. This is the only required env var shown in the examples.