portfolio-mcp-server
Related Servers
Alternatives to portfolio-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes a personal portfolio of projects, skills, and resume as callable tools for MCP-compatible AI assistants like Claude Desktop.4MIT
- FlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to retrieve a professional profile as callable tools, including projects, work experience, skills, and live GitHub activity.5-
- AlicenseNot gradedqualityDmaintenanceExposes core recruiting tools such as candidate ranking, profile retrieval, honeypot audits, and job description parsing via stdio protocol.MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to NALLAR engineering evidence and portfolio artifacts over MCP, exposing tools, resources, and prompts via stdio JSON-RPC.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to retrieve a personal biography, skills, projects, and contact links through a read-only MCP server.-
- FlicenseAqualityCmaintenanceExposes a personal portfolio's resume, projects, skills, certifications, and live GitHub repositories as tools for AI assistants to query via natural language.6-
TDQS
Scored across 32 tools
Each tool targets a distinct resource and action, with clear list/get/create/update/delete separation. There is no meaningful overlap or ambiguity between any of the 32 tools.
Tool names follow a consistent verb_noun pattern throughout: list_ for collections, get_ for single items, and create_/update_/delete_ for mutations. This makes the API surface highly predictable.
With 32 tools, the server is over-scoped for a portfolio use case, exceeding the threshold where tool selection becomes a cognitive burden. While the CRUD pattern is systematic, most real portfolio workflows would only need a small subset of read operations.
The tool set provides complete CRUD coverage for every portfolio content type, plus profile management. There are no obvious dead ends or missing lifecycle operations.