Connect your AI app
Every app needs the same thing: this server address, and your flff email and password the first time.
https://mcp.flff.fi/mcp
Claude (claude.ai and the desktop app)
- Open Settings → Connectors and choose Add custom connector.
- Give it a name, for example
flff, and pastehttps://mcp.flff.fi/mcpas the URL. Leave the advanced settings empty. - Click Connect. A flff sign-in page opens: sign in with your flff email and password.
- On the next page, review what Claude may do and click Allow. Leave "Allow changes to files" ticked if you want Claude to edit your site.
- In a new chat, make sure the flff connector is switched on in the chat's tools menu, then ask: "List my flff sites."
ChatGPT
Custom connectors need a paid ChatGPT plan with developer mode. Menu names change from time to time.
- Open Settings → Apps & Connectors, go to the advanced settings and turn on Developer mode.
- Create a connector with the URL
https://mcp.flff.fi/mcpand authentication OAuth. - Sign in on the flff page that opens, then click Allow.
- Turn the connector on in a chat and ask: "List my flff sites."
Claude Code
Run this in your terminal:
claude mcp add --transport http flff https://mcp.flff.fi/mcp
Then start Claude Code, type /mcp, choose flff and Authenticate. Your browser opens the flff sign-in page.
Apps that run AI on your computer
Many local apps, such as Locally Uncensored, can only start MCP servers as a command rather than connect to an address. A small bridge called mcp-remote fills the gap: it runs on your computer, handles the sign-in, and passes everything on to flff.
- Install Node.js (version 18 or newer) if you don't have it.
- Sign in once from a terminal. Local apps give up if the sign-in takes too long, so do it here first:
Your browser opens the flff sign-in page. Sign in, click Allow, and close the terminal when it says it's connected. Your login is saved on your computer.npx -y mcp-remote https://mcp.flff.fi/mcp - Add the server in your app: command
npx, arguments-y mcp-remote https://mcp.flff.fi/mcp.
Locally Uncensored, step by step
- Settings → Agent → MCP Servers: add the server as above, then click Connect. Check that it lists the flff tools (
list_sites,read_file,write_fileand so on). - Settings → Agent → Permissions: make sure the MCP row isn't set to Blocked. "Ask First" is fine: you'll approve each change.
- Open a new, empty chat and switch on Agent before your first message. If the Agent switch is greyed out, the model can't use tools: pick one marked as tool-capable in the Models tab.
- Ask: "Run the list_sites tool." Naming the tool makes sure the model sees it.
Local models vary a lot in how well they use tools. If the model talks about changes instead of making them, try a larger model with tool calling.
What to ask once you're connected
- "List my flff sites."
- "Show me the files on my site, then make a homepage for my bakery with our opening hours."
- "Change the background to dark green and make the headings bigger."
- "Add an About page and link to it from the homepage."
The tools your AI gets:
| Tool | What it does |
|---|---|
list_sites | Lists the sites you can use, whether you can change them, and each site's web address |
list_files | Lists the files in a folder of a site |
read_file | Reads a file |
write_file | Creates a file or replaces it completely; live immediately, and it tells your AI the page's address |
make_directory | Creates a folder |
move | Moves or renames a file or folder |
delete | Deletes a file or folder |
write_file replaces the whole file. Keep a copy of pages you like, or ask your AI to show you a file before rewriting it.If something doesn't work
| You see | What it means |
|---|---|
| "no bearer token" when you open the server address in a browser | That's expected: the address is for apps, not browsers. Your app adds the sign-in. |
| The AI says it has no flff tools | Start a new chat after connecting. In local apps, check the server is connected (see above) and Agent mode is on. |
| "This connection was not granted sites:write" | You connected read-only. Disconnect the app, connect again, and leave "Allow changes to files" ticked. |
| A site isn't listed | Your login hasn't been given access to it. Ask us. |
| "Request initialize timed out" in a local app | Do the one-time sign-in from a terminal first (step 2 under local apps). |
Still stuck? Tell us roughly when you tried and what you saw. We can follow the request on our side.