Skip to content

TS cassette converter between our formats? #14

@KryptosAI

Description

@KryptosAI

I built mcp-observatory and noticed TS cassette support + diffing are on your roadmap.

Our formats look close enough that a converter should be pretty small. You group request/response into interaction objects and keep HTTP metadata around, we store flat entries with a direction field. Feels like maybe ~50 lines to map between them.

Main use case is recording with your proxy, then replaying or diffing in Observatory without re-recording.

Would you want that as a PR here, or does it make more sense as a standalone package?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions