AI integration
You connect the AI in your editor, such as Claude Code, to tidoly through MCP (Model Context Protocol). There are two things you can connect, and they handle different things.
tidoly MCP is a tool for building and launching apps (install · build · deploy · address), and it covers only that app's repository and work record. Gitea MCP is a tool for working with Gitea, used when you need repositories outside that app or everyday development work such as PRs · reviews.
Which one to use
| tidoly MCP | Gitea MCP | |
|---|---|---|
| A tool for what | The platform — asset install · build · deploy · address · login (SSO) · logs | Gitea |
| Git · issue scope | This app's single repository | All of Gitea — other repositories · PRs · reviews · files · releases · wiki · search |
| When to use | Initial setup, up to getting the app into a first usable state | Everyday development after that — work on existing repositories · PRs · moving across several repositories |
| Credential | Per-project token | One AI account per person in a Gitea (independent of projects) |
| Where it can be reached | Only inside the VPN | Anywhere (public address) |
| Guide | Chapter 10 · Build apps with AI tools | Gitea MCP |
You do not need both. tidoly MCP alone is enough to build and launch a new app. Add Gitea MCP when you have existing repositories or collaboration work.
The default path for pushing code is tidoly MCP. When you write files with Gitea MCP, each file becomes its own commit and the history gets scattered.