Managing tickets and a wiki through an AI agent works badly when the data lives in a cloud tool. You add an MCP server, and then every query goes through an API: with a few thousand tickets the agent can't cheaply answer "is there already a bug report for this?", and updating something means hitting exactly the right tool with exactly the right fields. The prompt has to be precise, or nothing happens. So we skipped the API layer. Tickets and wiki pages are YAML + Markdown files inside the git repo. Nothing else. That means your AI IDE (Cursor, or whatever you use) already has everything it needs. it greps, reads, edits and creates tickets the same way it works with source code. No MCP server, no tokens, no schema mapping. And because it's just YAML, prompts don't have

  • 情报分类：项目价值、技术价值
  • 命中依据：AI管理工单与文件的项目，技术实用
  • 来源：Reddit · SideProject
  • 原作者：/u/Alternative-Try7044 https://www.reddit.com/user/Alternative-Try7044
  • 发布时间：2026/9/10 20:42:14