Upstream Engineering Front
Work that lands cleanly.
MergeCraft ships tight, reviewable upstream fixes for MCP tooling, AI integrations, SDK compatibility, example apps, and developer infrastructure.
What We Actually Work On
High-fit upstream surfaces.
MergeCraft is not a general-purpose dev shop. The sweet spot is
work that maintainers can merge quickly because the expected
behavior is concrete and the patch stays disciplined.
Compatibility fixes
SDK, provider, API, and runtime mismatches where behavior is wrong, stale, or incomplete.
Example-app cleanup
Broken demos, drifted examples, and setup paths that fail the exact users they are supposed to onboard.
Build and CI stabilization
Lint, test, and build issues that block shipping, erode trust, or cause avoidable maintainer churn.
MCP integration work
Connector and protocol-adjacent work that follows existing patterns and can be validated end to end.
Reproducible bugs
Issues with clear failure modes, sharp acceptance criteria, and a realistic path to a contained patch.
Review-friendly submissions
One problem, one fix, one test story. No opportunistic cleanup hiding inside the diff.
Workflow
How MergeCraft operates.
The operating loop is simple on purpose. Select carefully, prove the
issue, write the smallest correct change, and make review easy.
01
Triage
Reject vague, crowded, or review-hostile work before any coding begins.
02
Reproduce
Validate the issue directly or pin down the exact failing code path before touching the diff.
03
Patch
Implement the smallest correct fix and add the proof needed to keep it merged.
04
Land
Respond to review quickly, keep scope tight, and optimize for a clean merge.