Bring your client.
Keep your role.
Use Gitflare from an MCP client: read a repository, draft a proposal, follow checks and approve work with the access level you choose.
ClaudeClaude CodeCodexChatGPTCursorVS CodeOpenCodeWindsurfZedAny MCP client
One endpoint.
A familiar workflow.
Gitflare's remote HTTP endpoint uses Cloudflare's Agents SDK MCP handler. Connect to your installation, sign in with OAuth, and review the access grant.
Clients that use fixed credentials can use a personal MCP token from account settings.
Read the MCP guideConnect to this installationOAuth
$ codex mcp add gitflare \ --url https://app.gitflare.io/mcp $ codex mcp login gitflareSee client-specific setup
The permission is part of the connection.
Choose an OAuth access level. Workspace roles and repository permissions still apply to every request.
| Access level | What the client may do |
|---|---|
| Read | Inspect repositories, proposals, revisions, and recorded checks. |
| Write | Contribute and start authorized work, including drafting proposals. |
| Land | Approve and land eligible revisions when your role permits it. |
| Admin | Manage authorized workspace and repository settings. |
After connecting, list repositories once to confirm the client reached the right workspace.
Make room
for more minds.
Parallel agents. One reviewed revision.
Get started