get_workflow_inputs sitting between listing and executing is the difference between an agent that can run any workflow in the account and one that can only run the workflow it was written against. Authentication is itself a tool rather than configuration, so the credential arrives in-session. Everything here consumes what Folderr already holds: assistants and workflows can be listed, asked and executed, and none of them can be created or edited from here.
A Folderr client of 7 tools: authentication by token or by login, an assistant question path, and a workflow path that reports its own required inputs before execution.
- Authentication as a tool rather than a config file — set_api_token for a token, or login with an email and password.
- list_assistants, and ask_assistant, which puts a question to a named assistant_id.
- list_workflows, get_workflow_inputs, which returns the inputs a specific workflow requires, and execute_workflow, which runs it with those inputs supplied.
A Folderr account, reached either with an API token through set_api_token or with the email and password login takes. Assistants and workflows already defined in that account, since nothing here creates one.
One command plus a key — npx -y @folderr/folderr-mcp-server, then supply credentials