Developers

Reach your workspace from your own tools.

A personal access token authenticates as you and is hard-scoped at a single routing chokepoint. Point Claude at it, or call the REST API directly — either way it reaches exactly what the token allows and nothing more.

Developers

Work your tasks from Claude.

Generate a personal access token, run the setup script, and RESK shows up as an MCP server in Claude Desktop or Claude Code. It authenticates as you — and only reaches what the token is scoped to.

  • Settings → Developers → generate token

    Tokens are yours, revocable, and carry your real role underneath.

  • Scoped at the routing chokepoint

    Tasks CRUD plus read-only projects. Not a wider key with rules bolted on after.

claude_desktop_config.json

written by setup.py
{  "mcpServers": {    "resk": {      "command": "python",      "env": { "RESK_PAT": "crm_pat_·······" }    }  }}

What the token can reach

list_tasksTasks
create_taskTasks
update_taskTasks
list_projectsProjects · read-only

Everything else is refused before the user is even resolved — including minting more tokens.

Start hereYour next won deal

Never rebuild the same project twice.

We set up your workspace and your first admin. Your team joins by invite, and the next deal you close arrives as a project that is already moving.

  • We set up your workspace
  • Your team joins by invite
  • Bring the pipeline you have

Prefer to talk first?

  1. Deal marked Closed/Won

    One status change

    01

  2. Project, milestones, 5 tasks

    Drafted from the conversation

    02

  3. #harborview-onboarding

    Channel opened, kickoff posted

    03

  4. Owner notified

    In-app and browser push

    04

Every step above runs from one status change.