-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Reference material that lives outside the README. The MCP server exposes 22 FloopFloop tools to any LLM host that speaks the Model Context Protocol — Claude Desktop, Cursor, Zed, Cline, Continue, and others.
| Question | Where to look |
|---|---|
| "How do I install and configure it in my LLM host?" | README on the main repo — Claude Desktop + Cursor + generic stdio snippets |
| "Why does the MCP do X this way?" | FAQ (this wiki) |
| "My host doesn't show the tools, what now?" | Troubleshooting (this wiki) |
| "What changed between releases?" | npm version history |
| "What does each tool do exactly?" | README — Tools section |
LLM host ←→ @floopfloop/mcp (this) ←→ @floopfloop/sdk (Node) ←→ /api/v1/*
The MCP wraps the Node SDK and re-exposes a curated subset of its surface as MCP tools. Most "why does it work this way" questions about the underlying API live in the Node SDK wiki — this wiki is for MCP-host-specific concerns (configuration, tool discovery, stdio quirks).
Same backend, different surface. If you're building on top of FloopFloop directly rather than driving it from an LLM host:
-
@floopfloop/sdk— Node 20+ -
floopfloop— Python 3.10+ -
github.com/FloopFloopAI/floop-go-sdk— Go 1.22+ -
floopfloop— Rust 2021 / 1.75+ (crates.io) -
floopfloop— Ruby 3.0+ -
floopfloop/sdk— PHP 8.1+ -
floop-cli— terminal binary
Open an issue at floop-mcp/issues describing what you tried to look up and where you expected to find it. A wiki page is cheap to add — better that than another stuck user.