Productivity · Remote MCP server
Faldaro
Forms, submissions, workflows and reports in Faldaro, exactly as privileged as your API key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.faldaro/mcp- Version
- 0.1.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- com.faldaro
- Namespace
- Namespace verified by the MCP Registry via the domain faldaro.com · how
- Website
- faldaro.com/docs/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://faldaro.app/api/mcp | Authorization (required, secret) |
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; a Bearer token is asked for
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @faldaro/mcp | 0.1.1 | stdio |
How to connect Faldaro
Faldaro is a remote MCP server: there is nothing to install. Its endpoint is https://faldaro.app/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @faldaro/mcp version 0.1.1. 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 @faldaro/mcp@0.1.1. It reads these environment variables: FALDARO_API_KEY (required, secret) and FALDARO_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@faldaro/mcp@0.1.1"
],
"env": {
"FALDARO_API_KEY": "<secret>",
"FALDARO_URL": "<value>"
}
}
}
}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 |
|---|---|
| EzpzfileLocal file tools for agents: documents, PDFs, images, QR codes. Nothing is uploaded. | Local · stdio |
| Factura LuzLee y explica facturas de la luz españolas (QR de la CNMC). Todo en local. | Local · stdio |
| FairsignFill and sign PDFs in the browser, send for signature, and track who has signed. | Remote · HTTPLive check: ✗ no handshake |
| Faivelo EmailBusiness email on your own domain: mailboxes, send and read mail, aliases, DNS setup, and campaigns. | Remote · HTTPLive check: sign-in required |
| falzmarkeGeschäftspost nach DIN 5008 aus Markdown - Brief und E-Mail, am fertigen Dokument nachgemessen. | Local · stdio |
| FamiliaPrivate family planner for schedules, tasks, checklists, attachments, and availability. | Remote · HTTPLive check: ✓ handshake |
| Fantasy Football Draft AssistantThe full 2026 fantasy draft board, free to any AI agent. No key, no email, no signup. | Remote · HTTPLive check: ✓ handshake |
| Fantasy Tabletop HelperRead-only access to your tabletop campaigns: codex, sessions, and session notes. | Remote · HTTPLive check: sign-in required |