[06]UNCENSORED CODER / OPERATING NOTES

AI CODING TOOLCHAIN.
ACCESS WITH A PURPOSE.

A connection earns its place by doing something useful for the task. Keep the enabled tools understandable and the access intentional.

06 ENTRIES
01

FILESYSTEM

Read and work with the files allowed by the configured tool.

CONTEXTSETUP
02

GIT WORKFLOW

Inspect changes and repository state through the available shell or tooling.

CODESETUP
03

MYSQL / POSTGRES

Database connectors shown in the reference. Scope their credentials carefully.

DATASETUP
04

BROWSER TOOLING

Browser-related MCP connectors such as Playwright and DevTools.

WEBSETUP
05

SSH CONNECTION

A route to an explicitly selected host, user and working directory.

REMOTESETUP
06

MEMORY / DOCUMENTS

Relevant notes and document connections for the current task.

CONTEXTSETUP
CONFIGURATION IS PART OF THE WORK.

SEE WHAT
IS CONNECTED.

Reference connector list: inspect each connection before enabling its tools. Shared reference preview. Final product screens will differ.
THE PRACTICAL CONTEXT

Separate a tool name from the access it grants

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.

[NEXT]NO SINGLE MODEL OWNS YOUR PROCESS.

CONNECT WITH
A PURPOSE.

GET THE CODER