Istok.sh

vtimame4stars

Local-first project state, task tracking, and context for coding agents.

1# Istok.sh

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: Apache-2.0
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Istok.sh?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Istok.sh need an API key?

No required environment variable is listed on this record.

What transport does Istok.sh use?

Istok.sh runs locally over stdio.

When was Istok.sh last checked?

Last checked 2026-10-28. Local-first project state, task tracking, and context for coding agents.

From the publisher

Documentation

Why

If you work with Claude Code, Codex or Cursor, three things keep getting in the way:

Sessions end. Close the chat or hit the context limit, and the plan, the decisions and the half-finished work go with it.
Work is invisible. With several agents in several repositories, it is hard to tell who did what and what quietly stalled.
"Done" is a claim. The agent says the tests pass; nothing shows that it ran them.

Istok is a local CLI, MCP server and web UI. Your agent records its work through MCP while it goes; you keep talking to it as before. Everything stays on your machine in one SQLite file: no account, no cloud, and nothing written into your repository.

Quick start

1. Install (Linux and macOS, no root needed):

curl -fsSL https://get.istok.sh | sh

2. Connect your agent once, for your user. For Claude Code:

claude mcp add --transport stdio --scope user istok -- \
  istok mcp --actor-id claude --actor-name "Claude Code"

For Codex:

codex mcp add istok -- \
  istok mcp --actor-id codex --actor-name "Codex"

Cursor and other MCP clients are covered in the quick start, together with a short block of instructions that tells the agent when to use Istok.

3. Ask the agent to register your project. Start it in the repository and say:

Register this project in Istok.

Then give it real work as usual. It creates a task, claims it, runs the checks through Istok and completes the task with that evidence.

4. See what happened:

istok ui

The web UI opens on http://127.0.0.1:7700 with every project, task, run and check, and updates live while agents work.

Learn more

What is Istok — the problem and what you get.
Working with your agent — what to say to continue work, remember a rule or hand over to another agent.
Web UI and running it as a service.
How Istok works — projects, tasks and runs, validation, context and knowledge.
CLI and MCP tools reference.
Troubleshooting and FAQ.

The documentation is also available in Russian, and as llms.txt for agents.

Platforms

Releases are built for Linux (x86-64, ARM64) and macOS (Intel, Apple Silicon). Windows is not supported yet.

Releases are signed. istok update checks for a newer stable release, verifies it, backs up the database and migrates it; istok update --check only reports.

Build from source

Istok is written in Go with an embedded React web UI. Building needs Go with cgo (for SQLite) and pnpm:

make build      # writes bin/istok
make install    # installs into ~/.local/bin
go test ./...

A source build cannot update itself; install an official release for istok update.

License

Apache 2.0. Changes are listed in the changelog.