Tisty runs on your own machine — the client starts it, so there is no endpoint to ping. 127 installs a week from npm. Last commit 9 Nov 2026.
Agents plan in Markdown and work in tasks with steps, where you can follow and audit every stage.
We read the source, 21 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"http://169.254.169.254/latest",
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
r#""share.doc","id":"01M14RFT9ECC2B6E4CX4P59XPH","d":{"server":"https://tisty.cl","link":"k7Qm2xPa","key":"tWj3cJFtRiwp6ms2QS6DKXwHL2aGnEB6HcDUhX9r99E","edit":"edit-token","admin":"admin-token","version":1}"#,
пакет tisty-mcp ссылается на rgdevment/mcp-plugins
Edit::Drop { at } if !out.is_empty() => {
out.remove(at % out.len());
let secret = elsewhere.path().join("id_ed25519");
"envelope": "54454e56000000db7b22636f6e7472616374223a22312e362e30222c226b696e64223a226d61696e222c226964223a22686f7374696c65222c2276657273696f6e223a312c227365616c6564223a66616c73652c227061727473223a5b7b226e616d65223a226669727374222c22636f6d70726573736564223a747275652c2273656…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Tisty and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tisty -- npx -y tisty-mcp
{
"mcpServers": {
"tisty": {
"command": "npx",
"args": [
"-y",
"tisty-mcp"
]
}
}
}
[mcp_servers.tisty]
command = "npx"
args = ["-y", "tisty-mcp"]
{
"mcpServers": {
"tisty": {
"command": "npx",
"args": [
"-y",
"tisty-mcp"
]
}
}
}
{
"servers": {
"tisty": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tisty-mcp"
]
}
}
}
Self-hosted Markdown memory for AI agents: notes you can read and edit, with hybrid search.
Your agents, on a team with you. Every piece of work shows who did it and who accepted it.
Persistent work tracking for AI agents: tasks, status and history that follow you across machines
The markdown workspace your AI can read, search, and suggest edits in — every change signed.
Write and edit shared markdown pages with your team; every block shows who wrote it.
Your work meetings, notes, people, tasks and follow-ups from Fluent, in your AI assistant.
Lets your assistant work with the people and agents in your Ziggs workspaces: inbox, chats, tasks.
One shared memory for every AI you use, in plain Markdown files you own.
Answers built from our own checks of this server.