Introduction

Workflow Context Protocol (WCP)

Today, due to the speed of technological advancement, there are more applications than ever — and many of them share the same capabilities, because there are countless providers solving the same problems.

WCP lets you connect those applications so you never have to switch to the tool someone else is using just to collaborate. You work in your app, they work in theirs — WCP keeps them in sync.

The Problem

Modern knowledge work is scattered: notes in Obsidian, tasks in Notion, spreadsheets in Google Sheets, docs in Confluence. Keeping them in sync means either:

• Doing it manually (slow, error-prone)
• Paying for a tool like Zapier (expensive, SaaS lock-in, no conflict resolution)
• Building point-to-point integrations (fragile, hard to maintain)

The WCP Solution

WCP introduces a protocol-level sync layer on top of MCP. Instead of integrating App A with App B, you register both as MCP connectors and let WCP handle the rest.

One sync run writes to all connected targets. Fan-out is built in.

Key Features

Feature	Description
MCP-native	Works with any app that has an MCP server
Fan-out sync	Write to N destinations in a single run
Conflict resolution	Automatic (last-write-wins / source-wins) or manual queue
Self-hosted	Your data never leaves your server
REST API	Full API for automation and integrations
Dashboard	React UI to manage connections, review conflicts, view logs
Open source	AGPL-3.0

License

WCP is released under the GNU AGPL v3.0.
Copyright © 2026 Lucas Mella.