English Français العربية

app.reassign/reassign

Official registry Productivity

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

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

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  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.

Frequently asked questions

What is app.reassign/reassign?

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

How do I install app.reassign/reassign?

It runs as a remote server. In Claude Code: claude mcp add --transport http reassign 'https://reassign.app/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does app.reassign/reassign need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is app.reassign/reassign open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains app.reassign/reassign?

It is published by reassignai. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.