MCP Hub
Back to servers

tiddly-mcp

A Model Context Protocol server for TiddlyWiki that enables AI agents to read, write, search, and manage tiddlers within a Node.JS-hosted wiki instance.

Stars
2
Tools
5
Updated
Jan 4, 2026
Validated
Jan 11, 2026

Tiddly MCP

Tiddly MCP is a Model Context Protocol plugin for TiddlyWiki that lets you connect AI agents to your TiddlyWiki.

WARNING: This plugin is a work in progress.

This plugin is tested and works with:

The plugin only supports server (Node.JS-hosted) versions of TiddlyWiki.

This plugin provides the following tools to AI agents via MCP:

NameDescriptionArguments
list_tiddlersList all tiddlers or filter them using a filter expression.filter, limit, includeSystem, includeDetails
read_tiddlerRead a tiddler by title.title
search_tiddlersSearch for tiddlers containing specific text.query, field, caseSensitive
write_tiddlerCreate or update a tiddler by title.title, text, tags, type, username
delete_tiddlerDeletes a tiddler by title.title

The plugin defaults to read only mode. The update and delete tiddler tools are off by default.

Installation

This plugin only works with server (hosted on Node.JS) TiddlyWikis.

  1. Drag and drop $__plugins_rryan_tiddly-mcp.json into your Node.JS-hosted TiddlyWiki and import the tiddler, or copy the tiddly-mcp folder into your TiddlyWiki plugin path.
  2. Open the plugin configuration and customize the port and other settings.
  3. Restart your server and confirm you see [MCP] TiddlyWiki MCP Server started on port XXXX in your logs.

Authentication

For now, we recommend not exposing this MCP server to the Internet. You can use the plugin locally with Gemini CLI, Claude Code, or Claude Desktop without any security risks.

If you do expose the plugin to the Internet, we recommend:

  • Set it up behind a reverse proxy, just like your Node.JS-hosted TiddlyWik is.
  • Use HTTP Basic Authentication to protect access. Most clients support custom headers that allow you to provide a Authentication: Basic asdf1234 authentication header.
  • Set the CORS allowed hosts to the domain name you are hosting it on.
  • Use a path other than https://example.com/mcp to avoid attackers scanning for MCP servers.

Developing

To build the plugin JSON and folder:

pnpm install
pnpm build:folder

To run the unit tests:

pnpm test

To run integration tests with an MCP client against a development server:

pnpm test:live

Acknowledgements

Reviews

No reviews yet

Sign in to write a review