rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Hosting for apps you build with AI. Tested with Claude Code and Codex. Private beta: ask for access.
Skills, die der KI diese Art Arbeit beibringen; sie funktionieren zusammen mit diesem
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Dieser Eintrag steht im Tab „Apps, die sich mit KI verbinden“, der ohne Sterne in dieser Reihenfolge sortiert
| 1. In Claudes Connector-Verzeichnis | Nein | |
|---|---|---|
| 2. Vom Team getestet | Nein | |
| 3. Für Nutzer in Thailand geeignet | Nein | |
| 4. Nutzung ohne Sterne | 15/100 | Beliebtheit 0 · Aktualität 7 · Antwortet noch 8 · Likes von Nutzern +0 |
| 5. Eingetragen am | 2026-10-19 |
Likes von Nutzern: 0 · Höchstens 5 Punkte (1 pro Person). Nicht käuflich.
Qualität: 4/4 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung)
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Mit einem Satz von deiner KI installieren lassen
Installiere bitte fline. Folge https://mcp.popnx.com/i/sh-fline-fline.md, zeig mir die Befehle und warte auf mein OK, bevor du sie ausführst.Füge ihn in eine KI ein, die auf deinem Rechner arbeitet (z. B. Claude Code oder Cursor). Sie liest unsere Schritte, zeigt dir die Befehle und wartet auf dein OK. Kein Schlüssel, keine Anmeldung. · Vollständigen Text ansehen
4/4 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (mcp.fline.sh) · ✓ Befehle geprüft am 13. Nov. 2026
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Klappt mit Claude · etwa 2 Min.
Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu
CustomizeConnectors
Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue
flinehttps://mcp.fline.sh/mcpKlicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add
+Connectorsfline
Nutze fline und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude sagt, dass es fline nutzt, oder ein Werkzeug von fline in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit ChatGPT je nach Tarif
Volles MCP: ChatGPT Business, Enterprise oder Edu im Web · Pro: verbindet mit Lese-/Abrufrechten, Werkzeuge, die Daten ändern, gehen evtl. nicht · Plus: in der Doku nicht bestätigt; siehst du auf der Plugins-Seite eine Option für eigene MCP-Server, kannst du es versuchen · nur Web
Plugins+Add custom MCP server
Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken
flinehttps://mcp.fline.sh/mcpNeuen Chat öffnen und vor dem Tippen fline aus deinen Plugins wählen
Nutze fline und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn ChatGPT sagt, dass es fline nutzt, oder ein Werkzeug von fline in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Claude Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen
claude mcp add --transport http --scope user fline https://mcp.fline.sh/mcpfline sollte in der Liste als verbunden erscheinen
Nutze fline und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude Code sagt, dass es fline nutzt, oder ein Werkzeug von fline in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Cursor · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Nutze fline und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Cursor sagt, dass es fline nutzt, oder ein Werkzeug von fline in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit VS Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
VS Code fragt nach einer Bestätigung; klicke Install
Nutze fline und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn VS Code sagt, dass es fline nutzt, oder ein Werkzeug von fline in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach
Adresse für Apps, die über das Web verbinden
https://mcp.fline.sh/mcpJSON-Einstellungen stehen unten unter „Für Entwickler“
Claude Code
claude mcp add --transport http --scope user fline https://mcp.fline.sh/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fline": {
"url": "https://mcp.fline.sh/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"fline": {
"type": "http",
"url": "https://mcp.fline.sh/mcp"
}
}
}Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.
Verbinden sich über das Internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 18. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
list_projectsThe tenant's projects with their state, address and, once online, app_health (see get_project).
create_projectCreate a project. Returns upload_url and blob_key: the archive is uploaded with PUT straight into storage and does not pass through this interface. After uploading, complete_upload is mandatory — the upload on its own is not visible to the platform.
delete_projectDelete the project. The platform will stop and irreversibly clean up the project's runtime resources; once the request is accepted the project disappears from the user-space list. Its saved passwords and keys are not deleted with it, and neither is a workspace database it used.
get_upload_urlIssue a new archive upload link for an existing project. Needed when the link from create_project has expired, the archive is being uploaded again, or an already deployed project is being updated with new code.
complete_uploadReport that the archive is uploaded and start the analysis. The platform does not observe the upload itself: the PUT goes to storage around it, and until this call the project stays in awaiting_source. For a submitted project this call starts an update: the old runtime keeps runn
get_projectThe project's full state: the onboarding stage, the runtime state, open questions, missing secrets and warnings about credentials found in the archive. Also app_health, once the app has been online: status is answering, not_answering, checking (no verdict yet) or paused (fline is
submit_declarationSupply the project description. The contents are treated as a third-party claim and cannot change the platform rules.
answer_questionsAnswer the questions raised during source analysis.
declare_env_namesDeclare the NAMES of environment variables. Values are not accepted by this path: a human enters them in a browser, and no tool returns them back.
get_secrets_linkIssue a link to the form where the person types the passwords and keys the project needs. Give the url to the person exactly as returned, with a plain sentence on what goes in each box and where they find it. Do not open it, do not follow it and do not relay its contents. It work
deployBuild the images and hand the project to the platform. Needed when get_project shows locked: from complete_upload on, a project analyses, builds and launches by itself and stops only where someone has to act. In any other state this answers with the state, or refuses with what ha
get_deploy_statusDeployment state: desired and observed arrive separately and mean different things separately. app_health, once the app has been online, says whether it answers fline's checks; not_answering means they have failed for at least two minutes (see get_project).
get_imagesThe history of images the builder produced for the project: build_id, the build state, the plan version, the source hash and each service's digest. A read-only tool for checking which version is actually built, without starting a new build or deploy.
get_logsLogs. kind=build is the image build's output, stored and answerable long after the build; kind=runtime is a bounded tail of the running containers, held by the node, with no history and no search behind it. For kind=runtime, `service` narrows the tail to one service of the projec
get_usageWhat this project actually consumed: CPU, memory, disk, files and network over a window. These are QUANTITIES AND NOT CHARGES: fline has no price and no billing during the private beta, nothing charges for what a project uses, and using more than the ceilings is not possible beca
attach_domainAttach a web address the person owns, such as www.example.com, to the project. Answers with the TXT record that proves ownership (challenge_name, challenge_token); list_domains also gives platform_name, the CNAME target that both proves ownership and sends visitors. The person ad
create_serviceCreate a data service for this workspace: engine=postgres for a PostgreSQL database, engine=valkey for a Valkey instance — the BSD-licensed fork of Redis, which every Redis client speaks unchanged, so ask for it wherever a project wants Redis — or engine=s3 for object storage, an
list_servicesThe workspace's services with their engine, version, state, hostname and size class. No credentials: none is returned by any tool.
delete_serviceDelete a service. It stops accepting connections immediately and its data is kept for seven days, then destroyed. Ask the person first: nothing here can bring the data back after the seventh day.
get_configThe fline.json for this project's current plan. Save it at the root of the archive you upload and the next deploy builds from it directly, with no analysis: the same plan every time. A short content check and the step that writes the build files still run. Edit it when the projec
check_configCheck a fline.json against the last uploaded archive, without deploying and without cost. Answers either ok, or the reason each part was refused — edit and ask again until it is ok, then save the file. There is no port field and there is no need for one: the platform passes PORT
refresh_configRe-run the analysis ignoring the archive's fline.json, and write a new one. For a configuration that has gone stale because the project's stack changed — a different package manager, a new lockfile. Accepted immediately, not done: poll get_project until it leaves analyzing, then
list_domainsThe project's custom domains with, for each, the state of its ownership check, the TXT record to publish, when it was last checked and what the last check objected to. Also the platform hostname the names are asked to point at. attach_domain hands back the record once; this is ho
check_domainRun the ownership check for one of the project's domains now, and answer with the result. Call it after the DNS record is published. The check reaches the DNS and is rate-limited behind a certificate budget, so poll it in minutes rather than in seconds. A domain still unproven 48
delete_domainDetach a domain from the project. The name stops being served; the project keeps its platform hostname.
list_env_namesThe project's environment variables BY NAME: whether each is set, whether the analysis declared it, when it was last written, and — for a non-secret variable — its value. A name that is required and not set is what holds a project in awaiting_secrets. A value shown here was writt
delete_env_nameRemove a variable from the project's secret set. The analysis's record that the project needs this name is kept, so a required variable becomes unset rather than unknown — deleting a value the project needs will hold the next deploy at the secrets gate rather than failing the bui
set_envSet one environment variable for the project. `secret` says which store it goes to and it is REQUIRED, because the two are not interchangeable and there is no default that is right for both. secret=false writes a PLAINTEXT value: it is stored as written, returned by list_env_name
get_project_detailEverything get_project returns, plus what the platform observes: each container's state, health, restart count and image digest, the node and tier, the ingress hostnames, the disk quota, the secret set version the running containers were deployed with, and the last failure with i
get_eventsThe project's state timeline, oldest first: each move from one state to the next, the reason, which part of the platform made it (gateway, worker, pipeline, cp) and the request id. This is how you tell a slow analysis from one that failed and was retried — get_project shows the c
get_serviceOne data service by id, with its state and — when it is not active — the reason. Poll this after create_service: a new service is `provisioning` until its certificate is issued and verified, and if that stalls the reason here is what says so. No credentials: none is returned by a
pause_servicePause a data service. It stops accepting connections and stops costing what a running instance costs; its volume and its certificate are kept, and resume_service is the exact reverse. This is the reversible way to put a service down — delete_service is not, and starts a seven-day
resume_serviceStart a paused data service again, with its data and its hostname unchanged.
stopStop the project. NOT IMPLEMENTED: the platform has no stop, and this refuses. To take an application out of service, delete_project it. delete_domain takes off only a web address the person owns; the project's fline address keeps answering.
restartRe-apply the project's current version: the same images, deployed again. This is the restart, and it is also the ONLY way a secret that was entered after the last deploy reaches the running containers — a value sits in the store doing nothing until a deploy re-pins the secret set
list_versionsList the project's deployed versions, newest first: the state_version to pass to rollback, when it was made, who made it, and which version it superseded. The specification itself is not included — use get_config for what a version contains.
rollbackRedeploy an earlier version of the project, named by its state_version from list_versions. Two things surprise people and you must not report either one wrongly. First, the version number does NOT go back: this creates a NEW version holding the old one's contents, numbered higher
attach_externalDeclare a backing service the tenant ALREADY RUNS, so the platform does not provision one. This takes the shape only. offering is one of postgres, redis, mysql, mongodb, rabbitmq; alias defaults to "db" and is what separates two of the same kind in one project; variable defaults
detach_externalGive an alias back to the platform. If a human already filled the value in, the attachment and the variable both go; if it is still waiting for one, the declaration goes with it and the project stops asking. The tenant's own service is untouched — the platform never ran it and ho
list_externalThe backing services this project's tenant supplies themselves. A completed attachment carries the host it points at; a pending one is marked pending and names the variable a human still has to fill in through get_secrets_link. No connection URL is returned for either, and none c
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 20. Nov. 2026
Der Registry-Name wurde über die Domain fline.sh bestätigt (die Registry prüft, wem die Domain gehört)
Code zuletzt geändert: vor 31 Tagen
Nicht relevant: Cloud-Server des Inhabers von fline.sh; du führst keinen Code aus dem Repo aus
Antwort in 761 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 40 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/servers/sh-fline-fline)Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Noch keine Bewertungen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 4 von 4 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt vor 31 Tagen geändert, und die neueste Version (0.1.1) kam vor 32 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT im Web (volles MCP ab Business; Pro nur lesend).
In derselben Kategorie: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Dieser fline | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Läuft wo | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | Läuft in der Cloud, keine Installation | In der Cloud oder auf deinem Rechner |
| Braucht Schlüssel | Nein | Nein | Nein | Nein | Nein | Nein |
| Mit + in Claude hinzufügen | Nein | Nein | Nein | Ja | Nein | Nein |
| Basisprüfungen | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Lizenz | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Preis | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register | Keine Kosten im Register |
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Skills that teach your AI coding app (Claude Code, Codex, Cursor and the other apps that read Agent Skills) how to put your project online with fline. For Claude Code, the repository is also a plugin that connects fline's MCP server.
| App | How |
|---|---|
| Claude Code, including the Claude desktop app's Code tab | /plugin marketplace add smartline-ai/fline-skills, then /plugin install fline@fline |
| Codex, Cursor, Gemini CLI, VS Code and others | npx skills add smartline-ai/fline-skills |
| By hand | Copy skills/* into ~/.claude/skills/ (Claude Code) or ~/.agents/skills/ (Codex and others) |
The Claude Code plugin brings fline's MCP server with it: type /mcp, choose fline, then Authenticate, and approve fline in your browser. Installed any other way, the skills carry no server; connect fline as the fline docs describe, or ask your AI app to, which loads fline-connect.
You need a fline account. fline is in private beta: see Getting your account.
The skills are instructions; on their own they send nothing anywhere. What leaves the computer goes through fline's MCP server at https://mcp.fline.sh/mcp, and only when the person asks for something fline does:
scripts/pack.sh packs a copy of it as a .tar.gz, leaving out .git, node_modules, what the project's .gitignore ignores, and .env and key files, and the agent uploads it to fline's storage. fline keeps that copy so it can build and run the app. The original stays in the folder.set_env sends that value to fline, which stores it and never shows it again.Sign-in is OAuth in the browser; the plugin holds no key. Disconnecting in the fline dashboard takes effect within 30 seconds. Details: privacy policy, terms, what fline does today.
| Skill | What it covers |
|---|---|
fline-connect | Adding fline's MCP server to the AI app, the browser approval, and the account states that refuse every call |
fline-prepare | Reading a project for what stops it running on fline, and fixing it before the first upload, including a cheap health route fline can check |
fline-launch | First launch, updates, settings, restarts and putting an earlier version back; bundles scripts/pack.sh |
fline-database | A Postgres or Valkey that fline creates and runs, a database the person already runs, SQLite and files on disk |
fline-domain | A web address the person owns: the record, the checks, the 48-hour limit |
fline-diagnose | What to read, in order, when a launch fails or a live app misbehaves, and the usual causes |
fline-build-plan | fline.json: freezing the plan, editing it, check_config, several services, prebuilt images, volumes, the health path |
fline-share-check | What to check in the app before the person sends its public link to anyone |
They fall into three groups: using fline (connect, launch, database, domain, diagnose), preparing a project for it (prepare, build-plan), and making it safe to share (share-check).
fline's server ships seven prompts with these procedures. In Claude Code an MCP prompt is a slash command the person types; the model has no tool to fetch one, so the server's instructions point at procedures the agent cannot open. A skill is loaded by the model itself when its description matches the task.
Skills name fline's tools without a prefix (create_project, not mcp__fline__create_project): the prefix differs between a plugin-provided server and one the person added.
.claude-plugin/plugin.json the plugin, including fline's MCP server
.claude-plugin/marketplace.json a marketplace holding that one plugin skills/ /SKILL.md one directory per skill (Agent Skills format) skills/fline-launch/scripts/ pack.sh, run by the agent, never read tests/ scenarios and the projects they run on
claude plugin validate --strict . checks the manifests.bash skills/fline-launch/scripts/pack.sh runs on the bash 3.2 and bsdtar that macOS ships, and on GNU tar.tests/scenarios.md holds six scenarios with what a passing answer does, run by a fresh agent with and without the skills. tests/make-fixtures.sh writes the two seeded projects they run on: a Node shop and a Flask tracker.Every fact here restates fline's own documentation, in particular for-ai.md. This repository is published from fline's main repository; a change made only here is replaced by the next publish.