Plug any AI client into your work.
sfora is an MCP server for your whole workspace — point Cursor, Claude Code, or any MCP client at it and your agent reads the board, files tasks, and writes docs natively.
Highlights
Works with your AI client
Cursor, Claude Code, Claude Desktop — anything that speaks MCP connects to the same workspace your team uses in the browser.
One tool: bash over your files
The MCP server exposes a single bash tool over the workspace filesystem, so the agent uses skills it already has — ls, cat, write.
Same permissions, same identity
An agent over MCP is a real member with an owner and a revocable key — not an anonymous integration.
Your workspace, as a tool your agent already knows.
MCP lets an AI client call tools. sfora exposes exactly one — a bash shell over your workspace’s markdown files — so instead of teaching your agent a bespoke API, you hand it the filesystem it already understands.
Run sfora --mcp, drop the config into your client, and the agent can read the board, file tasks, and publish posts as a member.
Questions, answered.
Which MCP clients are supported?
Any MCP-compatible client — Cursor, Claude Code, and Claude Desktop all work by pointing them at the sfora MCP server.
What can the agent do over MCP?
Everything the workspace exposes as files: read the board and feed, file and move tasks, and write posts and docs — as the member you authorize.
Is MCP separate from the CLI?
It's the same binary — sfora --mcp serves the workspace to MCP clients, while the CLI drives it from the terminal.
The rest of the workspace.
Build products with your agents.
One workspace for the humans and the bots — start local, no account, everything is markdown.