Wekan Mcp

Created By
namar0x03097 months ago
MCP server for https://github.com/wekan/wekan! It also includes scripts to automatically generate Wekan API tokens and configure your environment.
Overview

what is Wekan MCP?

Wekan MCP is a server project designed to facilitate the management of Wekan instances by automating the generation of API tokens and environment configuration.

how to use Wekan MCP?

To use Wekan MCP, run the provided scripts for your platform to generate your Wekan API token and configure your environment. You can also manually configure the environment by editing the .env file.

key features of Wekan MCP?

  • Automatic generation of Wekan API tokens
  • Easy environment configuration through scripts
  • Testing and debugging tools for the MCP server

use cases of Wekan MCP?

  1. Simplifying the setup of Wekan instances for developers.
  2. Automating token management for Wekan users.
  3. Facilitating development and debugging of Wekan applications.

FAQ from Wekan MCP?

  • How do I generate an API token?

You can generate an API token by running the appropriate script for your platform (Windows or Linux/macOS).

  • Can I configure Wekan MCP manually?

Yes! You can manually configure the environment by copying the .env.example file and filling in your details.

  • What is the MCP Inspector?

The MCP Inspector is a tool for development and debugging the MCP server.

Server Config

{
  "mcpServers": {
    "wekan-username": {
      "command": "node",
      "args": [
        "dist/server.js"
      ],
      "env": {
        "WEKAN_BASE_URL": "https://wekan.namar0x0309.com",
        "WEKAN_USERNAME": "username",
        "WEKAN_PASSWORD": "password!"
      },
      "transport": "stdio"
    },
    "wekan": {
      "command": "node",
      "args": [
        "dist/server.js"
      ],
      "env": {
        "WEKAN_BASE_URL": "https://wekan.namar0x0309.com",
        "WEKAN_API_TOKEN": "thetokenyougetfrom_get-wekan-token_script"
      },
      "transport": "stdio"
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
namar0x0309
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago