Skip to main content
Glama
Sign In
kgromero-mcp

kgromero-mcp

by romero927
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to kgromero-mcp

No user-submitted related servers found.

    Related Servers

    • Interactive Curriculum MCP

      AnaCataVC
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and LLM clients to query a professional CV and portfolio, including work history, technical skills, projects, job compatibility evaluation, education, and contact details.
      MIT

    • Resume MCP Server

      Adarshcharjan
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes a structured professional resume as a set of AI-queryable tools, enabling AI clients like Claude Desktop to query summary, experience, skills, projects, and tailor resumes to job descriptions.
      1
      MIT

    • cv-mcp

      dabs1
      A
      license
      A
      quality
      C
      maintenance
      Exposes a curriculum vitae hosted on a backend REST API to AI assistants over stdio, letting them retrieve the full CV, list and fetch individual sections, and search for terms like technologies or companies. It also provides the full CV as attachable context and a prompt that compares the CV against a job description to suggest improvements.
      4
      MIT

    • mcp-perfil

      JeanSantos89
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query a professional profile in real time through tools for experiences, skills, projects, summary, recommendations, and GitHub repositories. It also serves a bilingual landing page and generated resume PDF from the same profile data.
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources