Cosync Local
Add CoSync local encryption and project setup to your agent so CoSync keys and credentials stay on your computer.
Overview
com.olane/cosync-local is a MCP server for the Ship phase that handles CoSync project setup and local encryption with keys that never leave your machine.
What is this MCP server?
- Stdio MCP via olane-cosync-local on PyPI (v0.2.0)
- CoSync project setup with encryption that never exports keys off-host
- Designed alongside cosync-remote for split local-secret vs hosted-graph architecture
- stdio transport for standard agent MCP registries
- Server version 0.2.0
- PyPI package olane-cosync-local with stdio transport
- Repository: github.com/olane-labs/cosync-local
What problem does it solve?
You are onboarding CoSync to an AI agent but cannot risk sending encryption keys or local secrets to a remote MCP endpoint.
Who is it for?
Builders standardizing on CoSync who need a stdio local MCP before enabling cosync-remote graph tools.
Skip if: Research-only workflows that only need remote entity search and CoSync scoring without local crypto.
What do I get? / Deliverables
CoSync projects are configured through MCP with encryption confined to your local environment.
- Stdio MCP registration for CoSync local encryption and setup
- CoSync workspace initialized with keys retained locally
- Foundation to add cosync-remote without exposing local key material
Recommended MCP Servers
Journey fit
How it compares
CoSync local encryption MCP, not the CoSync remote knowledge-graph service.
Common Questions / FAQ
Who is com.olane/cosync-local for?
Developers using CoSync with MCP-enabled agents who require on-device key handling and project bootstrap.
When should I use com.olane/cosync-local?
Use it at initial CoSync setup, when rotating local keys, or before shipping agent automation that reads encrypted CoSync data.
How do I add com.olane/cosync-local to my agent?
Install olane-cosync-local from PyPI (v0.2.0), configure it as a stdio MCP server in your client, and reload the agent.