career

Tailor a career resume and cover letter as real Word docx files from stored facts.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
77%
Calidad de los nombres
86%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~3,073Tokens (definiciones de herramientas)
~1.9 KBTamaño de respuesta típico
Impacto significativo en la atención (2.40% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "career": {
      "command": "uvx",
      "args": [
        "https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/resume.mcpb"
      ]
    }
  }
}

Paquetes ejecutables

mcpbhttps://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/resume.mcpb0.21.0stdio
mcpbhttps://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/resume.mcpb0.22.0stdio

Puntos de conexión remotos

https://mcp.zovo.one/mcp/careerstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (13)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟡profile_set(name, email, phone, location, links, ...)

Store the profile every resume and cover letter is built from: contact details, summary, skills, roles with bullets, education, certifications and languages. Returns a count of what was stored.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Your own name. Leave it out and the shared business profile's name is used, so you are never asked for a name the suite already holds"
    },
    "email": {
      "type": "string",
      "description": "Your own email address. Leave it out and the shared business profile's email is used; with neither, letters and letterheads show \"[add: email]\" and say so. Never invent one"
    },
    "phone": {
      "type": "string",
      "description": "Your own phone number. Defaults to the shared business profile's phone"
    },
    "location": {
      "type": "string"
    },
    "links": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Portfolio, LinkedIn, GitHub"
    },
    "summary": {
      "type": "string",
      "description": "Two or three lines. Used verbatim as the fit paragraph of a cover letter."
    },
    "skills": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "experience": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "company": {
            "type": "string",
            "minLength": 1
          },
          "title": {
            "type": "string",
            "minLength": 1
          },
          "start": {
            "type": "string",
            "minLength": 1,
            "description": "As you want it printed: \"2021\" or \"Jan 2021\""
          },
          "end": {
            "type": "string",
            "description": "Leave out for a current role; it prints as \"present\""
          },
          "bullets": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "What you did, one line each. Facts only: everything else in this server refuses to state anything that is not here."
          }
        },
        "required": [
          "company",
          "title",
          "start",
          "bullets"
        ],
        "additionalProperties": false
      },
      "default": [],
      "description": "Roles in any order you like -- profile_set sorts and stores them newest-first (an open role with no `end` first, then by `end` descending, then by `start` descending) before saving, since page-budget trimming and cover-letter bullet ranking both trust array order to mean recency."
    },
    "education": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "school": {
            "type": "string",
            "minLength": 1
          },
          "degree": {
            "type": "string",
            "minLength": 1
          },
          "start": {
            "type": "string"
          },
          "end": {
            "type": "string"
          }
        },
        "required": [
          "school",
          "degree"
        ],
        "additionalProperties": false
      },
      "default": []
    },
    "certifications": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "languages": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "accent_color": {
      "type": "string",
      "description": "Letterhead colour, six hex digits, e.g. 1F3864. Pro only."
    },
    "variant": {
      "type": "string",
      "description": "Name a second profile, e.g. \"backend\". One profile per data directory on the free tier; named variants are Pro only."
    },
    "merge": {
      "type": "boolean",
      "description": "Update the stored profile: fields you pass replace their stored value, fields you leave out are kept. Required when a profile already exists, unless you pass replace"
    },
    "replace": {
      "type": "boolean",
      "description": "Discard the stored profile and store exactly what this call carries. Required when a profile already exists, unless you pass merge"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢profile_get(variant)

Return the stored CV profile exactly as resume_create, cover_letter_create and tailor_to_job will use it, plus the variant read and every stored variant name. Call it before any rewrite.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "variant": {
      "type": "string"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡resume_create(variant, style, target_role, keywords, max_pages, ...)

Call this tool to write the stored profile to a Word .docx. Returns the output path, the estimated page count, which bullets were dropped to fit, and which keywords matched or are missing.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "variant": {
      "type": "string"
    },
    "style": {
      "type": "string",
      "enum": [
        "modern",
        "classic",
        "compact"
      ],
      "default": "modern",
      "description": "Free tier prints \"modern\" only; \"classic\" and \"compact\" are Pro."
    },
    "target_role": {
      "type": "string",
      "description": "Printed under your name and used to rank bullets"
    },
    "keywords": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "From the posting. A keyword that appears anywhere in the profile is printed in bold; one that does not is reported as missing and is never added to the resume."
    },
    "max_pages": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 2,
      "description": "Bullets are ordered by relevance to target_role and keywords, then trimmed to fit this many pages against a measured word budget. Default 2."
    },
    "out_path": {
      "type": "string",
      "description": "Where to write the .docx. Defaults to <data dir>/documents/<name>-resume.docx, numbered -2, -3, ... if that exists."
    },
    "overwrite": {
      "type": "boolean",
      "default": false,
      "description": "Replace an existing file at out_path. Default false: the call fails and nothing is written."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡resume_to_markdown(variant, target_role, max_pages)

Return the stored profile as markdown text inline, ready to paste into a form or an ATS box. Same page-budget trimming as resume_create for max_pages. Nothing is written to disk. Free.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "variant": {
      "type": "string"
    },
    "target_role": {
      "type": "string"
    },
    "max_pages": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 2
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡resume_to_html(variant, target_role, max_pages, out_path, overwrite)

Call this tool to write the resume as semantic HTML with a print stylesheet and return where it went; print it to PDF from a browser, because there is no doc_to_pdf here. Bullets are trimmed to fit max_pages. Free.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "variant": {
      "type": "string"
    },
    "target_role": {
      "type": "string"
    },
    "max_pages": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 2,
      "description": "Bullets are trimmed to fit this many pages against a measured word budget. Default 2."
    },
    "out_path": {
      "type": "string",
      "description": "Where to write the .html. Defaults to <data dir>/documents/<name>-resume.html, numbered -2, -3, ... if that exists."
    },
    "overwrite": {
      "type": "boolean",
      "default": false,
      "description": "Replace an existing file at out_path. Default false: the call fails and nothing is written."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢resume_read(path, docx_base64, save, variant)

Call this tool to read an existing .docx resume into the profile shape, with the sections found and anything unplaced. It saves nothing unless save is true, so review it first. .doc and .rtf are refused.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "minLength": 1,
      "description": "Name of a document uploaded with doc_upload"
    },
    "docx_base64": {
      "type": "string",
      "description": "The .docx itself, base64-encoded, instead of uploading it first"
    },
    "save": {
      "type": "boolean",
      "default": false,
      "description": "Store the result as the profile. Review it first."
    },
    "variant": {
      "type": "string"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡cover_letter_create(company, role, hiring_manager, job_description, tone, ...)

Call this tool to write a one-page cover letter .docx from the stored profile and return the path, word count and bracketed prompts. Nothing from the posting is restated as yours. Free: 3 a month.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "company": {
      "type": "string",
      "minLength": 1
    },
    "role": {
      "type": "string",
      "minLength": 1
    },
    "hiring_manager": {
      "type": "string"
    },
    "job_description": {
      "type": "string",
      "description": "Paste the posting. Used only to pick which of your own skills to lead with; no figure from the posting is ever restated as yours."
    },
    "tone": {
      "type": "string",
      "enum": [
        "formal",
        "direct",
        "warm"
      ],
      "default": "formal",
      "description": "Default \"formal\"."
    },
    "highlights": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Points to lead with. Each is checked against the profile; anything not found there is returned as a bracketed prompt, not printed as fact."
    },
    "out_path": {
      "type": "string",
      "description": "Where to write the .docx. Defaults to <data dir>/documents/<company>-<role>-cover-letter.docx, numbered -2, -3, ... if that exists."
    },
    "overwrite": {
      "type": "boolean",
      "default": false,
      "description": "Replace an existing file at out_path. Default false: the call fails and nothing is written."
    }
  },
  "required": [
    "company",
    "role"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢tailor_to_job(job_description, variant, limit)

READ-ONLY gap analysis against a posting: writes nothing, changes nothing. Returns matched keywords, missing ones, a coverage figure and orderings of facts you already stated. Act on it with resume_create.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "job_description": {
      "type": "string",
      "minLength": 1,
      "description": "Paste the posting. The free tier reads up to 2,000 characters; Pro reads any length."
    },
    "variant": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "minimum": 5,
      "maximum": 60,
      "default": 30,
      "description": "How many keywords to extract from the posting. Default 30."
    }
  },
  "required": [
    "job_description"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪license_activate(key)

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴doc_upload(name, docx_base64, url)

Send an existing Word document to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with doc_upload and then pass its name as `path` to doc_read, doc_to_html and doc_fill_template. Give exactly one of docx_base64 or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): a 13 KB base64 paste can take minutes to write out, while a url costs one line and the fetch happens here (10 second timeout, at most 3 redirects, public http(s) hosts only, 2 MB cap). Uploads are kept for your token between calls; doc_read and doc_fill_template also take docx_base64 directly; that file is stored under the name you give (default 'inline' / 'template') and can be removed with doc_delete_upload. Documents this server writes come back as a download link valid for one hour.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 70,
      "description": "Name to refer to this document by: 1-64 characters of letters, digits, underscore or dash, e.g. \"contract\""
    },
    "docx_base64": {
      "type": "string",
      "description": "The .docx file, base64-encoded"
    },
    "url": {
      "type": "string",
      "description": "url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢doc_files

List the documents uploaded for your token, with their sizes.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴doc_delete_upload(name)

Delete one document uploaded for your token: name is the name it was uploaded under, without .docx. doc_files lists them. A name nothing is stored under is refused and nothing is deleted.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 70
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada13 herramientas
verificadoversión no registrada13 herramientas