Skip to content
Development
MCP

chainlink-safe-fetch

Ships with chainlink: A simple, lean issue tracker CLI designed for AI-assisted development. Track tasks across sessions with context preservation.

From plugin
chainlink
3681 MCP

Claude Code

$ claude mcp add chainlink-safe-fetch -- python .claude/mcp/safe-fetch-server.py

From the README

What can you do with chainlink-safe-fetch?

  • Local-first

    All data stored in SQLite (.chainlink/issues.db)

  • Session management

    Preserve context across Claude/AI sessions with handoff notes

  • Context compression resilience

    Breadcrumb tracking via session action survives context resets

  • Quick workflow

    chainlink quick creates, labels, and starts work in one command

  • Issue templates

    Built-in templates for bugs, features, audits, investigations, and more

  • Subissues

    Break large tasks into smaller, trackable pieces

  • Dependencies

    Track blocking relationships between issues

  • Related issues

    Link related issues together for context

Security report

Info

Not enough data

  • Known flaws

    Not published

  • Signed build

    Not published

  • Maintained

    Aug 9, 2026

    Last push

  • Licence

    MIT

  • Runs as

    Local process

    On your machine

  • Deprecated

    Not published

Signals from public registries, not an audit. Checked Nov 15, 2026.

chainlink README

Chainlink

Crates.io Downloads License: MIT AI Generated

A simple, lean issue tracker CLI designed for AI-assisted development. Track tasks across sessions with context preservation.

Chainlink: The Missing Memory Layer for AI-Assisted Development

Features

  • Local-first: All data stored in SQLite (.chainlink/issues.db)
  • Session management: Preserve context across Claude/AI sessions with handoff notes
  • Context compression resilience: Breadcrumb tracking via session action survives context resets
  • Quick workflow: chainlink quick creates, labels, and starts work in one command
  • Issue templates: Built-in templates for bugs, features, audits, investigations, and more
  • Subissues: Break large tasks into smaller, trackable pieces
  • Dependencies: Track blocking relationships between issues
  • Related issues: Link related issues together for context
  • Labels & priorities: Organize issues with labels and priority levels
  • Milestones: Group issues into milestones/epics for release planning
  • Time tracking: Start/stop timers to track time spent on issues
  • Smart recommendations: chainlink next suggests what to work on based on priority and progress
  • Tree view: Visualize issue hierarchy with chainlink tree
  • JSON output: --json flag for structured, machine-readable output
  • Quiet mode: --quiet flag for minimal, pipe-friendly output
  • Batch operations: close-all with label/priority filtering
  • Export/Import: Backup and restore issues in JSON format
  • Issue archiving: Archive old closed issues to keep the active list clean
  • Claude Code hooks: Behavioral guardrails that inject best practices into AI sessions
  • Stale session detection: Auto-ends sessions idle >4 hours on next startup
  • Customizable rules: Override default rules via .chainlink/rules/ markdown files
  • No sync complexity: No git hooks, no auto-push, just simple local storage

Installation

# Install from crates.io
cargo install chainlink-tracker

The binary is named chainlink and will be available in your PATH after install.

Build from Source

git clone https://github.com/dollspace-gay/chainlink.git
cd chainlink/chainlink
cargo install --path .
# The binary will be at ~/.cargo/bin
# Or build without installing

cargo build --release
# The binary will be at target/release/chainlink

Quick Start

# Initialize in any project
chainlink init

# Start a session when you begin work
chainlink session start

# Create issues
chainlink create "Fix login bug" -p high
chainlink create "Add dark mode" -d "Support light/dark theme toggle"

# Quick create + label + start working in one command
chainlink quick "Fix login bug" -p high -l bug

# Use a template for structured issues
chainlink create "Login fails on refresh" --template bug

# Set what you're working on
chainlink session work 1

# Record breadcrumbs before context compression
chainlink session action "Investigating token refresh logic"

# End session with handoff notes
chainlink session end --notes "Fixed auth bug, dark mode is next"

Commands

Issue Management

CommandDescription
chainlink create <title>Create a new issue
chainlink create <title> -p highCreate with priority (low/medium/high/critical)
chainlink create <title> -d "desc"Create with description
chainlink create <title> --template bugCreate from template (bug/feature/refactor/research/audit/continuation/investigation)
chainlink create <title> --work -l bugCreate, label, and start working on it
chainlink quick <title> [-p high] [-l label]Shorthand: create + label + set as active work item
chainlink subissue <parent_id> <title>Create a subissue under a parent
chainlink subissue <parent_id> <title> -p highSubissue with priority
chainlink listList open issues
chainlink list -s allList all issues
chainlink list -s closedList closed issues
chainlink list -l bugFilter by label
chainlink list -p highFilter by priority
chainlink show <id>Show issue details
chainlink show <id> --jsonShow issue details as JSON
chainlink update <id> --title "New"Update title
chainlink update <id> -d "desc"Update description
chainlink update <id> -p criticalUpdate priority
chainlink close <id>Close an issue
chainlink close <id> --no-changelogClose without adding a changelog entry (e.g. internal scaffolding subissues)
chainlink close-allClose all open issues
chainlink close-all --no-changelogClose all without changelog entries (e.g. internal scaffolding subissues)
chainlink close-all -l bugClose all issues with a specific label
chainlink close-all -p lowClose all issues with a specific priority
chainlink reopen <id>Reopen a closed issue
chainlink delete <id>Delete an issue (with confirmation)
chainlink delete <id> -fDelete without confirmation

Tip: Add --quiet / -q to any command for minimal output (just the ID), useful for scripting and piping.

Comments & Labels

CommandDescription
chainlink comment <id> "text"Add a comment to an issue
chainlink label <id> <label>Add a label to an issue
chainlink unlabel <id> <label>Remove a label from an issue

Dependencies

CommandDescription
chainlink block <id> <blocker_id>Mark issue as blocked by another
chainlink unblock <id> <blocker_id>Remove blocking relationship
chainlink blockedList all blocked issues
chainlink readyList issues ready to work on (no blockers)

Related Issues

CommandDescription
chainlink relate <id1> <id2>Link two related issues together
chainlink unrelate <id1> <id2>Remove relationship between issues

Milestones

CommandDescription
chainlink milestone create <name>Create a new milestone
chainlink milestone create <name> -d "desc"Create with description
chainlink milestone listList all milestones
chainlink milestone show <id>Show milestone details and progress
chainlink milestone add <milestone_id> <issue_id>Add an issue to a milestone
chainlink milestone remove <milestone_id> <issue_id>Remove an issue from a milestone
chainlink milestone close <id>Close a milestone
chainlink milestone reopen <id>Reopen a closed milestone

Archiving

CommandDescription
chainlink archive <id>Archive a closed issue
chainlink unarchive <id>Restore an archived issue
chainlink archivedList all archived issues
chainlink archive-older <days>Archive issues closed more than N days ago

Export/Import

CommandDescription
chainlink exportExport all issues to JSON (stdout)
chainlink export -o backup.jsonExport to a file
chainlink import backup.jsonImport issues from JSON file
chainlink import backup.json --mergeMerge with existing issues

Smart Navigation

CommandDescription
chainlink nextRecommend the next issue to work on (by priority/progress)
chainlink treeShow all issues in a tree hierarchy
chainlink tree -s openShow only open issues in tree view

Time Tracking

CommandDescription
chainlink start <id>Start a timer for an issue
chainlink stopStop the current timer
chainlink timerShow current timer status

Session Management

Sessions preserve context across AI assistant restarts. Stale sessions (idle >4 hours) are auto-ended on the next startup.

CommandDescription
chainlink session startStart a session, shows previous handoff notes
chainlink session work <id>Set the issue you're currently working on
chainlink session action "..."Record a breadcrumb (survives context compression)
chainlink session statusShow current session info and last action
chainlink session endEnd the current session
chainlink session end --notes "..."End with handoff notes for next session
chainlink session last-handoffRetrieve handoff notes from the previous session

Daemon (Optional)

The daemon auto-flushes session state every 30 seconds.

CommandDescription
chainlink daemon startStart background daemon
chainlink daemon statusCheck if daemon is running
chainlink daemon stopStop the daemon

Workflow Example

$ chainlink session start
Previous session ended: 2026-01-15 09:00
Handoff notes:
  Working on auth bug. Found issue in token refresh.

Session #5 started.

# Quick create + label + start working in one step
$ chainlink quick "Fix token refresh" -p high -l bug
Created issue #3
Now working on: #3 Fix token refresh

# Record breadcrumbs as you work (survives context compression)
$ chainlink session action "Found root cause in refresh_token()"

$ chainlink comment 3 "Fixed the token refresh issue"
Added comment to issue #3

$ chainlink close 3
Closed issue #3

$ chainlink ready
Ready issues (no blockers):
  #2    medium   Add dark mode

$ chainlink session end --notes "Closed auth bug #3. Dark mode is next."
Session #5 ended.
Handoff notes saved.

Storage

All data is stored locally in .chainlink/issues.db (SQLite). No external services, no network requests.

Claude Code Hooks

Chainlink includes behavioral hooks for Claude Code that inject best practice reminders into AI sessions. These hooks help ensure Claude follows coding standards without requiring manual prompting.

Requirement: Python 3.6+ must be installed and available in your PATH for hooks to work. The VS Code extension will warn you if Python is not detected.

What the Hooks Do

The hooks are located in .claude/hooks/ and configured in .claude/settings.json:

HookTriggerPurpose
prompt-guard.pyEvery promptInjects language-specific best practices (condensed after first prompt)
post-edit-check.pyAfter file editsDebounced linting reminder to verify changes compile
work-check.pyBefore write/editEnforces issue tracking (configurable: strict/normal/relaxed) and blocks git mutations
session-start.pySession start/resumeLoads context, detects stale sessions, restores breadcrumbs after context compression

Behavioral Guardrails

The hooks enforce these principles:

  1. No Stubs: Implement complete, working code - no placeholder functions or TODO comments
  2. No Dead Code: Identify incomplete features and complete them, or remove truly dead code
  3. Full Features: Implement complete features as requested, don't stop partway
  4. Error Handling: Proper error handling everywhere, no panics on bad input
  5. Security: Validate input, use parameterized queries, no command injection

Large Task Management

When code will exceed 500 lines, the hooks guide Claude to:

  1. Create a parent issue for the feature
  2. Break it into subissues for trackable components

Stars on GitHub

Momentum

stars in total
368
Star history of dollspace-gay/chainlink on GitHub, a chart by star-history.com

More MCP servers from other plugins.

chrome-devtools
Auto-invoked

chrome-devtools

MCP

Connects to Chrome over the DevTools Protocol to inspect the DOM, network requests and console output.

ecc2w293k
@affaan-m@affaan-mInstall MCP
supabase

supabase

MCP

Queries a Supabase project: Postgres tables, auth users, storage and edge functions.

supabase2w114k
@supabase@supabaseInstall MCP

Questions about chainlink-safe-fetch.

Which coding agents can use chainlink-safe-fetch?
chainlink-safe-fetch works in any agent that reads an MCP config file: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf. Each agent reads it from its own file; this page names the file for each one.
How do I add chainlink-safe-fetch to Claude Code?
Run this in your terminal: claude mcp add chainlink-safe-fetch -- python .claude/mcp/safe-fetch-server.py