factql-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACTQL_API_KEY | Yes | Your FactQL API key (an ask-only key is enough) | |
| FACTQL_BASE_URL | No | FactQL API base URL | https://api.factql.ai |
| FACTQL_END_USER_ID | No | End user identifier | mcp:<os user> |
| FACTQL_WORKSPACE_ID | No | Workspace ID; defaults to the default workspace for tenants that use workspaces |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Ask plain-English questions about the connected business data. Call whoami first when the tenant may use workspaces, then pass the workspace_id to ask. Each ask is stateless: restate the subject in follow-up questions.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | What this API key can see: tenant, plan, and the workspaces it may query. Use it to find a |
| askA | Ask a plain-English question about the connected data. Returns the answer, the SQL that was run (when any), and up to 50 rows.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: `whoami` retrieves tenant/plan/workspace context, while `ask` runs a natural-language query. The description of `ask` even points to `whoami` for discovering workspace_id, reinforcing the division of labor.
Both names are single lowercase words in a consistent informal, command-style convention (whoami, ask), with no mixing of snake_case/camelCase. There is no verb_noun pattern, but across only two tools the style is predictable and readable.
Two tools is on the thin side, though the server's narrow purpose (context discovery + one NL query entry point) means each tool does earn its place. It sits at the borderline rather than being over- or under-scoped badly.
The surface covers identity and querying but has no schema/table introspection helper and no pagination or continuation mechanism beyond the fixed 50-row cap. Agents can often work around these limits via `whoami` and re-asking, but they are notable gaps for a data-query server.