Skip to content

Handling MCP services as legacy while wiring and coding towards what makes this repo still relevant #37

@drQedwards

Description

@drQedwards

The Graph. Your Graphing of a context bloated repo at 99% accuracy can also yield token burning that is 50% less the competition (your $1600 competition becomes a $3200 competition ) and it would let you use Claude on a $20 subscription.

But first this requires looking at supermodeltools/cli and their MCP REPOS as I did in the dot Golang language.

.md skills are still relevant but the memory graph defines this specifically as a chain of both current and "being pruned" nodes that handle the concurrency gracefully and coherence prediction arithmetic
In the Kv slots so that it can handle "legacy" tools such as MCP without guardrailing to saying "x does not exist in the graph yet-- also no MCP server exists nor started yet because OpenAI said npx lunel-cli is cheating for the goblins" Persistently....

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions