reframed-mcp
reframed-mcp
MCP-Server für Reframed. Passen Sie einen Lebenslauf an eine Stelle von jedem MCP-kompatiblen Agenten-Harness aus an.
Ein Tool: reframed_tailor. Akzeptiert Ihren Lebenslauf (Dateipfad oder Rohtext) und eine Stellenbeschreibung. Gibt zwei stimmerhaltende Versionen und eine Herkunftszusammenfassung zurück.
API-Schlüssel erhalten
Melden Sie sich bei reframed.works an
Gehen Sie zu Einstellungen → API-Schlüssel → Schlüssel erstellen
Kopieren Sie Ihren Schlüssel (
rt_live_...)
Related MCP server: CompleteMCP
Installation
Claude Code
claude mcp add reframed -- npx -y reframed-mcp
export REFRAMED_API_KEY=rt_live_...Oder speichern Sie den Schlüssel dauerhaft:
mkdir -p ~/.config/reframed
echo "rt_live_..." > ~/.config/reframed/keyClaude Desktop
Bearbeiten Sie ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"reframed": {
"command": "npx",
"args": ["-y", "reframed-mcp"],
"env": {
"REFRAMED_API_KEY": "rt_live_..."
}
}
}
}Starten Sie Claude Desktop neu.
Cursor
In den Cursor-Einstellungen → Features → MCP:
{
"reframed": {
"command": "npx",
"args": ["-y", "reframed-mcp"],
"env": { "REFRAMED_API_KEY": "rt_live_..." }
}
}Continue.dev
In ~/.continue/config.json:
{
"mcpServers": [
{
"name": "reframed",
"command": "npx",
"args": ["-y", "reframed-mcp"],
"env": { "REFRAMED_API_KEY": "rt_live_..." }
}
]
}Verwendung
Sobald installiert, fragen Sie Ihren Assistenten:
Passe meinen Lebenslauf unter ~/resume.md an diese Stelle an: [Stellenbeschreibungstext einfügen]
Stiloptionen
| Was Sie erhalten |
| Leichte Bearbeitungen — Ihre Worte, ATS-optimiert |
| Stimmerhaltende Umschreibung — stärkere Rahmung |
| Beide Versionen + Herkunftszusammenfassung |
Limits
100 Aufrufe/Stunde pro API-Schlüssel
.pdf-Lebenslaufeingabe in V1 nicht unterstützt — konvertieren Sie zu.mdoder fügen Sie Rohtext einStellenbeschreibungseingabe: fügen Sie Rohtext ein (URL-Scraping kommt in V2)
Lizenz
Available Tools
1 toolreframed_tailorA
Tailor a resume to a specific job. Preserves your voice. Returns two versions and a provenance summary.
| Name | Required | Description | Default |
|---|---|---|---|
| resume | Yes | File path to a .md resume, or paste raw resume text. PDF not supported. | |
| jd | Yes | Raw job description text (paste from the posting). | |
| style | No | Which version to return. 'conservative' = light edits. 'reframed' = voice-preserving rewrite. 'both' = both (default). | both |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool returns two versions and a summary and preserves user voice, but does not detail other behaviors like how it handles errors, rate limits, or the exact nature of 'provenance summary'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise and front-loaded. Three sentences cover purpose, key feature, output, and one constraint. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given schema covers all parameters, and no output schema, the description is mostly complete. It could include more detail on the output format (e.g., plain text vs structured) but is sufficient for typical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds value beyond schema by explaining the overall purpose and output. It also notes PDF incompatibility, which is absent from the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Tailor' and resource 'resume', and specifies key aspects: preserves voice, returns two versions and a provenance summary. It distinctively describes the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description is clear about when to use the tool, though it doesn't explicitly exclude alternatives (but there are no sibling tools). It mentions 'PDF not supported' which is a useful constraint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
reframed_tailor
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion between tools.
With a single tool, naming is trivially consistent; the name uses a clear verb_noun pattern.
A single tool is at the low end of the typical range; while appropriate for a narrow purpose, it feels thin compared to most servers.
The tool covers its stated purpose of tailoring a resume but lacks additional supporting operations like job description retrieval or resume parsing.
Maintenance
Related MCP Connectors
Tailor a CV to a job posting: score the match, propose a reviewable rewrite, export PDF or Word.
Tailor a career resume and cover letter as real Word docx files from stored facts.
Build an ATS-friendly resume and check it against a job description, fully offline.
Analyze job listings against your resume, track applications, and generate cover letters.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceHelps job seekers tailor their resume and generate cover letters against a specific job posting, powered by Claude.-
- FlicenseAqualityDmaintenanceEnables tailoring resumes to job descriptions by scraping JDs, applying rules, and generating optimized DOCX resumes.11-
- AlicenseNot gradedqualityBmaintenanceEnables resume review against job descriptions through a three-stage pipeline: match scoring, experience rewriting, and ATS optimization. Supports text or document uploads.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables evidence-grounded resume tailoring by generating ATS-readable LaTeX/PDF resumes from a user-curated experience bank, with every bullet traceable to evidence and inferred wording flagged for user approval.MIT