Made from your own words
Little tools, kept for you.
Ask any connected assistant for a small tool. Ship It checks the build, reads it back, and keeps the records under your account.
Make your first tool.
Start with one small thing to remember, list, count or choose. Creating a tool needs your own Google and GitLab accounts, an assistant that supports custom MCP connections, and access to a prepared public GitLab project with Duo and CI. Ship It sign-in does not grant GitLab access.
- Sign in. Use your own Google account for your tools and records.
- Connect your assistant. Add Ship It Builder, then connect your own GitLab account in the assistant that will build. Other assistants need only Ship It Builder to use your finished tools.
- Ask for one small job. Copy a starting prompt below. Your assistant checks build access, asks a few short questions and waits for your approval before preparing it.
Use your own prepared GitLab project
Optional. If you cannot build in the default project, use a public project with the matching Ship It build kit, working CI and your own Duo Developer access. A fork alone does not establish those requirements. Project setup
Use the numeric ID shown on your project's GitLab overview page. This only changes the prompt; it does not grant access.
Your request and examples will be public on GitLab. Keep them generic; save private records only after the tool is live. The assistant will read back the checked tool for your approval.
Evaluating Ship It? Start with the judge guide and public evidence. No sign-in is needed to inspect the Duo builds and CI; creating your own tool needs the access above.
Assistant connections use eight-hour sessions. If your assistant asks you to reconnect, sign in with the same Google account and review its access again. Your tools and saved records remain in place.
Checking your session…
Your tools, your records
Sign in to see your tools.
Your personal tools stay private. A shared list is visible only to its owner and people who accept an invitation. Assistants you authorize use the same records; the service operator can access stored data.
Use a Google account with a verified email address.
My tools
You have no live tools yet. Ask a connected assistant to make one; it starts with a few short questions.
Prepared in GitLab
Builds
No builds yet.
The same tools, any assistant
Connect an assistant.
Ship It Builder
Your assistant can find your tools, read them, and change records with the permissions you approve. When a new tool goes live, ask your assistant to list your tools.
Set up in ClaudeCustom connector support depends on your client, plan, and settings. Connecting from this page does not install or authorize a client automatically.
Use the name Ship It Builder when adding this server in another assistant.
Your connections
Sign in to review and revoke your assistant connections.
Your records stay with your tools.
Ship It stores your verified account identity, your tool requests, the approved tool definitions and their records. Google sign-in does not give it access to your Google files. A tool request is posted publicly on GitLab so GitLab Duo can build it; records are never posted there.
Owners can export a tool’s definition and records as JSON. Shared lists show each contributor’s verified email; the owner can manage invitations and remove access from the tool’s Share panel. Assistant permissions can be revoked above. Signing out ends this browser session and assistant connections authorized from it.