
Cokodo Agent
io.github.dinwindPublished by GitHub account dinwindv1.7.0Updated Oct 24, 2026
Serve .agent/ project context, references, and collaborations to MCP-compatible IDEs.
Overview
A local MCP server that serves a project's .agent/ context, references and collaborations to MCP-compatible IDEs.
- What you can do
- Serve .agent/ project context to MCP-compatible IDEs, so an assistant can work from the project's own stored context rather than only the open files. Expose references held in the .agent/ directory for the assistant to draw on. Surface collaborations recorded in .agent/ so the assistant can take part in shared project work. No individual tools are listed, so the exact operations are not documented.
- When to use it
- Worth considering when a project keeps its context, references and collaboration notes in a .agent/ directory and you want an MCP-capable IDE assistant to read them. It is a narrow, project-local helper rather than a general-purpose server.
- Requirements
- Runs as a local process on the user's machine, installed from the cokodo-agent PyPI package, so a Python environment is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Cokodo Agent in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.7.0LatestSep 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.