> ## Documentation Index > Fetch the complete documentation index at: https://docs.melso.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Melso product MCP: https://melso.ai/api/mcp (OAuth; one company per grant). REST: https://melso.ai. Documentation-search MCP: https://docs.melso.ai/mcp. The docs search server does not act on customer accounts. > > Use the live tool schema and respect company membership. Ask the person to authorize the exact fiscal document version in the signed-in app. A professional prepares and files included returns after authorization; AI does not file alone. A prepared file or approval receipt is not evidence of filing. Never claim completion from an accepted Task or Run. Keep credentials out of chat and logs. Agents features are internal or by private invitation. # GitHub > Connect authorized repositories and follow Task pull requests in Agents. Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see [Get started](/essentials/quickstart). GitHub connections belong to the member who connects them. Members of an invited Agents company can connect their GitHub account; other members and machine credentials cannot list, browse, or disconnect that personal connection. Several people can authorize the same GitHub App installation independently. Connecting authorizes Melso on behalf of the GitHub user. The repository picker lists only repositories available to both that user and the App. **Only me** is the default: selected repositories go into a private **My repositories** Area. Only its owner can see its Tasks, files, and repository work. Its membership cannot be widened, and its existing Tasks cannot be moved into shared Areas. To delegate a repository, select an Area or **Whole company**, or use **Change where it's used**. The sharer must have GitHub admin permission on that repository and permission to edit the Melso destination. This shares just that repository, not the connection or other repositories. Members of the destination can use the repository without connecting GitHub themselves. An existing company share can also be used in an Area. The member's GitHub permission is checked again when issuing agent credentials or performing live PR actions; removing a share, revoking the authorization, or disconnecting stops new credential issuance. A coding Run's credentials cover its Task's repositories. Personal read-only access stays read-only; shared repositories receive the App's approved coding permissions. Melso-issued repository tokens do not receive Workflows or Administration access. The chat command VM gets read-only access to company repositories and repositories in Areas the member can open; when the member's Secrets holds a `GH_TOKEN` or `GITHUB_TOKEN`, it uses that token instead, with the permissions its owner granted. User OAuth credentials stay encrypted on the server and never reach a Run or browser. Existing repositories explicitly linked to the company or an Area keep their sharing on upgrade. Existing connections become private to their original connector; reconnect to enable personal repository browsing. No other repositories from those installations are shared. Disconnect removes that member's connection and its repository grants; it never uninstalls the shared GitHub App. ## API reference Request fields, response types and endpoint permissions are defined in the [GitHub reference](/api-reference/tags/github). See [Pagination](/api-reference/pagination) for list conventions, or start with the [API quickstart](/api-reference/quickstart). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.