Skip to main content
Glama
deenesjakoruzh
notaprompt

reframed-mcp

by notaprompt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reframed-mcp

Reframed 用のMCPサーバーです。MCP互換のエージェントハーネスから、職務経歴書を求人内容に合わせて調整します。

ツールは reframed_tailor の1つです。職務経歴書（ファイルパスまたは生のテキスト）と求人内容を受け取ります。本人の語り口を維持した2つのバージョンと、変更履歴の要約を返します。

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キーあたり1時間100回まで

  • V1では .pdf 形式の職務経歴書入力は非対応 — .md に変換するか、生のテキストを貼り付けてください

  • 求人内容の入力：生のテキストを貼り付けてください（URLスクレイピングはV2で対応予定）

ライセンス

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