nextlevelbuilder / nextlevelbuilder/goclaw
CLI, MCP and client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 24
Description
there is seem to have a lack of awareness of activities in other repositories, such as https://github.com/nextlevelbuilder/goclaw-cli/pulls
but basically, I'm still maintaing it.
I'm also working on the MCP server, rewriting it completely in Golang instead of typescript.
And there is a real need to have an official goclaw-client repository. One that should actually be automatically updated with any agents whenever there is an API change on the server side.
And that client library could be use to connect the CLI and the MCP server to connect to goclaw.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the goclaw-cli pull requests and the current GoClaw API and MCP-server direction described in this issue. Clarify the scope and ownership of an official goclaw-client repository, then define how client updates should track server API changes and support both the CLI and MCP server. Done means the repository boundaries and update process are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- Domain
- api, backend-api-design, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100