Meegle Mcp

Interact with Meegle project management system via MCP protocol

Security Scan

The skill appears to implement the claimed Meegle MCP proxy, but its declared requirements and runtime behavior are inconsistent (missing declared env var), and the included setup script persists sensitive keys to shell profiles and the proxy places keys in query parameters and logs, which deserves caution.

Purpose & Capability

The skill's name, README, SKILL.md, and proxy implement an MCP proxy to talk to Meegle/Larksuite (this matches the stated purpose). However, the registry metadata only declares MEEGLE_USER_KEY as required while the code and instructions clearly require MEEGLE_MCP_KEY (and optionally MEEGLE_MCP_URL). The missing declared env var is an inconsistency that could mislead users about what secrets the skill needs.

Instruction Scope

Runtime instructions and the included setup script instruct the user to write MEEGLE_USER_KEY and MEEGLE_MCP_KEY into shell profile files (~/.bashrc, ~/.zshrc). The proxy forwards JSON-RPC messages to the configured MCP endpoint and constructs the endpoint URL embedding both keys as query parameters. The proxy also prints a partial user key to stderr on startup. These behaviors persist secrets to disk (in plain text shell profiles), expose credentials in request URLs (which can be logged by intermediaries/servers), and write identifying fragments to logs — all of which increase risk and should be considered before installing.

Install Mechanism

There is no external download/install spec — the package is instruction + local scripts. That reduces remote-install risk. The setup.sh script is included and will modify the user's shell config (and export credentials for the current session). Making the proxy executable and running node are standard for this type of skill; there are no remote code fetches in the provided files.

Credentials

The skill requires sensitive credentials: MEEGLE_USER_KEY and MEEGLE_MCP_KEY. The registry metadata only declared MEEGLE_USER_KEY (primaryEnv), but both keys are required at runtime by scripts — a transparency problem. The setup script advises saving both keys in shell profiles (plain text). The proxy constructs URLs with these keys as query parameters, which may be logged by servers or intermediaries. Requesting/storing two keys is reasonable for an API proxy, but the omission from declared requirements and the recommended storage method are disproportionate risks that should be addressed.

Persistence & Privilege

The skill is not set to always:true and allows user invocation (normal). It does not modify other skills or system settings. However, the included setup.sh persists credentials to the user's shell configuration files, creating lasting secrets on disk — this is expected for a local integration but is a privilege with security implications and should be noted to users.

What to consider before installing

This skill mostly does what it says (an MCP proxy to Meegle), but there are a few red flags to consider before installing: - The skill actually needs two secrets (MEEGLE_USER_KEY and MEEGLE_MCP_KEY), but the registry only declared MEEGLE_USER_KEY. Expect to provide both keys. - setup.sh writes those keys into your shell profile (~/.bashrc, ~/.zshrc) in plain text. If you are concerned about storing secrets on disk, don’t run the script; instead store keys in a secure vault or use OpenClaw's secure config mechanism. - The proxy embeds both keys in the request URL query string when contacting the MCP endpoint. Even over HTTPS, query parameters can be logged by servers or intermediaries. If possible, prefer sending credentials in headers or bearer tokens, or confirm that your MCP server is comfortable with query-based auth and logs are acceptable. - The proxy prints a fragment of your user key to stderr on startup (useful for debugging), which could end up in logs; be aware of log exposure. - If you proceed, prefer a dedicated, least-privilege service account for automation, rotate keys after testing, and review the mcp-proxy.js and setup.sh code yourself or with a trusted admin. If you want to be cautious: refuse or modify the setup script (avoid writing secrets to shell profiles), add MEEGLE_MCP_KEY to the skill metadata or verify with the publisher, and consider using a secure secrets store instead of environment variables in shell files.

Meegle MCP Skill

Integrate Meegle (visual workflow and project management tool) with OpenClaw using the Model Context Protocol (MCP).

What is Meegle?

Meegle is a leading visual project management tool powered by Larksuite, designed for agile teams. It provides:

• Customizable Kanban boards and Gantt charts
• Real-time collaboration with integrated chat
• Workflow automation and custom pipelines
• Time tracking and analytics dashboard
• Client portal access for external stakeholders

Setup

Prerequisites

You need:

1. A Meegle account with API access
2. Your MEEGLE_USER_KEY from your Meegle workspace

Configuration

Option 1: Environment Variable (Recommended)

Set your user key as an environment variable:

export MEEGLE_USER_KEY="your_user_key_here"
export MEEGLE_MCP_KEY="your_mcp_key_here"

Add this to your shell profile (~/.bashrc, ~/.zshrc, etc.) to persist across sessions.

Option 2: OpenClaw Config

Add the MCP server configuration to your OpenClaw settings:

1. Edit or create your OpenClaw MCP servers config file
2. Add the Meegle MCP server configuration:

{
  "mcpServers": {
    "meegle": {
      "command": "node",
      "args": ["{baseDir}/scripts/mcp-proxy.js"],
      "env": {
        "MEEGLE_USER_KEY": "your_user_key_here",
        "MEEGLE_MCP_URL": "https://project.larksuite.com/mcp_server/v1",
        "MEEGLE_MCP_KEY": "your_mcp_key_here"
      },
      "status": "active"
    }
  }
}

Option 3: Using mcporter (Alternative)

If you have mcporter installed:

mcporter add meegle \
  --url "https://project.larksuite.com/mcp_server/v1?mcpKey=your_mcp_key_here&userKey={user_key}" \
  --env MEEGLE_USER_KEY=your_user_key_here

Installation

Via ClawHub (Recommended):

clawhub install meegle-mcp

From GitHub:

git clone <this-repo-url> meegle-mcp
cd meegle-mcp
./scripts/setup.sh

Then restart OpenClaw and verify installation:

openclaw skills list | grep meegle

Available Tools

Once configured, the Meegle MCP server provides various tools for project management. Common operations include:

Project Management

• List Projects: View all projects in your workspace
• Create Project: Set up new projects with custom workflows
• Update Project: Modify project details, status, or members

Task Operations

• Create Task: Add new tasks with assignees, due dates, and priorities
• List Tasks: Filter and search tasks by project, assignee, or status
• Update Task: Change task properties, move between workflow stages
• Get Task Details: View comprehensive task information

Workflow Management

• Get Workflows: List available workflow templates
• Apply Workflow: Assign workflows to projects
• Update Workflow Stage: Move items through workflow stages

Team Collaboration

• Add Members: Invite team members to projects
• List Members: View project participants and roles
• Update Permissions: Manage access levels

Analytics & Reporting

• Get Project Stats: View progress, completion rates, and metrics
• Time Tracking: Log and query time entries
• Generate Reports: Create custom reports on project data

Usage Examples

Creating a New Project

Create a new Meegle project called "Q1 Website Redesign" with a Kanban workflow

Managing Tasks

Show me all high-priority tasks assigned to me in Meegle

Create a task in Meegle: "Update landing page copy" assigned to @designer, due next Friday

Workflow Operations

Move the task "Homepage mockups" to the "In Review" stage in Meegle

Team Coordination

Add [e-mail] as a contributor to the "Mobile App" project in Meegle

Reporting

Generate a summary of completed tasks in Meegle for the past week

Limitations

• Authentication: Requires a valid MEEGLE_USER_KEY with appropriate permissions
• Rate Limits: Subject to Meegle API rate limits (check your plan)
• Read-Only Operations: Some operations may be restricted based on your role
• Workspace Scope: Only accesses projects in your authorized workspace

Security Notes

• Never commit your MEEGLE_USER_KEY to version control
• Store credentials in environment variables or secure config files
• Review permissions before granting OpenClaw access to Meegle
• Consider using a dedicated service account for automation

Troubleshooting

"Authentication failed" error

• Verify your MEEGLE_USER_KEY is correct
• Ensure the key has not expired or been revoked
• Check that your Meegle account has API access enabled

"MCP server not responding"

• Verify network connectivity to project.larksuite.com
• Check that the MCP server URL and key are correct
• Review OpenClaw logs: openclaw logs --filter=meegle

Tools not appearing

• Restart OpenClaw after installation
• Check skill is loaded: openclaw skills list
• Verify environment variables are set correctly

Resources

• Meegle Official Website
• Meegle Documentation
• Larksuite Platform
• OpenClaw Skills Documentation
• Model Context Protocol Spec

Feedback

Issues or suggestions? Open an issue on the skill repository or contact via ClawHub.

---

Note: This skill uses the Model Context Protocol to communicate with Meegle's MCP server. Tool availability and capabilities depend on your Meegle plan and permissions.