The MCP User Profile Management Server enables interactive creation and management of user profiles with built-in elicitation capabilities for missing data.
Create User Profiles: Use the create_user_profile function to create new profiles, with interactive prompts to collect missing information such as name, email, age, and role
List User Profiles: Use the list_users function to retrieve all stored user profiles
Validation and Elicitation: Enforces validation rules (name length, email format, age range, role selection) and interactively prompts for missing or invalid data
VS Code Integration: Pre-configured for seamless VS Code MCP integration and debugging
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP User Profile Management Server create a user profile for me"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A demonstration Model Context Protocol (MCP) server showcasing elicitation capabilities.
https://github.com/user-attachments/assets/ce89872b-a015-48a6-b56f-6be6fee44ff0
Related MCP server: MCP Elicitations Demo Server
Ask response from user:
Collect info using command palette:
Success:
This project implements an MCP server with interactive elicitation capabilities, allowing clients to create and manage user profiles. When information is missing, the server uses MCP's elicitation feature to prompt users for required data.
create_user_profileCreates a new user profile with interactive elicitation support for missing fields.
Parameters (all optional):
name (string): User's full name
email (string): User's email address
age (number): User's age
role (string): User's role
Validation Rules:
Name: 2-100 characters
Email: 5-100 characters, must follow email format
Age: Between 13-120 years
Role: Select from predefined options (developer, designer, manager, analyst, tester)
list_usersLists all user profiles currently stored in the system.
npm installDevelopment Mode (with file watching):
npm run devProduction Mode:
npm startDirect execution:
node index.jsThe project comes pre-configured for VS Code MCP integration. Configuration file is located at .vscode/mcp.json:
{
"servers": {
"elicitationDemo": {
"type": "stdio",
"command": "node",
"args": ["index.js"],
"cwd": "${workspaceFolder}",
"dev": {
"watch": "*.js",
"debug": { "type": "node" }
}
}
}
}create_user_profile({
name: "John Doe",
email: "john@example.com",
age: 28,
role: "developer"
})// Provide partial information, system will prompt for missing data
create_user_profile({
name: "Jane Smith"
// Missing email, age, role - will trigger interactive elicitation
})list_users()Create a new job posting with elicitation support for missing fields
Inputs: no named parameters.
Create a new user profile with elicitation support for missing fields
Inputs: no named parameters.
List all job postings currently stored in the system
Inputs: no named parameters.
List all user profiles currently stored in the system
Inputs: no named parameters.
Search through user profiles using a simple text query
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools are cleanly divided between user profile operations (create_user_profile, list_users, search_users) and job posting operations (create_job_details, list_jobs), with no overlap in functionality.
All tools follow a consistent verb_noun naming pattern throughout. The verbs (create, list, search) are consistently applied to their respective nouns (user_profile, users, job_details, jobs), creating a predictable and readable naming convention.
Five tools is reasonable for a user profile management server, though it feels slightly thin. The server covers basic CRUD operations for two resource types (users and jobs), but lacks update and delete operations which would be expected in a complete management system.
There are notable gaps in the tool surface for a management server. While create and list operations exist for both users and jobs, there are no update or delete tools. Additionally, search exists only for users, not for jobs, creating an asymmetry in functionality.
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
Trusgent MCP — Trust Layer for AI agents. HK registry + Agent Cards. Default: get_merged_profile.
One profile — skills, credentials, and memory — synced to every agent tool via one MCP URL.
MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration
