Fillo

claude mcp add fillo -- npx -y @usefillo/mcp

Any other MCP client: runnpx -y @usefillo/mcpover stdio. SetFILLO_APIto point at a non-production deployment.

The server reads the same credentials the CLI writes to~/.fillo/config.json, or from the environment:

- FILLO_TOKEN— afcli_…login token (fromnpx @usefillo/cli login). Authenticated tools (fillo_list_forms,fillo_publish_form, and trusted pushes to a claimed workspace), plus local project selection with an ordinary login. File-request pushes remain draft/staged for review.
- FILLO_PK— apk_…publishable key.fillo_provision_workspacemints one and saves it for you.
- FILLO_API_KEY— afsk_…project API key, minted inSettings → Connectionsof a claimed workspace. Required by the response tools.
- FILLO_API— overrides the origin (defaulthttps://fillo.so).
- FILLO_CONFIG_DIR— overrides the config directory (default~/.fillo).

The server never prints login tokens, API keys, or claim tokens into the transcript. Thepk_publishable key is safe to surface (it lives in browser code), sofillo_provision_workspacereturns it for you to wire into the app's public env. Provisioning also makes that temporary project the active local MCP context, so an older saved account login cannot receive the next push. Selecting a project switches the context back to the account.

There are no delete tools. Write annotations still use the conservative worst-case hint because a push can replace draft state and a publish can replace the public schema. Every tool is a thin wrapper over Fillo's public HTTP API — the server never touches the database and imports no app code, so workspace scoping, rate limits, and validation stay in one place.

The three project tools are local-only and require the general token minted byfillo login. A project-specific handoff and a hosted remote-MCP OAuth grant remain pinned to the project a human approved. Selecting locally also clears cached preview andfsk_state from the prior project; replace anyFILLO_PKorFILLO_API_KEYenvironment overrides yourself.

Projects are sites/apps beneath one billed workspace. They isolate forms, publishable/API keys, allowed origins, respondent identities, and agent authority. Workspace membership, billing, storage connections, and usage totals remain shared.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

A workflow management system for AI-assisted development with MCP support, featuring flexible storage via file system or PostgreSQL.

Provides tools for scientific computation, including tensor storage, linear algebra, vector calculus, and visualization.

Accesses optimized documentation from the TrueNAS middleware repository to understand its codebase and APIs.

MCP Server for PGYER platform, supports uploading, querying apps, etc.

A .NET MCP server for interacting with the Autodesk AEC Data Model API and Viewer.

A command-line tool to run MCP servers from a single file, with support for automatic dependency resolution, environment setup, and package installation from local or S3 sources.

MCP server that moves files between your filesystem and cloud storage.

Interact with the Intelligent Content Management platform through Box AI.

Official Model Context Protocol (MCP) server for esa.io - STDIO transport version.