Danbooru-Turso MCP Server
Stores and manages Danbooru character data in a Turso cloud database with automatic upsert functionality for updating existing posts.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Danbooru-Turso MCP Server
Simple MCP server for collecting Danbooru character data and storing it in Turso database.
🎯 Purpose
Automatically collect and save Danbooru character data to Turso cloud database with automatic upsert (updates existing posts).
Related MCP server: alaya
✨ Features
📥 Collect character data from Danbooru API with automatic pagination
💾 Store in Turso cloud database
🔄 Auto-update existing posts (INSERT OR REPLACE)
⚡ Fast & Simple - Single tool, single purpose
🛠️ Tool
collect_and_save
Collect all posts for a character tag and save to Turso database.
Parameters:
tag(required): Character tag to collect (e.g., "yatogami_tenka")max_posts(optional): Maximum number of posts to collect
Example:
{
"tag": "yatogami_tenka",
"max_posts": 1000
}Response:
{
"success": true,
"tag": "yatogami_tenka",
"collected": 119,
"new_posts": 111,
"updated_posts": 8
}📊 Database Schema
This MCP uses the following table structure:
CREATE TABLE IF NOT EXISTS posts (
id INTEGER PRIMARY KEY,
tags TEXT NOT NULL,
tag_count INTEGER NOT NULL,
rating TEXT NOT NULL,
score INTEGER NOT NULL,
fav_count INTEGER NOT NULL,
file_url TEXT NOT NULL,
pixiv_id INTEGER
);Note: If you need additional fields (like image_width, image_height, created_at, etc.),
you can modify src/services/turso.ts to include them. The table is only created
if it doesn't exist (CREATE TABLE IF NOT EXISTS), so existing data is safe.
Danbooru API returns 50+ fields per post. This MCP stores the most commonly used fields for performance and simplicity. The current schema covers the essential data for most use cases.
🚀 Deployment
Smithery (Recommended)
Push to GitHub
Deploy on Smithery with environment variables:
TURSO_DATABASE_URL- Your Turso database URLTURSO_AUTH_TOKEN- Your Turso auth token
Local Development
npm install
npm run build
npm start📦 Environment Variables
TURSO_DATABASE_URL- Turso database URL (required)TURSO_AUTH_TOKEN- Turso auth token (required)PORT- Server port (default: 3000)
📖 Usage Example
Collect data:
collect_and_save({
tag: "yatogami_tenka",
max_posts: 500
})Response:
Shows how many posts were collected
Shows how many were new vs updated
Handles duplicates automatically with UPSERT
📝 License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.
Store, query, and update structured data from any AI agent
Supabase-compatible Postgres for agents: projects, branches, SQL, auth, storage, email.
Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceArchives posts from X into a local SQLite database and provides tools for semantic analysis and natural language search. It enables agents to manage low-cost data ingestion and retrieve relevant posts using local embeddings and topic labeling.3-
- AlicenseNot gradedqualityDmaintenanceA local memory engine for AI agents. Stores conversation episodes, consolidates knowledge through a neuroscience-inspired lifecycle, and builds a personal knowledge graph — all in a local SQLite database.19MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to store and retrieve long-term memories with semantic search, supporting various memory types and tags via PostgreSQL and pgvector.13 npmMIT
- AlicenseAqualityAmaintenanceSelf-hosted long-term memory gateway for AI clients, deployed to your own Cloudflare account (Workers + D1 + Vectorize). It captures conversations, consolidates them overnight, and exposes MCP tools to search, recall and write memories from any MCP client.10142AGPL 3.0