Luckycola MCP Server

LuckyCola的开放MCP服务

Local serverstdioTypeScript

What is the Luckycola MCP MCP server?

LuckyCola的开放MCP服务. Exposed over MCP by the luckycola mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

// 获取菜谱 await callTool("getFoodMenu", { foodTitle: "番茄炒蛋" }); ```

Its toolset

Everything the assistant can do here goes through one of these:

  • checkImage — The checkImage tool exposed by this server
  • getFoodMenu — The getFoodMenu tool exposed by this server

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at luckycola-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 3 environment variables: LUCKYCOLA_OPEN_KEY, LUCKYCOLA_OPEN_UID, MCP_FILE_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Luckycola MCP's toolset — checkImage, getFoodMenu — is a fair guide to whether it matches your workflow. It is maintained by mingle98; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Luckycola MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the luckycola mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
checkImageThe checkImage tool exposed by this server.
getFoodMenuThe getFoodMenu tool exposed by this server.

How to install the Luckycola MCP MCP server

或

**下载到本地使用**
```json
{
  "mcpServers": {
    "luckycola-mcp": {
      "command": "node",
      "args": ["/path/to/luckycola-mcp/build/index.js"],
      "env": {
        "LUCKYCOLA_OPEN_KEY": "你的APPKey",
        "LUCKYCOLA_OPEN_UID": "你的UID",
        "MCP_FILE_PATH": "希望进行文件/图片操作的目录路径,例如: /Users/yourname/Desktop/testDir"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
LUCKYCOLA_OPEN_KEYCredential the server authenticates with.Yes
LUCKYCOLA_OPEN_UIDConfiguration value read at startup.Optional
MCP_FILE_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Luckycola MCP to checkImage.
  • Use Luckycola MCP to getFoodMenu.

Frequently asked questions

It connects Luckycola MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (checkImage, getFoodMenu) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Luckycola MCP directly.