Getting Started
MergeSafe is a manual WebMCP tool creation and operations platform. Teams create project-scoped tools, attach explicit HTTP or Hook bindings, publish signed pack artifacts, and then load the active version into a browser runtime or SDK.
What MergeSafe helps you do
MergeSafe is designed for teams that already own a working product surface and want to expose carefully defined tool behavior through WebMCP. The platform is centered on manual tool creation rather than scanner-first discovery or automatic workflow recording.
In practice, that means you describe the tool you want, define input and output schemas, connect the tool to a real execution path, publish a versioned pack, and then monitor runtime behavior after launch.
What you should have before you start
- A clear product area you want to expose as a tool, including the user action or response you expect.
- A project in MergeSafe, since projects are the top-level boundary for domains, tools, versions, analytics, and health.
- One or more allowed domains for the project so runtime access can be checked against the project allowlist.
- A decision about whether the execution path should be request-driven through HTTP or product-local through a Hook binding.
- Schema intent for the tool so you can describe the input and output shape before publishing.
Domain language stays qualified
Docs should describe domains as origin allowlist entries. The current product truth does not support stronger ownership-verification claims such as DNS proof or TXT challenge flow.
Typical high-level flow
- 1
Create a project
Projects hold the project key, domains, tools, pack versions, analytics, and health data for one product surface.
- 2
Add one or more domains
Domains act as allowlist entries for origin-based runtime access decisions. Multiple domains per project are supported.
- 3
Create a tool and define schemas
Choose a user-facing tool contract, then define the expected input and output shapes before you wire execution.
- 4
Choose a binding
Use HTTP when the tool should call an existing route or API-backed action. Use Hook when the tool should run through an explicit product-side callable path.
- 5
Publish a pack
Publishing compiles eligible tools, signs the artifact, creates a new version, and makes that version active.
- 6
Load the runtime and monitor operations
The frontend snippet and SDK load the active version, fetch the artifact, verify the signature, register eligible tools, and report telemetry that feeds analytics and tool health.
What to read next
- Use Projects, Domains, and Multiple Domains before you document rollout boundaries for a real product surface.
- Use Creating a Tool, HTTP Bindings, and Hook Bindings once you are shaping the first callable behavior.
- Use Frontend Snippet, SDK and Bootstrap, and Latest Pack Fetch and Runtime Delivery when you are wiring the live runtime.
- Use Tool Health, Analytics, and Verification plus Troubleshooting and Known Ambiguity when you move from launch into operations.