MCP
MCP terminology and the limits of generic tool connections.
Model Context Protocol (MCP) describes how a client can use tools exposed by a server. It doesn’t establish which tools the application supports.
| Connection | Available setup |
|---|---|
| GitHub Apps | Forge and Lens App installation in Integrations. |
| Generic MCP server | Unavailable. |
| Generic API key | Unavailable. |
Available setup
There is no generic MCP server form in Integrations. You cannot add an arbitrary server URL, paste its credentials or select its permission scopes there. GitHub installation uses GitHub Apps and the GitHub API; it doesn’t use an MCP connection form.
Permissions and records
Installing a GitHub App doesn’t authorise a separate MCP server. A link to a document or issue doesn’t give an agent access to its source. The named provider’s availability determines which reads, writes or synchronisation it supports.
The protocol alone doesn’t determine who holds the authoritative record or whether the application stores a copy. Those behaviours depend on the supported connector. The GitHub reference describes the available provider.