kgromero-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KGROMERO_OFFLINE | No | Set to 1 to skip the network and use the bundled snapshot | |
| KGROMERO_SITE_URL | No | Point at another deployment, e.g. http://localhost:5173 | https://kgromero.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Answers questions about Kyle Romero, a software engineering leader, using the content published at kgromero.com. Start with get_profile for an overview. list_experience gives one entry per employer and get_experience the details of a role; get_career_timeline lists every title including promotions. get_skills, list_side_projects, list_documents (portfolio and resume downloads), get_interests, get_travel, and get_contact cover the rest. Use search to find anything by keyword. Only state facts these tools return; do not invent details.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Overview of Kyle Romero: title, summary, location, current role, and total experience. |
| get_contactB | Contact details and online profiles (LinkedIn, GitHub, Keyoxide), plus a vCard link. |
| list_experienceA | Career timeline, most recent first. Each entry has an id for use with get_experience. |
| get_experienceA | Full details for one or more roles: highlights, accomplishments, and tech stack. Args: company_or_id: An id from list_experience (e.g. "0"), or part of a company or position name (e.g. "Tenna", "HP", "Director"). Case-insensitive. |
| get_educationC | Degrees and schools. |
| get_career_timelineA | Every title Kyle has held, most recent first, including promotions within a company (e.g. Manager → Senior Manager → Director at MEARS) and education. |
| get_skillsB | Kyle's skills two ways: by category (Cloud, DB, AI, Processes, ...) and as technologies used on the job, merged across roles with where and how recently. Args: filter: Optional case-insensitive substring to narrow results (e.g. "aws", "react", "agile"). Matches skill names, sub-components, and category names. |
| list_side_projectsB | Personal side projects with language, description, and GitHub link. |
| list_documentsA | Downloadable resume formats plus the portfolio: architecture diagrams, process docs, project write-ups, certificates, and college lab reports, grouped by employer/school. Args: group: Optional filter by group name, e.g. "Resume", "MEARS", "HP", "Texas Tech", "Other". Case-insensitive substring. |
| get_interestsB | Personal interests and hobbies, and the tech news sites Kyle reads. |
| get_travelB | Places Kyle has lived and traveled to (from the travel globe on kgromero.com). Args: lived_only: Only return places Kyle has lived. |
| searchA | Search everything on kgromero.com (resume, skills, projects, documents, timeline, interests, travel) for a keyword or phrase, e.g. "cost", "Kubernetes", "architecture". Every word in the query must appear for a result to match. Case-insensitive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| assess_job_fit | Compare Kyle Romero's resume against a job description. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resume-json | |
| resume-markdown | |
| site-content |
TDQS
Scored across 12 tools
Most tools target clearly distinct data: profile, contact, education, skills, projects, documents, interests, and travel are unambiguous. The one confusing pair is list_experience versus get_career_timeline, which both describe a 'career timeline, most recent first'; the descriptions help somewhat (one yields ids, the other shows title progression plus education), but an agent could reasonably hesitate between them.
The set follows a clear get_*/list_* verb_noun convention throughout (get_profile, get_contact, list_experience, list_documents, get_travel, get_skills). The lone deviation is the bare 'search' tool, which lacks the noun form of the others, but this is a minor and intuitive exception.
Twelve tools is well within the appropriate 3-15 range and each maps to a natural content section of a portfolio site. get_career_timeline is arguably redundant with list_experience plus get_experience, making the count slightly heavier than strictly necessary.
For a read-only personal portfolio domain, the surface covers profile, contact, experience, education, timeline, skills, projects, documents, interests, travel, and full-text search — essentially every content area a consumer would need. There are no meaningful gaps for this read-only scope.