# Fline MCP server

Source: https://glimind.com/server/mcp-registry%2Fsh.fline%2Ffline
Registry id: `mcp-registry/sh.fline/fline`
Status: live (checked 2026-11-22T17:25:18.320Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 682
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "fline-mcp-server": {
      "type": "http",
      "url": "https://mcp.fline.sh/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fline-mcp-server https://mcp.fline.sh/mcp
```

## Tools (42)

- `answer_questions`: Answer the questions raised during source analysis.
- `attach_domain`: Attach 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_toke
- `attach_external`: Declare 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,
- `check_config`: Check 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 
- `check_domain`: Run 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 a
- `complete_upload`: Report 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 c
- `create_project`: Create 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 upload
- `create_service`: Create 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
- `declare_env_names`: Declare 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.
- `delete_domain`: Detach a domain from the project. The name stops being served; the project keeps its platform hostname.
- `delete_env_name`: Remove 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 tha
- `delete_project`: Delete the project. The platform will stop and irreversibly clean up the project's runtime resources; once the request is accepted the project disappears from t
- `delete_service`: Delete 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 t
- `deploy`: Build 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
- `detach_external`: Give 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 declara
- `get_config`: The 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
- `get_deploy_status`: Deployment state: desired and observed arrive separately and mean different things separately. app_health, once the app has been online, says whether it answers
- `get_deployment_status`: Get the status of a deployment
- `get_events`: The 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)
- `get_images`: The 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 
- `get_logs`: Logs. 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 
- `get_project`: The project's full state: the onboarding stage, the runtime state, open questions, missing secrets and warnings about credentials found in the archive. Also app
- `get_project_detail`: Everything get_project returns, plus what the platform observes: each container's state, health, restart count and image digest, the node and tier, the ingress 
- `get_secrets_link`: Issue 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 
- `get_service`: One 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 certi
- `get_upload_url`: Issue 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 alread
- `get_usage`: What 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
- `list_domains`: The 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 objec
- `list_env_names`: The 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 — 
- `list_external`: The 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 
- `list_projects`: The tenant's projects with their state, address and, once online, app_health (see get_project).
- `list_services`: The workspace's services with their engine, version, state, hostname and size class. No credentials: none is returned by any tool.
- `list_versions`: List 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 s
- `pause_service`: Pause a data service. It stops accepting connections and stops costing what a running instance costs; its volume and its certificate are kept, and resume_servic
- `refresh_config`: Re-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 diff
- `restart`: Re-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 la
- `resume_service`: Start a paused data service again, with its data and its hostname unchanged.
- `rollback`: Redeploy 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
- `set_env`: Set 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 d
- `stop`: Stop 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
- `submit_declaration`: Supply the project description. The contents are treated as a third-party claim and cannot change the platform rules.
- `update_project`: Update an existing project on fline

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
