{"repo":"acertainKnight/project-thoth","free":true,"listed":false,"github":"https://github.com/acertainKnight/project-thoth","clone":"git clone https://github.com/acertainKnight/project-thoth.git","description":"An advanced AI-powered research assistant system built for flexibility, extensibility, and user control. Thoth combines intelligent automation with comprehensive customization — every prompt, schema, and source can be tailored to your workflow.","language":"Python","stars":13,"topics":["ai-agent-tools","ai-agents","mcp","mcp-server","obsidian","obsidian-plugin","ai-research-assistant","letta-agents","microservices","multi-agent-systems"],"license":null,"category":"mcp-servers","readme_excerpt":"Thoth Research Assistant A local-first, extensible research assistant for staying on top of AI/ML papers. Built with Python, Letta, and Obsidian. --- About This Project The Problem As an AI practitioner juggling a full-time job while trying to stay current with rapid advancements in AI research, I found myself drowning in papers. Existing research tools were too rigid—they locked me into their workflow, their sources, their extraction schemas. I couldn't easily add new paper sources, customize what metadata got extracted, or control where my data lived. But the real friction wasn't just the lack of customization—it was the interface . Research tools forced me to constantly hunt through settings files, create countless memory configurations, edit YAML configs, and manage dozens of rule files. Sure, I could edit these manually, but why should that be the only option? The Insight Users want a single integration point: natural language. They don't want to manage files—they want to tell the agent what they need and have it happen. This drove a core architectural decision: the agent has access to everything a user can do manually . Every setting, every prompt template, every research query, every extraction schema—the agent can read and modify all of it through MCP tools. The system is deeply configurable, but users shouldn't have to learn the configuration surface to use it. In practice, this means you can say things like: - \"The notes you're generating from papers need to include","default_branch":null,"files":null,"tree":[],"storefront":"/r/acertainKnight","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/acertainKnight/project-thoth/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}