Is io.github.YOLKINS/weeek-mcp safe to use?

io.github.YOLKINS/weeek-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install io.github.YOLKINS/weeek-mcp?

io.github.YOLKINS/weeek-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.YOLKINS/weeek-mcp do?

io.github.YOLKINS/weeek-mcp provides 5 tools: Quickstart, Tools, Configuration, Troubleshooting, Errors. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.YOLKINS/weeek-mcp?

io.github.YOLKINS/weeek-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is io.github.YOLKINS/weeek-mcp actively maintained?

io.github.YOLKINS/weeek-mcp is actively maintained — last commit was 2 days ago.

io.github.YOLKINS/weeek-mcp

weeek-mcp

Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.

418/wk 5 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 2d ago

Works with most clients

Transport: stdio, http

5 tools · ~173 tok

Grade A · 0.1% of 200K ctx

MCPpedia last refreshed this data 2h ago

Edit this pageView history

io.github.YOLKINS/weeek-mcp is an MCP server that local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools. Its tool list has not been published yet over stdio and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "weeek": {
      "env": {
        "WEEEK_ACCESS_TOKEN": "YOUR_WEEEK_TOKEN_HERE"
      },
      "args": [
        "-y",
        "weeek-mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-yolkins-weeek-mcp)](https://mcppedia.org/s/io-github-yolkins-weeek-mcp)

Read me

What io.github.YOLKINS/weeek-mcp does

Local, read-only-by-default MCP server for Weeek — with opt-in write tools.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'weeek-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

89/100across 5 weighted dimensions

How we score →

0255075100

−11

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked weeek-mcp against OSV.dev.

Inventory

Tools (5)

Click any tool to inspect its schema.

~173 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.YOLKINS/weeek-mcp safe to use?: io.github.YOLKINS/weeek-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.YOLKINS/weeek-mcp?: io.github.YOLKINS/weeek-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.YOLKINS/weeek-mcp do?: io.github.YOLKINS/weeek-mcp provides 5 tools: Quickstart, Tools, Configuration, Troubleshooting, Errors. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.YOLKINS/weeek-mcp?: io.github.YOLKINS/weeek-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.YOLKINS/weeek-mcp actively maintained?: io.github.YOLKINS/weeek-mcp is actively maintained — last commit was 2 days ago.

Similar servers

Others in other

View all →

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

123 3

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.2k 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

329 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.YOLKINS/weeek-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "weeek": {
      "env": {
        "WEEEK_ACCESS_TOKEN": "YOUR_WEEEK_TOKEN_HERE"
      },
      "args": [
        "-y",
        "weeek-mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-yolkins-weeek-mcp)](https://mcppedia.org/s/io-github-yolkins-weeek-mcp)

Read me

What io.github.YOLKINS/weeek-mcp does

Local, read-only-by-default MCP server for Weeek — with opt-in write tools.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'weeek-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

weeek-mcp

Local, read-only-by-default MCP server for Weeek — with opt-in write tools.

Русская версия README

weeek-mcp connects AI clients (Claude Desktop, Claude Code, Cursor, MCP Inspector) to your Weeek workspace over stdio. It is read-only by default — a default install can list projects, tasks, boards, members and tags but change nothing — and exposes five write tools only when you opt in with READ_ONLY=false. Runs on Node ≥ 20; install with npx, no clone or build required.

Why this one

On npm. npx -y weeek-mcp works today — no clone, no build, no absolute paths.
Read-only by default, with composable gates. Writes are simply not registered unless you opt in; ENABLED_TOOLS whitelists a subset and MAX_RESPONSE_CHARS caps every payload. Server-side, not client convention.
Bilingual. Full EN ↔ RU documentation parity.
Granular error model. Nine distinct error codes with agent-readable messages, so a model knows when to retry versus give up without parsing prose.

Quickstart

The recommended install path is npx — no clone, no build. Drop examples/claude_desktop.mcp.json into your MCP client config, replace YOUR_WEEEK_TOKEN_HERE with a real token from https://app.weeek.net/ws/_/settings/apps/api, and restart the client:

{
  "mcpServers": {
    "weeek": {
      "command": "npx",
      "args": ["-y", "weeek-mcp"],
      "env": {
        "WEEEK_ACCESS_TOKEN": "YOUR_WEEEK_TOKEN_HERE"
      }
    }
  }
}

npx downloads weeek-mcp on first launch and caches it. Cursor and Cline use the same mcpServers shape — see examples/cursor.mcp.json and examples/cline.mcp.json. Other env vars have safe defaults; override only what you need (see Configuration). If npx cannot find node (typical with nvm), see Troubleshooting; for a zero-dependency smoke test see docs/smoke.md.

examples/ lives on GitHub only — the npm tarball ships dist/ + README.md + README.ru.md + LICENSE.

Tools

Ten read tools are exposed by default. All fifteen appear only under READ_ONLY=false (see Enabling write tools).

Read tool	Returns
`ping`	`pong: <msg>` — transport health check, no API call, no token
`weeek_get_me`	the authenticated user (`id`, `email`, `name`) — confirms the token
`weeek_list_projects`	every project visible to the token
`weeek_get_project`	a single project by id, including its `description`
`weeek_list_tasks`	one page of tasks (filters + offset/`per_page` pagination)
`weeek_get_task`	a single task by id, with multi-assignee fields
`weeek_list_members`	every workspace member
`weeek_list_tags`	every tag
`weeek_list_boards`	every board in a project
`weeek_list_board_columns`	every column of a board, in sort order

Write tool (`READ_ONLY=false`)	Does
`weeek_complete_task`	flips the completion flag; `completed: false` re-opens
`weeek_move_task`	moves a task to a board column (a column is a status)
`weeek_create_task`	files a new task and returns it with its new id
`weeek_update_task`	edits title / priority / type / due date
`weeek_set_task_mr_link`	records a merge/pull-request URL in a custom field

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

89/100across 5 weighted dimensions

How we score →

0255075100

−11

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked weeek-mcp against OSV.dev.

Inventory

Tools (5)

Click any tool to inspect its schema.

~173 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.YOLKINS/weeek-mcp safe to use?: io.github.YOLKINS/weeek-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.YOLKINS/weeek-mcp?: io.github.YOLKINS/weeek-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.YOLKINS/weeek-mcp do?: io.github.YOLKINS/weeek-mcp provides 5 tools: Quickstart, Tools, Configuration, Troubleshooting, Errors. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.YOLKINS/weeek-mcp?: io.github.YOLKINS/weeek-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.YOLKINS/weeek-mcp actively maintained?: io.github.YOLKINS/weeek-mcp is actively maintained — last commit was 2 days ago.