The GitHub Copilot coding agent uses a remote MCP URL plus static headers. It does not use Tindre’s OAuth flow, so create a dedicated personal access token for the account whose organizational access the repository should inherit.
- 1
Create the token
Mint a named personal access token under Settings → API & MCP.
- 2
Store a repository secret
Use a name beginning with COPILOT_MCP_, as required by the coding agent.
- 3
Add the MCP server
Configure the Tindre URL and reference the secret in the Authorization header.
- 4
Review the owner
Confirm that the token’s person has exactly the access the repository should use.
The repository inherits one person
A personal token acts as its owner. Do not choose an administrator merely because setup is easier; that silently gives the coding agent broader organizational access.
Protect the secret
Never commit the plaintext token. Set an expiry appropriate to the workflow and rotate before it lapses. Revoke immediately when the repository or owner no longer needs the connection.
Separate code access from Tindre access
Repository permissions and Tindre permissions are independent. A collaborator may trigger a coding workflow that uses the configured token, so review both systems’ boundaries together.
Copilot Chat in the editor
The same server address and bearer header work in Copilot Chat in VS Code: add an HTTP MCP server, set Authorization to Bearer followed by the token, and reload. Keep the header out of anything committed to a repository.
Start read-first
Validate capability discovery and reads before enabling a workflow that may propose or execute changes.