Charlotte

io.github.wcharyszPublished by GitHub account wcharyszv1.0.8Updated Oct 24, 2026

Query, replay and rewrite your app's real HTTPS traffic, captured locally by Charlotte.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Charlotte exposes your app's locally captured HTTPS traffic to an assistant so it can query, replay and rewrite real requests and responses.

What you can do
  • Query captured HTTPS traffic from the local Charlotte proxy.
  • Replay recorded requests against the app.
  • Rewrite requests or responses to test variations.
  • Works over stdio as a local process on a desktop machine.
When to use it
Useful when debugging or testing an app's real network traffic and you want an assistant to inspect captured HTTPS exchanges, re-issue them, or try modified requests and responses instead of hand-editing a proxy tool.
Requirements
Runs as a local stdio process on a desktop machine; no web executable. Traffic must first be captured locally by Charlotte. No packages, environment variables, headers or authentication are declared in the manifest.
Before you install
It works on real captured HTTPS traffic, which can contain credentials, tokens, cookies and personal data; replaying or rewriting requests sends traffic to the app under test and may change server-side state. Review what is captured and shared with the assistant.

Installation

In SourceWeft

  1. Open Charlotte in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.8LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.