Agent integrations, without inflated claims

Use Corresync where your agent runs. See exactly how it is packaged.

Corresync connects to local AI agents over stdio. This matrix separates direct MCP setup, Skills, native packages, source availability, and actual marketplace publication—so a compatible client is never mistaken for an official listing.

Version snapshot

Three versions, three different facts.

The source bundle can be ahead of the latest stable release, while an external registry can still show an older verified record. They are displayed separately on purpose.

Source bundle
0.9.0-rc.1
Latest stable release
0.8.6
MCP Registry observed
0.8.6

Publication matrix

What is available now—and where.

Every working integration below is local. “Source available” means the reviewed package is in this repository; it does not mean the upstream vendor lists or endorses it.

Read the labels literally

Compatibility, packaging, and publication are separate.

Source available

Source available

A versioned native package is generated and tested in this repository. An official vendor directory has not been claimed.

Not listed

Not listed

Use corr setup for the reviewed direct MCP path. Marketplace submission waits for native metadata and upstream review.

Local means local

No hosted agent or private tunnel is enabled by a listing.

Corresync exposes one local stdio server and local account state. Hosted ChatGPT, cloud agents, Kiro Web, and remote sandboxes cannot reach it merely because a plugin format exists.

A hosted relay or private MCP tunnel would introduce a new data path and requires its own architecture decision, consent, privacy disclosure, revocation design, and security review.

The shortest path

Let corr setup detect and connect the agents on this machine.

The matrix is reference material. The guided command remains the natural starting point and only offers reviewed local paths.