PIL
Related Servers
Alternatives to PIL
- AlicenseNot gradedqualityDmaintenancePrivacy-first personal knowledge database for your AI that ingests data exports (Google Takeout first) and exposes them via MCP tools like search and list items. Runs locally with no cloud or telemetry.MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes a locally built, searchable index of your saved Instagram reels — AI summaries, key points, transcripts, categories, and every extracted tool, place, product, and link — to any AI assistant over MCP. Enables chat-based search and retrieval across the whole collection without leaving the conversation.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceTurns likes, bookmarks, and saved links into persistent project-aware memory, enabling AI agents to search, import, and process personal content through a local SQLite-backed MCP server.Apache 2.0
- AlicenseBqualityBmaintenanceSelf-hosted MCP server for Instagram creators: publish, schedule, triage comments and DMs, and read insights through Meta's official Instagram API, with approval before every write.42MIT
- AlicenseAqualityCmaintenanceA local, read-only MCP server that makes bookmarks from browsers, read-later apps, and export files accessible to AI assistants, enabling search, triage, and summarization without sending data anywhere.870 npm1MIT
- AlicenseBqualityBmaintenanceSelf-hosted MCP server and CLI for publishing and scheduling Instagram Reels, photos, carousels and stories through the official Instagram Graph API. Validates and auto-fixes media with ffmpeg, keeps a persistent queue, and lets AI agents read insights and reply to comments.122MIT
- AlicenseNot gradedqualityBmaintenanceThin MCP server that turns each tool into one authenticated call to a self-hosted Instagram REST API, letting an agent schedule and publish posts, take and keep insights snapshots, and reply to comments and DMs by rules within Meta's limits. At startup it reads the API token's permissions and exposes only the tools that token can use.MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct purpose: single-post retrieval (get_post), collection listing (list_folders), tag listing (list_tags), aggregate metrics (library_stats), and query-based retrieval (search_posts). There is no meaningful overlap between them, so an agent can select the right tool unambiguously.
Four tools follow a clean verb_noun pattern (get_post, list_folders, list_tags, search_posts). library_stats breaks the pattern by being noun-only with no verb, a minor deviation that doesn't hurt readability.
Five tools is well-scoped for a read/browse library server. Each tool earns its place, covering retrieval, browsing by folder/tag, search, and stats without redundancy.
The read-side surface is solid: single-item lookup, folder/tag enumeration, search, and stats cover the main workflows. Minor gaps exist—no plain list-all-posts or folder-contents tool—but search_posts with folder/tag filters largely compensates.