ask_assistant
Ask a question to a specific assistant
LABSCO SUMMARY
The workflow states its own inputs, so a call is composed from the workflow rather than from a guess at its shape.
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.
What it is
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.
What you get
- 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.
Requirements
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.
Setup effort
One command plus credentials — npx -y @folderr/folderr-mcp-server, then supply credentials
USE CASES
01
Connecting the session to a Folderr account
Authentication happens through the tools rather than the configuration file, so either a token or an email and password gets the session working without a restart.
02
Putting a question to the assistant that knows the domain
The available assistants are listed first because the question has to name one by id, so the routing decision is made against what the account actually has.
03
Running a workflow somebody else built
The workflow reports its own required inputs before it is executed, so the call is assembled from the workflow's own contract rather than from a guess at what it wants.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
execute_workflow
Execute a workflow with the required inputs
get_workflow_inputs
Get the required inputs for a workflow
list_assistants
List all available assistants
list_workflows
List all available workflows
login
Login to Folderr with email and password
set_api_token
Set an API token for authentication (alternative to login)
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. list_workflows, get_workflow_inputs and execute_workflow are undocumented. Call login first; the other tools return nothing until you authenticate.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"folderr-mcp-server": {
"command": "npx",
"args": [
"-y",
"@folderr/folderr-mcp-server"
]
}
}
}npx
TERMINAL
npx -y @folderr/folderr-mcp-server
