A pip install into a fresh venv will now install version 2.0.0 of the mcp package which might not be playing nicely with dsagt. In a Claude session I get:
"Blocker: the DSAgt registration tools this project's CLAUDE.md requires me to use — save_code_spec,
search_registry, get_registry, kb_remember, kb_get_memories, search_skills, kb_ingest — aren't actually
wired up in this session (checked via tool search, nothing matches). Without save_code_spec I have no way
to write these functions into the registry / trace_archive/ per the CLAUDE.md constraints, and per
constraint #1 I shouldn't fabricate CLI codes by hand-writing files as a substitute for that mechanism.
─────────────────────────
☐ Missing tooling
The DSAgt registry tools (save_code_spec, search_registry, etc.) aren't available in this session. How would
you like to proceed?
❯ 1. Connect the DSAgt MCP server
Pause here — you go set up/connect the MCP server or backend that exposes save_code_spec,
search_registry, kb_remember, etc., then we resume registration.
etc. etc."
There may have been some changes to the interface, leading to errors like "'Server' object has no attribute ‘list_tools'".
If I manually downgrade mcp back to 1.28.1 it all seems to work fine as before.
A pip install into a fresh venv will now install version 2.0.0 of the mcp package which might not be playing nicely with dsagt. In a Claude session I get:
"Blocker: the DSAgt registration tools this project's CLAUDE.md requires me to use — save_code_spec,
search_registry, get_registry, kb_remember, kb_get_memories, search_skills, kb_ingest — aren't actually
wired up in this session (checked via tool search, nothing matches). Without save_code_spec I have no way
to write these functions into the registry / trace_archive/ per the CLAUDE.md constraints, and per
constraint #1 I shouldn't fabricate CLI codes by hand-writing files as a substitute for that mechanism.
─────────────────────────
☐ Missing tooling
The DSAgt registry tools (save_code_spec, search_registry, etc.) aren't available in this session. How would
you like to proceed?
❯ 1. Connect the DSAgt MCP server
Pause here — you go set up/connect the MCP server or backend that exposes save_code_spec,
search_registry, kb_remember, etc., then we resume registration.
etc. etc."
There may have been some changes to the interface, leading to errors like "'Server' object has no attribute ‘list_tools'".
If I manually downgrade mcp back to 1.28.1 it all seems to work fine as before.