Model Context Protocol

Hand your assistant the evidence, not your resume.

The Idynic MCP server gives Claude, Cursor, or any MCP client direct access to your career portrait: the claims you have reviewed, the roles you are tracking, and the tools that turn one into the other. No pasting a resume into a chat box every time.

Read the setup docs See the config

A session, start to finish.

Three turns from a job link to something you can send. The tool calls below are the real ones, with the arguments and responses the server uses.

Your assistantidynic mcp

youSave this posting and tell me how I actually stack up: idynic.com/examples/demo-role

calladd_and_match

{
  "url": "https://idynic.com/examples/demo-role",
  "description": "Staff Platform Engineer at Glasspine Logistics..."
}

result

{
  "opportunity": {
    "id": "0000de00-0000-4000-8000-000000000002",
    "title": "Staff Platform Engineer",
    "company": "Glasspine Logistics"
  },
  "scores": { "overall": 78, "must_have": 84, "nice_to_have": 61 },
  "strengths": [
    {
      "requirement": "Multi-region Kubernetes in production",
      "match": {
        "claim": "Active/active EKS migration, 11-minute failover",
        "type": "achievement",
        "similarity": 91
      }
    }
  ],
  "gaps": [
    {
      "requirement": "Managed a team of 8 or more",
      "type": "experience",
      "category": "mustHave"
    }
  ]
}

assistantSaved and scored. You clear the platform requirements; the one must-have with nothing behind it is direct people management at that headcount.

youIs that gap showing up everywhere, or just this one role?

callportfolio_gaps

{ "status": ["tracking", "applied"] }

result

{
  "opportunities_analyzed": 14,
  "gaps_by_type": {
    "experience": [
      {
        "text": "Managed a team of 8 or more",
        "opportunity": "Staff Platform Engineer",
        "category": "mustHave"
      }
    ],
    "skill": [],
    "education": [],
    "certification": []
  },
  "score_distribution": {
    "avg_overall": 71,
    "avg_must_have": 79,
    "avg_nice_to_have": 58
  }
}

assistantIt is the pattern, not the posting. Headcount ownership is the recurring must-have across the roles you are tracking.

youSend me the link for the one I tailored yesterday.
callcreate_share_link
```
{ "id": "0000de00-0000-4000-8000-000000000002" }
```
result (text)
```
Share link created: https://idynic.com/shared/danawrenfielddemoplatform2026abc
Expires: 2099-01-01T00:00:00.000Z
```
assistantHere it is. The page opens the tailored profile with the evidence sitting behind each line.

Illustrative session. Glasspine Logistics is a fictional company and the identifiers are sample values. The tool names, arguments, and response shapes are the ones the server uses.

More than 70 tools, grouped around one job.

Get a role in front of an employer with your own evidence behind every line. Here is the shape of it.

Read the portrait

Your assistant can pull the evidence you have already reviewed, with the confidence score attached to each claim.

get_profile
get_claims
get_claim_detail
get_base_resume

Work an opportunity

Save a posting from a URL or pasted text, score it against your portrait requirement by requirement, and see which gaps keep recurring.

add_and_match
analyze_match
portfolio_gaps
update_opportunity_status

Build the application kit

Reframe the portrait for one role, draft the cover letter, grade the result, and hand over a link the employer can open.

retailor_opportunity
generate_cover_letter
judge_application
create_share_link

The full list is in the MCP reference, and the server answers help at runtime with the same inventory.

Two ways to connect.

Point a client at the hosted endpoint over Streamable HTTP, or spawn the server locally over stdio. Both read the same portrait.

Hosted, no install

Remote over HTTP

One endpoint for every client that speaks Streamable HTTP. The API key you send decides whose portrait the tools read.

{
  "mcpServers": {
    "idynic": {
      "url": "https://idynic.com/api/mcp",
      "headers": {
        "Authorization": "Bearer idn_your_key"
      }
    }
  }
}

Local process

stdio via npx

Prefer a locally spawned server? The published package reads your key from the environment and talks to the same API.

{
  "mcpServers": {
    "idynic": {
      "command": "npx",
      "args": ["-y", "@atriumn/idynic-mcp"],
      "env": {
        "IDYNIC_API_KEY": "idn_your_key"
      }
    }
  }
}

The key decides what the assistant can touch.

Every Idynic API key carries a list of scopes, and the server enforces them per tool call. A key holding only read:profile and read:claims can show your portrait to an agent and nothing more: a write comes back 403 insufficient_scope. Create a key per client, and revoke one without touching the others.

The full scope vocabulary is in the API reference. Keys live in Settings, API Keys.

Connect it in about two minutes.

Create a scoped key, paste one block of config, and ask your assistant what it can see.

Set up the MCP server