Productivity · Remote MCP server
Fillo
Fillo MCP server - provision, scaffold, publish, and query forms from your coding agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jacobfunch/usefillo- Version
- 0.9.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- jacobfunch (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jacobfunch) · how
- Repository
- github.com/jacobfunch/usefillo
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://fillo.so/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @usefillo/mcp | 0.9.0 | stdio |
How to connect Fillo
Fillo is a remote MCP server: there is nothing to install. Its endpoint is https://fillo.so/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @usefillo/mcp version 0.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @usefillo/mcp@0.9.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"usefillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/mcp@0.9.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| FilechangerConvert documents between text formats (markdown, html, and more) via the FileChanger API. | Local · stdio |
| FilesystemSecure MCP server for sandboxed filesystem operations with document parsing support. | Local · stdio |
| FileToPDFConvert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FilingpulseHosted SEC EDGAR filings: Form 4 insider trades, 8-K events, S-1/IPO registrations. Read-only. | Remote · HTTPLive check: ✓ handshake |
| FilloutRead Fillout forms and submissions, export responses, and create submissions and webhooks. | Remote · HTTPLive check: ✓ handshake |
| FinalPeaceState document requirements for all 50 US states, an after-a-loss checklist, and a planning gap chec. | Remote · HTTPLive check: ✓ handshake |
| FinCraftlyAI employees that run your CRM, invoicing, email, documents, dashboards and agents. | Remote · HTTPLive check: sign-in required |
| Findable MCP ServerFind and summarize building documents, projects, tasks, SharePoint sync state, and red flag data. | Remote · HTTPLive check: sign-in required |