Faldaro

com.faldaroPublished by faldaro.comv0.1.1Updated Oct 24, 2026

Forms, submissions, workflows and reports in Faldaro, exactly as privileged as your API key.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Faldaro's MCP server lets an assistant work with forms, submissions, workflows and reports in a Faldaro account, with the same privileges as the API key used.

What you can do
Connect an assistant to a Faldaro account to work with forms, submissions, workflows and reports. The server exposes no tool list in the manifest, so the exact operations are not documented here. Access is scoped to the privileges of the supplied API key. It can be reached as a hosted remote endpoint or run locally over stdio.
When to use it
Use it when you already use Faldaro for forms, submissions, workflows or reports and want an assistant to work with that data directly instead of copying it between tools.
Requirements
A Faldaro account and an ffk_ API key created on the Settings → API keys page, supplied as the FALDARO_API_KEY environment variable or as an Authorization bearer header. The hosted endpoint is at faldaro.app; for a self-hosted deployment, set FALDARO_URL. The local option is the npm package @faldaro/mcp over stdio, which needs Node.js.
Before you install
The API key grants the same privileges the key itself holds, so scope it narrowly and treat it as a secret. The server can act on forms, submissions, workflows and reports, which may include writing or changing data; confirm before destructive actions. A self-hosted FALDARO_URL sends requests to that host rather than to Faldaro.

Installation

In SourceWeft

  1. Open Faldaro in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.faldaro%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "faldaro": {
      "type": "http",
      "url": "https://faldaro.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.