Developer Portfolio MCP Server
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 |
|---|---|
| get_developer_profileA | Get the developer's core profile: name, title, contact, summary, and availability. |
| list_projectsA | List all projects in the developer's portfolio. Args: status: Optional filter — 'Active', 'Completed', or None for all. |
| get_project_detailsB | Get detailed information about a specific project. Args: project_id: Project slug, e.g. 'developer-portfolio-mcp'. |
| search_skillsA | Search skills by keyword and optional category. Args: query: Skill name or keyword to search for (case-insensitive). category: Skill category to search in, or 'all' for every category. |
| get_contact_infoA | Get contact links and availability for scheduling interviews. |
| compare_stackB | Compare a job's required tech stack against the developer's skills. Args: required_stack: List of technologies from a job description, e.g. ['Python', 'React', 'Docker']. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| interview_prep | Generate an interview preparation brief for a specific role. Args: role: Target job title, e.g. 'Senior Python Engineer'. company: Company name for context. |
| recruiter_brief | Generate a recruiter-friendly candidate brief. Args: focus: 'technical', 'leadership', or 'full' overview. |
| project_pitch | Generate a pitch for a specific portfolio project. Args: project_id: Project slug, e.g. 'developer-portfolio-mcp'. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resume_resource | Full developer resume in Markdown format. |
| projects_resource | Complete list of portfolio projects as JSON. |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: profile, contact, projects (list and detail), skills search, and stack comparison. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With 6 tools, the server is well-scoped for a developer portfolio, covering all essential areas without unnecessary bloat.
The tool set covers profile, contact, projects, skills, and stack comparison. Missing a direct list_all_skills tool, but search_skills covers it with a broad query. Minor gap, but overall adequate for a read-only portfolio.