agentleFS
wnkincwnkinc/claude-custom-connector-server/CLAUDE.md

claude-custom-connector-server

CLAUDE.md1 starsChanged 4 months agoMITView on GitHub

  • Reads credentials

The file

We found no rules to list in this file: it reads as prose or reference rather than instructions.

Files
CLAUDE.md

Layout

docker-compose.yml         # the stack: tools + guardrail + egress sidecars (local, auth off)
docker-compose.tunnel.yml  # public overlay: Cloudflare ingress routes + auth-on posture
env.example                # deployment identity (MCP_DOMAIN, TUNNEL_ID) -> cp to .env;
                           #   compose interpolates it into the tunnel overlay
security/                  # shared plumbing, imported by every tool
  serve.py                 #   serve(mcp, ...): env-selects transport + security posture, runs it
  auth.py                  #   Google OAuth provider (email allowlist, fail-closed)
  approval/                #   out-of-band human-in-the-loop approval gate + tool-mode authority
                           #     (per-tool always_allow/needs_approval/blocked; the gatekeeper tool
                           #     + in-chat manage_tools panel edit it — see docs/GATEKEEPER.md)
  egress-proxy/            #   squid egress allowlist (per-tool domains, default-deny)
  ingress/                 #   tunnel creds staging (gitignored; routing lives in the overlay)
  guardrail/service/       #   output-screen sidecar; GUARDRAIL_PROVIDER=llamafirewall|bedrock
                           #     (proves detection at startup: broken screen = unhealthy container)
  test_stack.py            #   stack-consistency validator (CI): the add-a-tool wiring rules
tools/                     # one tool per dir: server.py + Dockerfile + requirements.lock +
                           #   deploy.json. WHICH tools exist and what each is: the README's
                           #   "The tools" table (the deploy.json manifests are the machine source)
deploy/                    # cloudflare/ = shared ingress (tunnel+DNS, both paths);
                           #   aws/ = EC2 VM running this stack (reads the ingress stack)
scripts/new-tool.sh        # stamp a new tool (.claude/skills/new-tool = the decision procedure)
docs/                      # DEPLOY.md chooser -> deploy/{local,aws}.md runbooks; ARCHITECTURE.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.