Skip to main content
Glama
deenesjakoruzh
notaprompt

reframed-mcp

by notaprompt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reframed-mcp

Reframed용 MCP 서버입니다. 모든 MCP 호환 에이전트 하네스에서 이력서를 직무에 맞게 조정하세요.

단일 도구: reframed_tailor. 이력서(파일 경로 또는 원문)와 직무 기술서를 입력으로 받습니다. 어조를 보존한 두 가지 버전과 출처 요약을 반환합니다.

API 키 발급

  1. reframed.works에 로그인합니다.

  2. 설정(Settings) → API 키(API Keys) → 키 생성(Create key)으로 이동합니다.

  3. 키(rt_live_...)를 복사합니다.

Related MCP server: CompleteMCP

설치

Claude Code

claude mcp add reframed -- npx -y reframed-mcp
export REFRAMED_API_KEY=rt_live_...

또는 키를 영구적으로 저장하려면:

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

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json 파일을 편집합니다:

{
  "mcpServers": {
    "reframed": {
      "command": "npx",
      "args": ["-y", "reframed-mcp"],
      "env": {
        "REFRAMED_API_KEY": "rt_live_..."
      }
    }
  }
}

Claude Desktop을 재시작합니다.

Cursor

Cursor 설정 → 기능(Features) → MCP:

{
  "reframed": {
    "command": "npx",
    "args": ["-y", "reframed-mcp"],
    "env": { "REFRAMED_API_KEY": "rt_live_..." }
  }
}

Continue.dev

~/.continue/config.json 파일:

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

사용법

설치 후 어시스턴트에게 다음과 같이 요청하세요:

~/resume.md에 있는 내 이력서를 이 직무에 맞춰 조정해줘: [직무 기술서 텍스트 붙여넣기]

스타일 옵션

style

결과물

conservative

가벼운 수정 — 본인의 어휘 유지, ATS 최적화

reframed

어조 보존 재작성 — 더 강력한 프레이밍

both (기본값)

두 버전 모두 + 출처 요약

제한 사항

  • API 키당 시간당 100회 호출

  • V1에서는 .pdf 이력서 입력이 지원되지 않음 — .md로 변환하거나 원문을 붙여넣으세요.

  • 직무 기술서 입력: 원문 붙여넣기 (V2에서 URL 스크래핑 기능 추가 예정)

라이선스

MIT — LICENSE를 참조하세요. 크레딧은 NOTICE.md를 참조하세요.

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
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

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

Resources

Related MCP Connectors

Related MCP Servers