Feishu Markdown Mcp
Bridge Feishu (Lark) Markdown docs and your coding agent so specs, runbooks, and meeting notes stay in sync with implementation work.
Overview
feishu-markdown-mcp is a MCP server for the Build phase that connects agents to Feishu Markdown documents for specs and operational notes.
What is this MCP server?
- stdio MCP server feishu-markdown-mcp v0.1.3 from npm
- Targets Feishu Markdown workflows for team knowledge and specs
- Lets agents read and write Markdown-aligned Feishu content in one session
- Fits distributed solo-plus-contractor teams already on Lark/Feishu
- npm registry transport for standard Node-based MCP clients
- Catalog version 0.1.3 with npm package identifier feishu-markdown-mcp
- stdio transport on the published MCP registry entry
Community signal: 25 GitHub stars.
What problem does it solve?
Builders who run specs in Feishu lose context when their agent can only see the git repo and not the Markdown docs the team actually follows.
Who is it for?
Solo founders and tiny teams standardized on Feishu/Lark for internal Markdown specs and runbooks.
Skip if: Teams on Notion-only or Google Docs-only stacks, or anyone needing full Feishu calendar, approval, and chat bot coverage.
What do I get? / Deliverables
After setup, your agent can work with Feishu Markdown content alongside code so documentation updates ride the same iteration loop as implementation.
- Agent-driven reads and updates aligned with Feishu Markdown documents
- Specs and runbooks that stay consistent with repository changes
Recommended MCP Servers
Journey fit
Build docs is the canonical shelf because the server’s core job is authoring and maintaining Markdown-oriented knowledge inside Feishu workflows that precede and accompany shipping code. Docs captures internal specifications, API notes, and handoff material indie teams often keep in Feishu rather than a standalone wiki.
How it compares
Feishu Markdown MCP bridge, not a generic Markdown file skill on local disk.
Common Questions / FAQ
Who is feishu-markdown-mcp for?
It is for developers and PMs using Feishu or Lark who want Claude Code, Cursor, or similar agents to interact with Markdown-style team docs during builds.
When should I use feishu-markdown-mcp?
Use it while writing specs, updating internal API documentation, or syncing implementation details with Feishu-hosted Markdown during build and grow content work.
How do I add feishu-markdown-mcp to my agent?
Install the npm package feishu-markdown-mcp v0.1.3, configure it as a stdio MCP server io.github.huandu/feishu-markdown-mcp, and supply Feishu app credentials per the GitHub repository instructions.