usuarios
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_projectA | Initialize a new usuarios project. Creates the .usuarios/ directory structure: .usuarios/ config.yaml research/ <- Put interview files here patterns/ <- Analysis results go here profiles/ <- Generated profiles (JSON + MD) validations/ <- Validation reports Args: project_path: Absolute path to the project directory. |
| list_researchA | List all research files in the project. Args: project_path: Absolute path to the project directory. |
| get_research_promptA | Generate an analysis prompt from research data. Reads all research files (or specified subset) and returns a prompt that you (the AI host) should process with your LLM to extract:
After processing, call save_patterns with the structured result. Args: project_path: Absolute path to the project directory. source_files: Optional list of specific file names to analyze. |
| save_patternsA | Save extracted research patterns to the project. Accepts the patterns as a JSON string. The patterns should follow the structure provided by the get_research_prompt output. Args: project_path: Absolute path to the project directory. patterns: JSON string with the analysis results. |
| get_generate_promptB | Generate a prompt for creating synthetic user profiles. Reads the patterns file and returns a prompt with the complete 12-dimension profile schema for you to generate rich synthetic user profiles. Args: project_path: Absolute path to the project directory. count: Optional number of profiles to generate (default: auto-detect from patterns). |
| save_profileA | Save a generated synthetic user profile. Saves both a JSON file (for machine consumption) and a Markdown file (for human consumption). The profile must follow the 12-dimension schema provided by get_generate_prompt. Args: project_path: Absolute path to the project directory. profile: JSON string with the 12-dimension profile. |
| list_profilesA | List all synthetic user profiles in the project. Args: project_path: Absolute path to the project directory. |
| get_profileA | Get a specific profile by ID. Args: project_path: Absolute path to the project directory. profile_id: The profile identifier (e.g. "maria-cuidadora"). format: Output format: "json" (structured) or "markdown" (human-readable). |
| get_validate_promptA | Generate a validation prompt for testing a design against a profile. Reads the specified profile and design document, then returns a prompt for you to evaluate the design against the user's criteria and needs. Args: project_path: Absolute path to the project directory. profile_id: The profile to validate against (e.g. "maria-cuidadora"). design_file: Path to the design document to validate (relative to project). |
| save_validationB | Save a validation report. Args: project_path: Absolute path to the project directory. profile_id: The profile that was validated against. report: JSON string with the validation report. |
| list_validationsB | List all validation reports in the project. Args: project_path: Absolute path to the project directory. |
| get_project_configC | Get the current project configuration. Args: project_path: Absolute path to the project directory. |
| quick_statusA | Get a dashboard overview of the entire project. Shows research files count, patterns status, profiles created, validations run, and project health. Call this FIRST in any workflow to understand the current state. Args: project_path: Absolute path to the project directory. |
| get_workflow_guideA | Get the complete workflow guide for using usuarios-mcp. Returns detailed instructions on how to use the server effectively: autonomous workflows, methodology, and UX principles. Call this when you need a refresher on the correct workflow. |
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 14 tools
Each tool has a clear, distinct purpose. Tools like get_generate_prompt, get_research_prompt, and get_validate_prompt serve different stages of the workflow, while list_ and save_ tools operate on different resources. There is no overlap or confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_profile, save_patterns, list_research). The verbs (get, init, list, save, quick) are appropriate for the action, and the naming makes the tool's purpose immediately clear.
With 14 tools, the server is well-scoped for its domain of user research and synthetic profile generation. Each tool contributes to a specific step in the workflow without redundancy or unnecessary bloat.
The tool set covers the full research-to-validation workflow: initialization, research analysis, pattern extraction, profile generation, and validation. Missing are update/delete operations for resources, but the forward-only generation process mostly mitigates this need.