CV Resume Builder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPOS | Yes | Repository path(s). Single repo: 'default:/absolute/path/to/repo'. Multiple repos: 'CompanyA:/path1,CompanyB:/path2,Personal:/path3' | |
| JIRA_URL | No | Your Jira instance URL (e.g., https://your-company.atlassian.net) | |
| JIRA_USER | No | Your Jira user email | |
| JIRA_EMAIL | No | Your Jira account email | |
| AUTHOR_NAME | Yes | Your git username/author name (must match exactly with git config user.name) | |
| CREDLY_USER_ID | No | Your Credly username (found in your profile URL: https://www.credly.com/users/YOUR-USERNAME) | |
| JIRA_API_TOKEN | No | Your Jira API token (get from https://id.atlassian.com/manage-profile/security/api-tokens) | |
| LINKEDIN_PROFILE_URL | No | Your LinkedIn profile URL (e.g., https://www.linkedin.com/in/yourprofile) - Note: Not yet implemented | |
| MAX_BULLETS_PER_EXPERIENCE | No | Maximum number of bullet points per experience section in CV formatting |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_git_logB | Get latest git commits by author from default repo (excludes merge commits) |
| list_reposB | List all configured git repositories |
| get_git_log_by_repoC | Get git commits from a specific repository by name |
| get_git_log_all_reposC | Get git commits from all configured repositories, grouped by repo |
| get_commit_detailsB | Get detailed commit information including code changes (diff) to analyze impact. Use this to understand what was actually done in commits. |
| analyze_commits_impactC | Get commits with their code changes for impact analysis. Returns commit messages + diffs to help AI understand the actual work done. |
| read_cvB | Read current CV (LaTeX) |
| read_winsB | Read wins.md achievements file |
| get_jira_ticketsC | Get Jira tickets assigned to or created by user |
| get_credly_badgesC | Get Credly badges and certifications |
| get_linkedin_profileB | Get LinkedIn profile summary (headline, about, experience) |
| get_cv_guidelinesB | Get CV formatting guidelines and constraints |
| parse_cv_pdfC | Parse an existing CV PDF file to extract text content and structure |
| generate_enhanced_cvC | Generate an enhanced CV by combining existing CV content with data from all sources |
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
There is significant overlap between several tools, particularly the commit-related ones: analyze_commits_impact, get_commit_details, get_git_log, get_git_log_all_repos, and get_git_log_by_repo all deal with retrieving commit data, which could confuse an agent about which to use. However, descriptions provide some differentiation (e.g., impact analysis vs. general logs, single vs. all repos), and other tools like get_credly_badges and get_linkedin_profile have distinct purposes.
Tool names follow a consistent verb_noun pattern using snake_case throughout, such as generate_enhanced_cv and get_jira_tickets. There are no deviations in style, making them predictable and readable, though some verbs like 'analyze' and 'get' are used interchangeably for similar functions, which is a minor inconsistency.
With 14 tools, the count is reasonable for a CV/resume builder that integrates multiple data sources like Git, Jira, LinkedIn, and Credly. It's slightly on the higher side but well-scoped to cover various aspects of data retrieval and processing, without feeling overly bloated or insufficient for the domain.
The tool set covers key areas for CV building: data extraction from Git, Jira, LinkedIn, and Credly; CV parsing and reading; and CV generation. Minor gaps exist, such as no tools for updating or deleting CV content or managing configurations, but core workflows (data gathering to CV enhancement) are supported, allowing agents to work effectively.