Metadata-Version: 2.4
Name: feishu-mcp
Version: 0.2.0
Summary: A safe Feishu MCP server for task-delivery notifications
Author: Internal Platform Team
License-Expression: LicenseRef-Proprietary
Requires-Python: >=3.11
Description-Content-Type: text/markdown
Requires-Dist: mcp<2.0.0,>=1.0.0

# Feishu MCP (uvx launcher)

This package runs the Feishu task-delivery MCP over stdio. It is designed for
employees who use a local MCP client and should not need to create a Python
virtual environment or manually install dependencies.

## What `uvx` solves

`uvx` downloads a pinned version of this package, creates an isolated cached
environment, and runs the `feishu-mcp` command. Employees still need the `uv`
tool installed, but do not need Python, `pip`, or the `mcp` package installed
separately.

For a centralized remote MCP service, use a versioned container/service image
instead; `uvx` is intended for client-side stdio launch and local development.

## Build a distributable wheel

From this repository:

```powershell
uv build --wheel --out-dir dist
```

Publish the generated wheel to an internal Python package index for employee
use. Pin the package version in every MCP configuration.

## Codex / Amazon Quick configuration

After installing `uv`, configure the MCP client with a versioned package. The
environment values below are examples; store the actual secret in the
client's secure configuration facility or a managed environment, never in the
repository.

```toml
[mcp_servers.feishu]
command = "uvx"
args = ["--from", "feishu-mcp==0.2.0", "feishu-mcp"]
enabled = true

[mcp_servers.feishu.env]
FEISHU_APP_ID = "cli_xxxxxxxxxxxxx"
FEISHU_APP_SECRET = "set-in-secure-configuration"
FEISHU_TARGETS_FILE = "C:\\Users\\employee\\.feishu-mcp\\targets.json"
FEISHU_AUDIT_LOG = "C:\\Users\\employee\\.feishu-mcp\\audit.jsonl"
```

For a local wheel smoke test before publishing, substitute the package source
with the absolute wheel path:

```powershell
uvx --from "D:\\AmazonQuickWorkspace\\dist\\feishu_mcp-0.2.0-py3-none-any.whl" feishu-mcp
```

## Updating employees

1. Build and publish a new immutable package version, for example `0.2.1`.
2. Update the pinned version in the managed MCP configuration.
3. Restart the MCP client. `uvx` obtains the new version automatically.

Do not use an unpinned package version in production. It makes incident
rollback and security review unnecessarily difficult.
