What is implemented is the querying half: views, the items inside them, one item's detail, and the role configuration. Writing — creating work items, moving them through a workflow, commenting — is mapped in the README but unbuilt, and the repository is archived in favour of Feishu's own MCP server. Worth knowing before you plan around it.
An MCP server over the Feishu Project (飞书项目) Open API. It lets an assistant look up a project's views, list the work items inside a view, open a single work item, read the metadata needed to create one, and read the process-role configuration. The repository is archived: Feishu has since shipped an official MCP server, and this one is no longer updated.
Working today, per the repository's own feature checklist: login and authentication against the Open API; the project's view list; the work-item list for a view; a single work item's detail; the metadata required to create a work item; and the process-role configuration. Creating, updating and deleting views and work items, attachments, space management, workflows, sub-tasks and comments are listed as unchecked — the API surface is mapped out but not implemented.
A Feishu Project plugin credential, which is four values in the server's environment: `FS_PROJ_PROJECT_KEY` (the project), `FS_PROJ_USER_KEY` (the user), and `FS_PROJ_PLUGIN_ID` with `FS_PROJ_PLUGIN_SECRET` from the Open API plugin. `FS_PROJ_BASE_URL` defaults to `https://project.feishu.cn/`. Run it with `uvx mcp-feishu-proj@latest --transport stdio`; Docker Compose and Kubernetes manifests are included, with the four values supplied as a Secret in the cluster case.
One command plus a key — uvx mcp-feishu-proj@latest --transport stdio, then supply credentials