Gitea

@gitea list all organizations in our instance and show me their member counts

Here are the organizations in your Gitea instance: **Engineering** (12 members) - Main development teams **DevOps** (5 members) - Infrastructure and deployment **Documentation** (3 members) - Technical writing **Security** (4 members) - Security review and auditing This data comes from the paginated organizations endpoint. Each organization includes basic metadata like creation date and visibility settings. I can drill into any specific org if you need member details or repository lists.

This example uses the Get All Organizations tool to provide visibility across your self-hosted Gitea. Requires API key with org:read scope. Response is limited by the instance's pagination settings (typically 50 items per page) — larger instances may need follow-up queries to see all orgs.

@gitea what gitignore template should I use for a new Python data science project?

For a Python data science project, I recommend the **Python** gitignore template. Here's what it excludes: - Python bytecode (*.pyc, __pycache__) - Virtual environments (venv/, env/) - Jupyter notebook checkpoints (.ipynb_checkpoints/) - Distribution/packaging artifacts (dist/, build/, *.egg-info) - pytest cache and coverage reports This template covers standard Python patterns. You may want to manually add data-specific exclusions like `*.csv`, `*.h5`, or `models/` depending on your workflow.

This example demonstrates the Get Gitignore Template Info tool, which retrieves pre-configured ignore patterns. Useful during repository setup to avoid committing build artifacts or credentials. The template content is static — you'll need to customize it for project-specific data files or model checkpoints.

@gitea check our instance settings and tell me if LFS and time tracking are enabled for repos

Based on your Gitea instance's repository settings: **Git LFS**: ✅ Enabled - Large file storage is available for all repositories **Time Tracking**: ✅ Enabled - Issue time estimates and logging are active Additional flags: - HTTP Git access: Enabled - Repository mirroring: Enabled - External migrations: Disabled These are instance-wide defaults. Individual repositories may have features disabled at the repo level. LFS requires client-side git-lfs installation to use.

This example uses Get General Repository Settings to surface instance-level feature flags. Helpful for onboarding new teams or troubleshooting why a feature isn't available. Requires admin-level API access to read global settings. Note that these are defaults — repo owners can override some settings per-repository.

When Gitea MCP helps teams scope a self-hosted move

A 6-person engineering team evaluating a move from GitHub to self-hosted Gitea can use this MCP to audit their target instance before committing. The Get General Repository Settings and Get General Attachment Settings tools surface deal-breakers early—if your team relies on LFS for design assets and the instance has it disabled, you know before migration day. The Get All Organizations tool confirms the instance can handle your org structure at the scale you need. This is a pre-decision integration: run it once during evaluation, not daily in production. If you're already on Gitea and need live repo work (PRs, issues, commits), you want the GitHub MCP or a Git-native tool instead. Use Gitea MCP when you're shopping for a self-hosted platform, not operating one.

When ActivityPub federation matters for contributor identity

An open-source maintainer team running Gitea with ActivityPub federation enabled can use the Get ActivityPub Person Actor tool to resolve contributor identities across federated instances. This matters when you're coordinating with contributors who authenticate via Mastodon or other ActivityPub services—you need their actor URI to verify identity or send federated notifications. The use-case is narrow: if your Gitea instance isn't federated (most aren't), this tool does nothing. If you're just managing issues and PRs on a single instance, the other 18 tools won't help either—they're mostly settings-inspection, not workflow automation. Use this MCP when you're running a federated Gitea setup and need programmatic access to ActivityPub metadata. For standard repo work, stick with Git or GitHub integrations.

When Gitea MCP speeds up bulk repository creation

A platform team provisioning 20+ new service repos per quarter can use the Get Gitignore Template Info and Get Label Template Info tools to standardize repo setup without manual clicks. You script the template fetch, apply it to each new repo via API, and ensure every service starts with the same ignore rules and label taxonomy. This works when your Gitea instance has custom templates defined and you're creating repos in batches—if you're provisioning one repo a month, the overhead isn't worth it. The MCP doesn't create repos itself (you'd call the Gitea API directly for that), but it surfaces the template data you need to feed into your provisioning script. Use this when you're automating repo creation at a cadence where consistency matters more than speed.