Connect an agent to DYNIK

1. Create a key

In DYNIK, open Settings → Agents and choose Create key. Tick only what the agent needs: a key that can only read cannot change anything, whatever it is asked to do. The secret is shown once and stored only as a fingerprint, so copy it before closing the dialog.

2. Configure your client

# Read the key without echoing it or storing it in shell history.
printf 'DYNIK key: ' >&2
IFS= read -r -s DYNIK_MCP_KEY
printf '\n' >&2
export DYNIK_MCP_KEY
claude mcp add-json --scope user dynik \
  '{"type":"http","url":"https://api.dynik.com/api/v1/mcp","headers":{"Authorization":"Bearer ${DYNIK_MCP_KEY}"}}'

# In Bash or zsh: this prompt neither echoes nor records the key in history.
printf 'DYNIK key: ' >&2
IFS= read -r -s DYNIK_MCP_KEY
printf '\n' >&2
export DYNIK_MCP_KEY

# ~/.codex/config.toml
[shell_environment_policy]
# The MCP transport can still read this variable; Codex shell commands cannot.
exclude = ["DYNIK_MCP_KEY"]

[mcp_servers.dynik]
url = "https://api.dynik.com/api/v1/mcp"
bearer_token_env_var = "DYNIK_MCP_KEY"
default_tools_approval_mode = "writes"

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "dynik": {
      "url": "https://api.dynik.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer ${env:DYNIK_MCP_KEY}" }
    }
  }
}

// ~/.copilot/mcp-config.json
{
  "mcpServers": {
    "dynik": {
      "type": "http",
      "url": "https://api.dynik.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer ${DYNIK_MCP_KEY}" },
      "tools": ["*"]
    }
  }
}

grok mcp add --transport http --scope user dynik https://api.dynik.com/api/v1/mcp \
  --header 'Authorization: Bearer ${DYNIK_MCP_KEY}'
grok mcp doctor dynik --json

{
  "mcpServers": {
    "dynik": {
      "type": "http",
      "url": "https://api.dynik.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer dnk_live_YOUR_KEY" }
    }
  }
}

3. Check it works

Ask the agent: “Use the dynik tools to tell me which account I am on and what you are allowed to do.” It should call get_profile and read back your email and the key’s scopes. If it cannot, the key is wrong or revoked, and the server answers 401 and says so.

Or check by hand after setting DYNIK_MCP_KEYin your shell:

curl -s https://api.dynik.com/api/v1/mcp \
  -H "Authorization: Bearer $DYNIK_MCP_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: server/discover" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "server/discover",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientInfo": {"name": "manual-probe", "version": "1.0"},
        "io.modelcontextprotocol/clientCapabilities": {}
      }
    }
  }'

Job-seeker tools

Employer tools

Confirm high-impact writes

Submitting an application, writing a cover letter, publishing or closing a posting, and rejecting a candidate require confirmation. Without it, the tool returns CONFIRMATION_REQUIRED describing the effect. After showing that preview to the person, call again with confirm: true to go ahead. Treat the refusal as a preview, not an error to route around.

New job postings are always created as drafts, so an agent cannot make a role live by accident. Writing a cover letter is gated for a different reason: it spends one of the plan’s monthly AI generations, which do not refill on request.

Errors

Tool failures come back as MCP tool errors carrying code, message and retryable, so an agent never has to parse prose to decide what to do next.

A JSON-RPC request ID links a call to its response; it does not prevent a duplicate write indefinitely. Identical calls with the same ID and arguments are blocked for 24 hours while the replay cache is available. If a call with idempotentHint: false times out, inspect the current state before deciding whether to call it again. Check list_applications after creating an application, list_cover_letters after writing a cover letter, list_job_postings after creating a posting, get_candidate after moving a candidate, or list_resumes after uploading a resume. Ask the account owner if the result is still unclear.

For a write you may need to retry, pass operation_key: a unique string you choose (a UUID works well). The five non-idempotent tools (create_application, create_job_posting, update_candidate_status, upload_resume and generate_cover_letter) run at most once per key: a later call with the same key and identical arguments returns the remembered outcome (replayed: true on success) instead of running again, and reusing the key with different arguments is a CONFLICT. A call whose outcome is not yet known answers OPERATION_IN_PROGRESS, retryable while the original may still be running, not retryable once it is stale. Keys are remembered for 7 days from last use. A refusal (validation, confirmation, quota, not-found) is not remembered, so the confirming retry with the same key still runs.

Rate limits

120 calls per minute per key, and 300 per minute from one IP address across all keys. Exceeding either returns HTTP 429 with a Retry-After header and a RATE_LIMITED body carrying retry_after_seconds. Requests are refused, never silently dropped.

Protocol details

• Transport: Streamable HTTP, POST only. The endpoint is stateless: no session id is minted, and GET and DELETE answer 405. Send one message per POST with an id for every request. Legacy clients may batch up to ten messages.
• Protocol versions: 2026-07-28 (current), and 2025-11-25, 2025-06-18 and 2025-03-26 for clients that still open with an initialize handshake.
• Authentication: Authorization: Bearer on every request. Never in a query string, and cookies are ignored. DYNIK currently uses scoped keys created in Settings; interactive OAuth login is not available.
• Discovery: server/discover, plus RFC 9728 metadata at /.well-known/oauth-protected-resource.

If something goes wrong

• 401 on every call. The key is wrong, revoked or expired. Check Settings → Agents; the status column says which.
• A tool you expected is missing. The key lacks its scope. Scopes cannot be added to an existing key. Create a new one and revoke the old.
• 400 with -32022. Your client asked for a protocol version we do not speak; the error lists the ones we do.
• 403 with “Origin not allowed”. Something is sending a browser Origin header. MCP clients send none; this is the DNS-rebinding guard doing its job.