English Français العربية

app.reassign/reassign

Registre officiel Productivité

Reassign: a circular 24-hour calendar and time-tracking copilot with ADHD-friendly scheduling.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http reassign 'https://reassign.app/api/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "reassign": {
            "type": "http",
            "url": "https://reassign.app/api/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Reassign
  2. Install
  3. What's inside
  4. Links
  5. License

Reassign

Reassign: a circular 24-hour day planner. One capability, five package forms, one canonical skill.

Reassign plans, edits, and reviews your day on a circular 24-hour calendar. It applies ADHD-friendly time-management methods as concrete edits to the dial, not advice recited back at you. The same scheduling capability ships in several package forms, all backed by one canonical skill and the Reassign MCP.

Install

FormHow
Claude Code plugin/plugin marketplace add reassignai/plugins → /plugin install reassign@reassign
Agent Plugin (VS Code, Cursor, Copilot, Codex, Kiro)Install from source with the repo URL — e.g. VS Code's Chat: Install Plugin From Source → https://github.com/reassignai/plugins
Standalone skillnpx skills add reassignai/plugins
Claude.ai / ChatGPT connectorAdd a custom connector pointing at https://reassign.app/api/mcp
npm (any stdio MCP client)npx -y @reassign/mcp

What's inside

plugins/                                  ← repo root = plugin root
├── plugin.json                           ← Agent Plugins 1.0.0 manifest
├── mcp.json                              ← Agent Plugins MCP config (streamable-http)
├── .claude-plugin/
│   ├── plugin.json                       ← Claude Code manifest
│   └── marketplace.json
├── .mcp.json                             ← Claude Code MCP config (type "http")
├── skills/
│   └── reassign-scheduling/              ← canonical skill (every form, zero copy)
│       ├── SKILL.md
│       └── references/
│           ├── adhd-methods.md
│           ├── focus.md             ← focus intervals, live pauses, and saved rhythms
│           ├── context.md           ← event and Inbox search, weather, and energy
│           ├── workflows.md
│           ├── taxonomy.md
│           ├── calendars.md          ← calendar and task-app sync, import policies, event kinds, mirroring
│           ├── reflection.md         ← reviewing a past day: marks + adherence
│           └── limits.md             ← subscription access, refusal codes, and retries
├── server.json                           ← Official MCP Registry entry
├── package.json                          ← npm client shim
├── npm/reassign-mcp.js                   ← npm shim entry (not bin/: Cowork and apps refuse a top-level bin/)
├── scripts/
│   ├── build.sh                          ← validates manifests + version lockstep
│   └── version.mjs                       ← reads/sets the two version trains
├── .github/workflows/
│   ├── publish-registry.yml
│   └── publish-npm.yml
├── README.md
└── LICENSE

The skills/reassign-scheduling/ directory is the single source of truth: every package form consumes it in place, with no copying.

Two manifests, on purpose

The root plugin.json/mcp.json pair is Agent Plugins 1.0.0; .claude-plugin/plugin.json + .mcp.json is the Claude Code format. Clients auto-detect by manifest path and read exactly one pair, so both ship side by side. They are not copies of each other — the same endpoint is "type": "streamable-http" under the spec and "type": "http" for Claude Code, so scripts/build.sh checks each file's transport vocabulary separately — and cross-checks that the two still name the same servers at the same URLs, since a copy-paste and a one-sided URL move are both silent breaks.

Versions

Two independent trains, both checked by scripts/build.sh:

TrainFilesWhat it tracks
pluginplugin.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, SKILL.mdthe skill and its manifests
packagepackage.json, server.jsonthe npm shim + registry entry, released on a v* tag
node scripts/version.mjs                 # print both
node scripts/version.mjs check           # exit 1 on drift
node scripts/version.mjs set plugin 1.11.0
  • Website: reassign.ai
  • MCP endpoint: https://reassign.app/api/mcp
  • Developer docs (MCP setup, REST API, error codes): reassign.dev

License

Apache-2.0 © Pogled Naprej d.o.o.

Questions fréquentes

Qu'est-ce que app.reassign/reassign ?

Reassign: a circular 24-hour calendar and time-tracking copilot with ADHD-friendly scheduling.

Comment installer app.reassign/reassign ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http reassign 'https://reassign.app/api/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour app.reassign/reassign ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

app.reassign/reassign est-il open source ?

Oui. Son code est sur GitHub sous licence Apache-2.0.

Qui maintient app.reassign/reassign ?

Il est publié par reassignai. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.