{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibjlc5ktcq2gnx5bawqdo2df5wzswlwn33zks3m3hmjosj5i6m5si",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mlzlwmnwnxo2"
  },
  "path": "/t/local-ai-for-document-search-informity-ai-runs-entirely-on-device/37769?page=2#post_27",
  "publishedAt": "2026-05-17T03:15:32.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "# Informity AI v0.13.0 is out\n\n# v0.13.0\n\nThis release introduces an optional MCP Server (Experimental) so trusted AI clients can query your local Informity library, while keeping a strong privacy-first and read-only default posture.\n\n# What’s included\n\n  * Added MCP Server (Experimental) to Settings for easy client integration.\n  * Added read-only MCP tools for health, file listing, semantic search, index status, and scan status.\n  * Kept MCP scope intentionally read-only in this release.\n  * Improved retrieval quality by filtering out local upload noise and reducing duplicate result entries.\n  * Simplified setup for external clients with a cleaner standard command flow.\n  * Added stronger safety controls and operational guardrails around MCP behavior.\n  * Added dedicated MCP logging so interactions are easier to audit and troubleshoot.\n\n\n\n# Notes\n\n  * Privacy model: MCP is disabled by default and should be enabled only for trusted clients.\n  * Scope: this release focuses on read-only MCP access; advanced/extended MCP capabilities remain deferred.\n  * QA status: validated through expanded MCP-focused automated coverage and end-to-end client checks during this release cycle.\n\n\n\n**Tag:** `v0.13.0`",
  "title": "Local AI for document search — Informity AI, runs entirely on-device"
}