Weeeking MCP Server

What this does

Weeeking exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

WEEEK_API_TOKEN
WEEEK_TOKEN
READ_ONLY
WEEEK_LANG
WEEEK_ALLOW_ACTIONS
WEEEK_DENY_ACTIONS
WEEEK_PROFILE
WEEEK_BASE_URL
WEEEK_DISABLE_KEYCHAIN
WEEEK_MAX_RESPONSE_CHARS
WEEEK_RPS
WEEEK_RPS_BURST
WEEEK_LOG

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Weeeking?

Run the Claude Code command in the install section to add Weeeking to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Weeeking?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Weeeking as well.

Does Weeeking need an API key?

Yes. Before it can run, set these environment variables: WEEEK_API_TOKEN, WEEEK_TOKEN, READ_ONLY, WEEEK_LANG, WEEEK_ALLOW_ACTIONS, WEEEK_DENY_ACTIONS, WEEEK_PROFILE, WEEEK_BASE_URL, WEEEK_DISABLE_KEYCHAIN, WEEEK_MAX_RESPONSE_CHARS, WEEEK_RPS, WEEEK_RPS_BURST, WEEEK_LOG. They go in the env block of your MCP config.