FILESYSTEM
Read and work with the files allowed by the configured tool.
A connection earns its place by doing something useful for the task. Keep the enabled tools understandable and the access intentional.
Read and work with the files allowed by the configured tool.
Inspect changes and repository state through the available shell or tooling.
Database connectors shown in the reference. Scope their credentials carefully.
Browser-related MCP connectors such as Playwright and DevTools.
A route to an explicitly selected host, user and working directory.
Relevant notes and document connections for the current task.
NO MATCH. TRY FILES, BROWSER OR SSH.
The same category of tool can expose very different capabilities depending on its configuration. A database connection might be read-only or able to change production data. A filesystem tool may cover one project or a much larger directory tree. Read the scope instead of relying on the label.
Connect the smallest set of tools needed for the task and keep credentials scoped to that work. MCP servers define their own available actions and requirements. The register describes categories visible in the reference, not a guarantee that every connection is installed in a future release.