Profile Questions MCP Server
Related Servers
Alternatives to Profile Questions MCP Server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityFmaintenanceConnects AI agents to the Futurykon prediction platform, enabling them to query and interact with prediction questions, manage predictions, and view leaderboards.-- AlicenseNot gradedqualityCmaintenanceExposes the Filly Forms REST API as MCP tools for AI agents, enabling form type listing, record CRUD, data preview, and document upload with AI extraction.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and manage a document knowledge base via MCP, with RAG-powered search and grounded answers with citations.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the FormIO API for dynamic form creation, submission management, and user roles using natural language.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to fully automate Appwrite backend operations with 143 tools covering databases, users, storage, functions, messaging, and more. Supports advanced features like GeoJSON attributes, file uploads, function deployment, and bulk operations.3 npm-
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to generate fake user profiles and companies using the Random Profiles API with automatic API key handling.59 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource-action pair: get_my_answers (retrieve user answers), list_questions (discover questions), create_question (author questions), submit_answer (single answer), batch_submit_answers (bulk answers). The single vs. batch submit pair is clearly delineated, and questions vs. answers tools don't overlap.
All names follow a consistent snake_case verb_noun pattern: get_my_answers, list_questions, create_question, submit_answer, batch_submit_answers. The batch_ prefix is a predictable modifier rather than a convention break.
Five tools is well-scoped for a questionnaire/profile domain, with each tool earning its place across the read/create/answer lifecycle. Nothing feels redundant or missing at the count level.
Core lifecycle is covered: authoring questions, listing them, and submitting answers singly or in bulk. However, there is no update/delete for questions and no retrieval of a single question by id, which are minor gaps an agent can work around.