Skip to main content
Glama
notaprompt

reframed-mcp

by notaprompt

reframed-mcp

Tailor a resume to a job posting, from inside whatever agent you already use.

No account. No API key. Install it and ask.


Start

Claude Code

claude mcp add reframed -- npx -y reframed-mcp

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "reframed": {
      "command": "npx",
      "args": ["-y", "reframed-mcp"]
    }
  }
}

Restart Claude Desktop.

Cursor

Settings → Features → MCP:

{
  "reframed": {
    "command": "npx",
    "args": ["-y", "reframed-mcp"]
  }
}

Continue.dev

In ~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "reframed",
      "command": "npx",
      "args": ["-y", "reframed-mcp"]
    }
  ]
}

Related MCP server: resume-tailor-mcp-server

Ask

Tailor my resume at ~/resume.md to this job: [paste the posting]

That's the whole thing.


What comes back

Two versions of the resume and a provenance summary — how much of the result is still your own words.

style

What you get

conservative

Light edits — your words, shaped for the ATS

reframed

Voice-preserving rewrite — stronger framing

both (default)

Both versions + provenance summary

The provenance summary is backed by a signed receipt at reframed.works/verify/<id> — the percentages are checkable, not just asserted.


The free tier

Three tailors a week. No sign-up, nothing to configure.

Counted per network address, on the same weekly window the site uses.

When they're gone, the tool says so and points at reframed.works/pricing.

Other limits:

  • .pdf resume input isn't supported — convert to .md or paste raw text

  • Job description goes in as raw text (URL scraping comes later)


For more than the free tier

An API key raises the ceiling to your plan's quota and runs the tailor against your saved voice profile.

  1. Sign in at reframed.works

  2. Settings → API Keys → Create key

  3. Copy the key (rt_live_...)

Then either export it:

export REFRAMED_API_KEY=rt_live_...

Or write it once and forget it:

mkdir -p ~/.config/reframed
echo "rt_live_..." > ~/.config/reframed/key

With a key present, calls run against the account. Without one, they run on the free tier. Nothing else changes.

Plans and quotas: reframed.works/pricing.


Pointing somewhere else

REFRAMED_API_BASE overrides the host — useful against a preview deployment or a local server. Defaults to https://reframed.works.


License

MIT — see LICENSE.
See NOTICE.md for credits.

Available Tools

1 tool
reframed_tailorA

Tailor a resume to a specific job. Preserves your voice. Returns two versions and a provenance summary.

ParametersJSON Schema
NameRequiredDescriptionDefault
resumeYesFile path to a .md resume, or paste raw resume text. PDF not supported.
jdYesRaw job description text (paste from the posting).
styleNoWhich version to return. 'conservative' = light edits. 'reframed' = voice-preserving rewrite. 'both' = both (default).both

TDQS

A4.2/5.0
Behavior3/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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. 1 tool updatev1.0.0
    • First observedreframed_tailor

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no risk of confusion between tools.

Naming Consistency5/5

With a single tool, naming is trivially consistent; the name uses a clear verb_noun pattern.

Tool Count3/5

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.

Completeness4/5

The tool covers its stated purpose of tailoring a resume but lacks additional supporting operations like job description retrieval or resume parsing.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers