resumejson

Parse a resume or CV (PDF, DOCX, text, scan or photo) into typed JSON.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
90%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~192Tokens (tool definitions)
~1.1 KBTypical response size
Minimal attention impact (0.15% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "resumejson": {
      "url": "https://resumejson.tiraisoft.com/mcp"
    }
  }
}

Remote endpoints

https://resumejson.tiraisoft.com/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢parse_resume(file_base64, text, output_language)

Parse a resume or CV into typed JSON: name, contact details, every role with normalised dates, education, skills, certifications and languages. Give EITHER `file_base64` holding a PDF, DOCX, JPEG, PNG or WebP file encoded as base64 (scans and photos work), OR `text` holding the resume as plain text. A field the CV does not state comes back null.

Input Schema

{
  "type": "object",
  "properties": {
    "file_base64": {
      "type": "string",
      "description": "The resume file, base64-encoded."
    },
    "text": {
      "type": "string",
      "description": "The resume as plain text, when there is no file."
    },
    "output_language": {
      "type": "string",
      "description": "Optional. Write extracted text values in this language, e.g. \"French\" or \"pt-BR\". Omit to keep the CV's own language."
    }
  }
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools