Integrations: GitHub, GitLab & Forgejo, MCP

Three modules connect Enclessa to tools outside it:

• GitHub mirrors a repository's issues and pull requests, or a Projects v2 project, onto a board, and can push a moved card back.
• GitLab & Forgejo does the same for a GitLab, Forgejo or Gitea repository's issues and merge requests.
• MCP lets an AI agent you run (Claude Desktop, an IDE, a hosted assistant) connect to Enclessa and use the same tools as the companion, as you.

Each is installed and configured by an administrator in the marketplace. Pointing a board at a repository is a team decision made on the board.

Where to find itCopy Anchor Link

Administrators can also press ⌘K and type github, gitlab, forgejo or mcp to open the connection page directly.

GitHubCopy Anchor Link

Connect GitHub (administrator)Copy Anchor Link

1234

1. 1Setup progressCredential stored, installation chosen, webhook secret set, connection verified.
2. 2ConnectA GitHub App for a team, or a personal access token to try it out.
3. 3Creating the AppThe webhook URL and permissions to set when you create the App on GitHub.
4. 4App IDPaste the App ID here, then the private key and webhook secret below it.

1. Open System console → Marketplace → GitHub and switch the module on. Boards must be on too.
2. Under Connect, choose how this organisation authenticates:
   • A GitHub App — acts as itself and survives whoever set it up leaving. Recommended for a team. Follow Creating the App: set the webhook URL shown, give Issues read & write, Pull requests read, Metadata read and (for projects) Projects read & write, generate a private key and install the App on your GitHub organisation. Paste the App ID, private key and webhook secret.
   • A personal access token — the quickest way to try it; it stops working when its owner's access does.
3. Select Connect and test. If the App is installed in several places, choose the Installation.
4. Under Webhook, copy the address into GitHub with content type application/json and the same secret, and subscribe to issues, issue comments, pull requests, pull request reviews, projects v2 items and check suites. Recent deliveries shows whether GitHub reaches you.

The setup progress shows four steps: credential stored, installation chosen, webhook secret set, connection verified. For GitHub Enterprise Server, set the API and web address.

Credentials are encrypted at rest. If the panel says the installation cannot store credentials, the operator has to set ENCLESSA_SECRET_KEY and restart the API.

Link a boardCopy Anchor Link

1. Open the board and its configuration dialog, then the GitHub tab. You need manage boards in the board's team.
2. Choose a repository, a Projects v2 project, or both. A repository brings issues and pull requests; a project brings everything on it, including drafts.
3. Importing closed items is off by default, so a first sync of an old repository is not mostly history.

Linked items show their GitHub state on the card (open, draft, merged, review needed, checks). Without a webhook, boards change only when somebody selects Sync now.

Disconnecting GitHub unlinks every board; the items they imported stay.

GitLab & ForgejoCopy Anchor Link

Connect a forge (administrator)Copy Anchor Link

1234

1. 1AddressWhere your GitLab, Forgejo or Gitea answers.
2. 2Access tokenA token with API access to the repositories a board will mirror.
3. 3TestSigns in with the stored address and token and reports the account.
4. 4WebhookCopy this address into the forge’s webhook settings, with the same secret.

1. Open System console → Marketplace → GitLab & Forgejo, switch it on, and enter the host address and an access token in the module's settings.
2. Under Test the connection, select Test; it reports which account the token signs in as.
3. Copy the webhook address shown:
   • GitLab: Settings → Webhooks. Paste the address, put the webhook secret in Secret token, and tick Issues, Merge requests and Comments.
   • Forgejo or Gitea: Settings → Webhooks → Add webhook. Paste the address, set the same secret, content type application/json, and choose Issues and Pull requests with their comments.

Without a webhook, boards change on the next scheduled sync.

Mirror a repository on a boardCopy Anchor Link

1. Open the board's configuration dialog, GitLab & Forgejo tab, Mirror a repository.
2. Enter the repository (group/project on GitLab, owner/repo on Forgejo) and choose the direction: Read only, Write only or Both ways.
3. Choose what to import (issues, merge/pull requests, closed ones too), whether new cards are filed as issues, and where open items land. Select Link this board; the first sync starts.
4. Under Columns, mark which columns mean open and which mean closed. Moving a card into a closed column closes what it mirrors.
5. Sync now runs a sync at once; Unlink stops following the repository and keeps the imported items.

MCP (connected AI agents)Copy Anchor Link

Connect an agent (any user)Copy Anchor Link

1234

1. 1A connected agentThe agent acts as you and can only do what you can do.
2. 2End connectionDisconnects the agent at once.
3. 3What a connected agent may do as youNarrows the organisation’s settings for your own agents. It can only subtract.
4. 4Access tokensTokens for your own scripts.

1. In your agent, add an MCP server with your Enclessa installation's address followed by /mcp (for example https://enclessa.example.com/mcp).
2. The agent opens your browser; sign in and approve the connection. The agent now acts as you and can only do what you can do.
3. Changes it asks to make wait under Your account → Connected apps until you approve them, unless the tool is allowed to act without asking.
4. End connection there disconnects an agent at once.

Under the same pane, What a connected agent may do as you narrows the organisation's settings for your own agents. It can only subtract. Access tokens for scripts are next to it.

Set what agents may do (administrator)Copy Anchor Link

123

1. 1What each agent is shownChoose a connected agent to set which areas of the product it is offered.
2. 2Tools this agent is shownHow many tools the agent is offered, reading and changing.
3. 3An areaSwitch an area off to keep its tools off the agent’s list. The person loses nothing.

Open System console → Marketplace → MCP:

• What a connected agent may do — one row per tool, each set to Off (absent from the agent's list), Ask first or Without asking. Reading tools are On or Off. This can only narrow what the person could already do.
• What each agent is shown — per connected agent, which areas of the product it is offered. Hiding an area takes nothing away from the person; it only keeps the agent's tool list short.

Every agent action is audited under the person who connected it, marked as coming from MCP.

Roles and permissionsCopy Anchor Link

• Connecting GitHub or a forge and setting MCP policy needs a system administrator's console access.
• Linking a board needs manage boards in that board's team.
• Connecting an agent needs only an account; what the agent can do is bounded by your own permissions, the organisation's MCP policy and your personal narrowing.

TipsCopy Anchor Link

• Prefer a GitHub App over a personal token for anything beyond a trial.
• If GitHub boards are not updating, open Recent deliveries: an empty list usually means the webhook address or secret is wrong.
• A webhook address on localhost cannot be reached by a hosted forge; use Sync now or a tunnel during development.