{"id":"ai.letsship/ship","slug":"ai-letsship-ship","title":"SHIP","description":"Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.","version":"0.24.0","publisher":{"kind":"domain","id":"letsship.ai","label":"letsship.ai","url":"https://letsship.ai"},"website":"https://letsship.ai/docs/mcp","repository":"https://github.com/letsship/mcp","remotes":[{"type":"streamable-http","url":"https://mcp.letsship.ai/mcp","headers":[{"description":"A SHIP personal access token, sent as a bearer token. Create one at https://letsship.ai/settings/tokens. Leave it out to sign in with OAuth instead.","value":"Bearer {token}","isSecret":true,"variables":{"token":{"description":"The token value. It starts with pat_.","isRequired":true,"isSecret":true,"placeholder":"pat_..."}},"name":"Authorization"}]}],"packages":[],"published":"2026-10-12","updated":"2026-10-12","status":"online","auth":"","latency_ms":1044,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"healthz","title":"API health probe","description":"Returns the upstream API status, environment, and version.","read_only":true},{"name":"whoami","title":"Identify the calling principal","description":"Returns the caller's identity, org, role, role-derived RBAC capabilities, and token scopes. Use this to check whether the current token may perform an action (e.g. config:write) before attempting it.","read_only":true},{"name":"get_setup_progress","title":"Get setup progress","description":"Read what the workspace has set up with SHIP so far, as the console's setup checklist shows it: up to 13 milestones in three groups, taken in order (get started, make it yours, make it autonomous). `activeGroup` names the group to work on now, and each group carries its own count. Each milestone says whether it is reached and, when a console page takes it and the caller's role can, the page that d","read_only":true},{"name":"get_billing","title":"Get workspace credits","description":"Read the workspace's credit balance by source and expiry, whether a new mission would start now, the per-mission credit ceiling, the project allowance and recent usage. Check it before dispatching work.","read_only":true},{"name":"list_billing_ledger","title":"List workspace credit ledger","description":"List where the workspace's credits went, newest first: one entry per mission (its start, each further 3 agent-hours, and messages charged before messages became free), per grant, per adjustment and per expiry. Pass nextCursor back as cursor for the next page. Owners and admins only.","read_only":true},{"name":"list_credit_offers","title":"List credit packs, the monthly plans and Enterprise","description":"List what SHIP sells: the credit packs (credits, the price in US dollars before tax, which checkout adds for the buyer's location, and the price per credit), the monthly plans under `team.plans` (Starter and Scale: each its credits a month, monthly price, price per credit, which credits added on top also cost, and agents at once), the range of credits a workspace on a plan can add at once, Enterpr","read_only":true},{"name":"start_credit_checkout","title":"Start buying credits or a monthly plan","description":"Opens a payment page and returns its URL. Nothing is charged until the buyer pays on that page. It sells one credit pack, a monthly plan (offer team, with teamPlan starter or scale, a subscription that renews until cancelled), or extra credits for a workspace already on a plan (offer team_credits, for quantity credits at that plan's own price per credit, paid once, expiring with the plan month). O","read_only":false},{"name":"update_team_subscription","title":"Change the monthly plan subscription","description":"Change the workspace's monthly plan subscription: plan switches between starter and scale from the next renewal on (nothing is charged or refunded for the current month; passing the current plan drops a waiting switch), or cancelAtPeriodEnd true ends it when the month already paid for ends, false resumes it before then. Pass at least one. Owners and admins only. The answer is the subscription as i","read_only":false},{"name":"request_more_credits","title":"Ask for more credits","description":"Ask for more credits for the workspace, saying what they are for. Any member may ask. The answer says who has the request: SHIP for a sponsored or Enterprise workspace, its owners and admins otherwise. A message sent while a request is open joins it.","read_only":false},{"name":"get_notices","title":"Get workspace notices","description":"Read what needs attention in the workspace, critical first: a tracker connection its vendor no longer accepts (missions cannot start or report back until someone reconnects it), or credits running out. Each notice has a stable id and kind, a message and, when the caller can act, an action URL to hand to a person. A notice the caller dismissed is left out. Check it before dispatching work.","read_only":true},{"name":"dismiss_notice","title":"Dismiss a workspace notice","description":"Close a notice for the person this token acts for, as the console's close button does. Only a notice with dismissible: true can be closed (a low balance). It stays closed while its id lasts: a low balance that a top-up ends and a later spend brings back has a new id and shows again. Critical notices cannot be closed.","read_only":false},{"name":"report_setup_blocker","title":"Report why setup stops","description":"Record why the person this token acts for will not finish setting up SHIP, in their words: for example no repository yet, no wish to set up model keys or credits, or no time now. Call it only after the person said why. Ask them when get_setup_progress shows setup is not done and they say they will stop. Do not guess a reason. Each call is a new report. A token that acts for no person is refused.","read_only":false},{"name":"mark_setup_step","title":"Mark a setup step","description":"Mark a step of the setup checklist completed or skipped for the person this token acts for, as the console's Mark as complete and Skip controls do; open removes the mark. Give step for one milestone, or group to mark every open step of that group (the console's Skip all). A marked step counts as done on that person's checklist and its status says how; reached stays false until SHIP sees the step d","read_only":false},{"name":"list_projects","title":"List projects","description":"List the projects accessible to the calling principal. Returns id, slug, name, status, createdAt for each. An empty list means the workspace is not set up yet: no mission can run until the person connects GitHub and a model key and creates a project in the SHIP console. Call get_setup_progress and give the person the console page of its next step.","read_only":true},{"name":"get_project","title":"Get project","description":"Fetch a single project by its UUID. Returns 404 if the project is not in the caller's org.","read_only":true},{"name":"update_project","title":"Change a project's settings","description":"Change the settings of one project; a field you leave out keeps its value. status paused or archived stops new missions in the project, and active starts them again. autoMerge sets whether SHIP merges a ready pull request by itself. defaultSandboxTemplateId sets the sandbox the agents start in (null for the platform base). repoFullName, linearTeamKey and jiraProjectId connect the project to anothe","read_only":false},{"name":"transfer_project_repository","title":"Transfer project repository","description":"Move the repository that SHIP made for a project with Start from scratch into the person's own empty GitHub repository, or name that repository for a transfer that waits on it. Only the repository moves. The hosted site, its waitlist, its database and SHIP's models, paid in credits, stay. SHIP archives its own copy and deletes it after a grace period. Only an owner of the workspace can do this, an","read_only":false},{"name":"get_project_transfer","title":"Get project transfer","description":"Read the transfer of a project's repository to the person's GitHub account: its state, what the person does next, where the repository goes, and when SHIP deletes its archived copy. This tool only reads: SHIP moves the transfer on by itself. The result gives the next step in action: choose_target means the person makes an empty repository on their own GitHub account, installs SHIP's GitHub App on ","read_only":true},{"name":"cancel_project_transfer","title":"Cancel project transfer","description":"Stop the transfer of a project's repository before the project uses the new repository. The project keeps SHIP's copy, and SHIP writes nothing more to the person's repository. Only an owner of the workspace can do this.","read_only":false},{"name":"start_mission","title":"Start a mission","description":"Hand a mission off to the AI agent team. Omit startAt for the default full run (planner first); pass startAt='builder' with a plan to skip straight to coding; pass startAt='reviewer' or startAt='qa' with an existing prNumber to hand off an existing build. Requires the missions:run token scope.","read_only":false},{"name":"create_mission","title":"Create a mission","description":"Create the tracker issue AND start the run in one call, for work that has no issue yet. Pass entryStartAt='builder' with an entryPlan to hand over a plan you already wrote; pass entryStartAt='reviewer'/'qa' with entryPrNumber to hand over an existing build — in which case title may be omitted and the pull request's own title names the mission. For the first mission of a SHIP Sites project, pass st","read_only":false},{"name":"set_agents_override","title":"Set a per-issue agents-override for one role","description":"Patch one role's harness/model/effort/prompt for a single mission, layered over ship.yml per-field (a role or field this call omits keeps resolving from ship.yml — SHIP-337). Use promptContent or promptPath(+promptRef) to run an ephemeral prompt experiment (spec D9) without committing to the target repo. Read-modify-write: this call is merged onto the previously stored override record (via get_age","read_only":false},{"name":"get_agents_override","title":"Read a mission's agents-override","description":"Read the per-issue agents/baseBranch override record for one mission, or null when unset.","read_only":true},{"name":"send_mission_instruction","title":"Send a follow-up instruction to a mission","description":"Tell a mission what to change. Use kind='follow_up' (the default) to ask for a change: the instruction reaches the agents AND dispatches the builder against the mission's open pull request, overriding cached review and QA verdicts. Use kind='note' to record context for whatever runs next without starting any work. A restart is a different thing: it re-evaluates an unchanged pull request against it","read_only":false},{"name":"clear_agents_override","title":"Clear a mission's agents-override","description":"Delete the per-issue agents/baseBranch override — the mission resolves from ship.yml again.","read_only":false},{"name":"list_missions","title":"List missions","description":"List missions in the caller's accessible projects, newest activity first, with total for paging. Each has issueId, title, activity (what it does now), pipelineProgress, review/check/test state, PR, cost and paused. Archived missions are left out. Requires the missions:read scope.","read_only":true},{"name":"get_mission","title":"Get mission detail","description":"Fetch one mission. view='summary' (the default, small enough to poll) returns its summary (activity, stage, review/check/test state, PR, paused and pauseSource, cost), its agent runs (sandboxId, role, status, harness, model, cost) and proofRunSandboxId (pass it to list_artifacts as sandboxId for the proof). view='full' adds its stages, events, stats and the plan/review/QA outcomes. pauseSource 'ch","read_only":true},{"name":"pause_mission","title":"Pause a mission","description":"Hold a mission before its next stage. The stage that runs now finishes; no agent is stopped. Use resume_mission to continue. Requires the missions:write scope and a role that can control missions.","read_only":false},{"name":"resume_mission","title":"Resume a mission","description":"Continue a paused mission. When a checkpoint holds it (get_mission shows pauseSource 'checkpoint:<role>'), this approves that stage's result and starts the next stage. To ask for changes to the result instead, use send_mission_instruction. Requires the missions:write scope.","read_only":false},{"name":"stop_mission","title":"Stop a mission","description":"Hard-stop a mission: every agent run of it stops and its work in progress is lost. The pull request stays open, and start_mission starts the mission again. To stop one agent run only, use stop_agent_run. Requires the missions:write scope.","read_only":false},{"name":"approve_mission_ceiling","title":"Let a mission continue past its credit limit","description":"A mission that reached its credit limit pauses until a member lets it continue. This raises the mission's limit by one step and runs the stage that stopped again, so it spends credits: ask the person first. Returns the new limit. Answers 409 when the mission is not at its limit. Requires the missions:run scope.","read_only":false},{"name":"answer_qa_checkpoint","title":"Answer the QA checkpoint of a mission","description":"A mission waits at the QA checkpoint (get_mission shows pauseSource 'qa-unverifiable') when QA could not check some acceptance criteria, so no code change can move it. A person checks those criteria another way, then answers. 'accept' counts QA as passed, 'reject' ends the mission as failed, and 'rerun' runs QA again on the same commit. Send only the decision the person made. Answers 409 when the ","read_only":false},{"name":"merge_mission","title":"Merge a mission's pull request","description":"Merge the mission's open pull request on GitHub with the repository's own merge method; the mission then becomes done, and the merge cannot be undone from here. When the branch is out of date with its base, answers 202 with status 'updating_branch' and a message: SHIP updates the branch and merges once CI passes, with no further call. Answers 409 with the reason for any other blocker (missing revi","read_only":false},{"name":"decline_mission","title":"Decline a mission's pull request","description":"Close the mission's open pull request on GitHub without merging it; the mission becomes declined, and no call here reopens it. Requires the missions:write scope.","read_only":false},{"name":"set_mission_auto_merge","title":"Turn auto-merge on or off for one mission","description":"Set whether SHIP merges this mission's pull request by itself once the checks, the review and the test pass. The setting is for this mission only and replaces the project's auto-merge for it; get_project shows the project's. While it is on, SHIP merges without asking again. Requires the missions:write scope.","read_only":false},{"name":"archive_mission","title":"Archive a mission","description":"Hide a finished mission from list_missions and the board. Nothing else changes: unarchive_mission shows it again. Requires the missions:write scope and the config:write capability (an owner or admin).","read_only":false},{"name":"unarchive_mission","title":"Unarchive a mission","description":"Show an archived mission in list_missions and on the board again. Requires the missions:write scope and the config:write capability.","read_only":false},{"name":"set_mission_disposition","title":"Record why a mission ended","description":"Record a person's reason for how a mission ended, which the delivery statistics use: product (real work, judged on its merits), probe (a test on purpose), superseded (another mission replaced it: give supersededBy) or takeover (a person finished the work outside SHIP); null clears it. Set it only with the person's answer, never from your own guess. Requires the missions:write scope and the config:","read_only":false},{"name":"list_scheduled_tasks","title":"List scheduled tasks","description":"List recurring agent missions (scheduled tasks) across the caller's accessible projects — schedule, enabled state, and next/last fire time for each. Pass projectId for the tasks of one project.","read_only":true},{"name":"list_scheduled_task_templates","title":"List scheduled task templates","description":"Read-only gallery of curated scheduled task templates — a prepared prompt plus a suggested cadence. A template is content, not a code path: pass its key as templateKey on create_scheduled_task for attribution, or copy its prompt/schedule into a hand-written scheduled task.","read_only":true},{"name":"get_scheduled_task","title":"Get scheduled task","description":"Fetch one scheduled task by id: its project, name, prompt, triggers (schedule), labels, template key, skip-if-previous-open setting, enabled state, and next/last run times. An id outside the caller's accessible projects returns not found. For what each fire produced, use list_scheduled_task_runs.","read_only":true},{"name":"create_scheduled_task","title":"Create a scheduled task","description":"Create a recurring agent mission. Firing it — on schedule, or immediately via run_scheduled_task — creates an ordinary tracker issue assigned to the agent, which drives a normal pipeline run: a scheduled task is a stored mission request, not a new execution mode. This tool calls the SHIP API, documented at https://letsship.ai/docs/api. Requires the config:write capability.","read_only":false},{"name":"update_scheduled_task","title":"Update a scheduled task","description":"Patch a scheduled task's name, prompt, schedule, skip-guard, or enabled state — only the fields passed are changed. To change the schedule, set interval/time/timezone together (plus weekday or dayOfMonth as the interval requires). This tool calls the SHIP API, documented at https://letsship.ai/docs/api. Requires the config:write capability.","read_only":false},{"name":"run_scheduled_task","title":"Run a scheduled task now","description":"Fire a scheduled task immediately, bypassing both its schedule and the skip-if-previous-open guard — an explicit run always creates a new issue even while a prior fire's mission is still open. Requires the pipeline:control capability and, for a token caller, the missions:run scope — the same authorization starting a mission by hand requires, because it is the same act.","read_only":false},{"name":"list_scheduled_task_runs","title":"List a scheduled task's run history","description":"Run history for one scheduled task, each row's status (dispatching/dispatched/skipped/failed) and, once its issue exists, the joined mission progress/cost. A 'dispatched' status means the issue was created and the mission started — never that the work succeeded; read the joined mission state for that. Newest first; when older runs exist, pass nextCursor back as cursor for the next page.","read_only":true},{"name":"delete_scheduled_task","title":"Delete a scheduled task","description":"Delete a scheduled task and its run history, which no call can bring back. Missions it already started continue. Setting enabled to false stops new runs and keeps the task and its history. Requires the scheduled-tasks:write scope and the config:write capability.","read_only":false},{"name":"list_mcp_servers","title":"List a project's MCP servers","description":"The MCP servers a project's repository declares in its MCP file (.mcp.json by default), each with its binding: enabled roles, transport, status, approved tools, per-role effective tool counts (null when the server runs inside the sandbox and the role gets every tool it exposes), and the NAMES of the credential fields set (never values). Also reports whether the file could be read (configStatus).","read_only":true},{"name":"list_mcp_bindings","title":"List the org's MCP bindings","description":"Every MCP server binding across the projects you can see in your org: project, server, transport, status, enabled roles, how it authenticates, and the NAMES of the credential fields set (never values). Use it to find where a credential is used; use list_mcp_servers for one project's full detail.","read_only":true},{"name":"set_mcp_config_path","title":"Set a project's MCP file path","description":"Point the project at the repository file that declares its MCP servers, e.g. .cursor/mcp.json or .vscode/mcp.json. null restores the default (.mcp.json). The file is read, never edited. When the repository's ship.yml sets mcp.config, that wins and this call is refused (409); list_mcp_servers reports which one applies as configPathSource. Requires the config:write capability.","read_only":false},{"name":"bind_mcp_server","title":"Bind an MCP server","description":"Create or update the binding for a server the repository declares. roles is the full set of pipeline roles that may use it (reviewer and qa only ever receive read-only tools, and cannot use a server that runs inside the sandbox). transport: 'remote' (the gateway proxies to the server's URL), 'isolate' (the gateway runs the server's npm package in isolation, for a command that needs a secret) or 'l","read_only":false},{"name":"unbind_mcp_server","title":"Remove an MCP server binding","description":"Delete a binding and its stored credential: no role receives the server from its next run. The repository's MCP file is not changed, so the server can be bound again. Requires config:write.","read_only":false},{"name":"refresh_mcp_server_tools","title":"Refresh an MCP server's tool list","description":"Snapshot the bound server's current tools (with their readOnlyHint / destructiveHint annotations) for approval. Approvals of tools that no longer exist are dropped. The binding must be ready; a server inside the sandbox has no gateway tool list. Requires config:write.","read_only":false},{"name":"start_mcp_server_oauth","title":"Start OAuth for a remote MCP server","description":"Begin the OAuth consent for a server bound as remote. Returns an authorizeUrl that a HUMAN must open in a browser signed in to the SHIP console as the same user this token acts for; the provider returns to the console, which stores the credential. The link is single-use and expires (expiresAt). An agent cannot complete the consent itself. Requires config:write.","read_only":false},{"name":"list_agent_runs","title":"List agent runs","description":"List the agent runs, live and finished, in the caller's accessible projects, newest first. Each run is one agent in its own sandbox. Returns id (the run's sandbox id), issueId, role, harness, status, instance type, and latest CPU/memory/disk metrics. When more runs match, nextCursor is set: pass it back as cursor, with the same filters, for the next page.","read_only":true},{"name":"get_agent_run","title":"Get agent run detail","description":"Fetch one agent run: its run record, metric series (CPU/mem/disk over time), and the agent session summaries (role, outcome, cost, sessionId). sessions lists every session of the run's role on the mission; runSessionId names this run's own, so read its log and cost from that one.","read_only":true},{"name":"get_agent_run_logs","title":"Get agent run logs","description":"Fetch a session's log content from one agent run. part=session is the agent stream-json (reasoning + tool calls); part=system is the container/runner stdout (clone, dependency install, validation gate, git, callback); part=prompt is the assembled input prompt. The role and sessionId are fields of the agent run's own record. A log longer than 40,000 characters returns its end, from a whole line, wi","read_only":true},{"name":"watch_agent_run","title":"Watch an agent run","description":"Wait on one agent run and follow what its agent does, instead of polling get_agent_run. The call returns when the run ends, when its mission moves to another stage, or after maxSeconds. While it waits, each agent event (a thought, a tool call, a plan update, an error) is sent as a progress notification when the request has a progress token. The result has the status of the run, the stage of its mi","read_only":true},{"name":"stop_agent_run","title":"Stop an agent run","description":"Stop the agent in one run before it finishes. Its work in progress is lost, and the run's status becomes stopped a few seconds later. Needs an org admin and the sandboxes:stop scope. This stops one agent run, not the mission: to stop the whole mission, use POST /v1/missions/{issueId}/stop.","read_only":false},{"name":"list_sandbox_templates","title":"List custom sandboxes","description":"List the org's sandboxes (definitions agents start in), with each one's active version, size and latest build status.","read_only":true},{"name":"get_sandbox_capacity","title":"Read how many agents are running","description":"How many agents the org's missions are running at once against its limit (null while the org is unclassified), which missions wait for an agent slot and why, and whether every slot on the platform is taken. Read from the platform's once-a-minute capacity check.","read_only":true},{"name":"list_sandbox_starters","title":"List sandbox starters","description":"Ready-made sandbox definitions (Python, Java, Go, Rust, Ruby) to create a sandbox from.","read_only":true},{"name":"list_sandbox_template_versions","title":"List a sandbox's versions","description":"Every saved version of a sandbox, newest first, with the active one marked and each one's latest build.","read_only":true},{"name":"get_sandbox_build_log","title":"Read a sandbox build's log","description":"A page of a build's log after sequence number `after`. Call again with after = nextAfter until done is true.","read_only":true},{"name":"save_sandbox_template","title":"Create or update a sandbox","description":"Create a sandbox (omit templateId) or change one. A definition is Dockerfile steps on the platform base (RUN, ENV, ARG, WORKDIR, USER; no FROM). A changed definition or size becomes a new version and is built at once; the response carries that build. Refusals name the line or the size bound.","read_only":false},{"name":"activate_sandbox_template_version","title":"Roll a sandbox back (or forward) to a version","description":"Make a version the one missions use from their next dispatch. It is rebuilt only if its snapshot is gone; the response says which.","read_only":false},{"name":"build_sandbox_template","title":"Build a sandbox now","description":"Build the sandbox's active version, or return the build already running for it.","read_only":false},{"name":"list_sandbox_registries","title":"List private registries","description":"The org's private package registries sandboxes install from: host, auth scheme, username. Never the secret.","read_only":true},{"name":"save_sandbox_registry","title":"Store a private registry credential","description":"Store (or replace) the credential for a registry host. The platform attaches it to sandbox requests for that host only; it never enters a sandbox and is never returned.","read_only":false},{"name":"delete_sandbox_template","title":"Delete a sandbox","description":"Delete a sandbox with all its versions and builds. Answers 409 while an agent or a project's default sandbox uses it: point those at another sandbox first (update_project with defaultSandboxTemplateId). Missions that run in it now finish. Requires the agents:write scope and the config:write capability.","read_only":false},{"name":"delete_sandbox_registry","title":"Remove a private registry credential","description":"Delete the stored credential of a private registry (an id from list_sandbox_registries). A sandbox build that installs from that host then gets no credential. Requires the connectors:write scope and the config:write capability.","read_only":false},{"name":"list_environments","title":"List preview environments","description":"List per-mission preview environments for the caller's accessible projects. Returns id, issueId, projectId, prNumber, workerName, and lifecycle status.","read_only":true},{"name":"get_environment","title":"Get preview environment detail","description":"Fetch one preview environment's registry row (status, worker name, timestamps).","read_only":true},{"name":"destroy_environment","title":"Destroy a preview environment","description":"Request teardown of a preview environment (its deployed Worker(s) + every provisioned datastore). Enqueues to the orchestrator; requires project write capability.","read_only":false},{"name":"list_site_templates","title":"List site templates","description":"List the templates that a SHIP-hosted site starts from: website, blog and docs. Each one names its public repository. Pass a template id as templateId to create_site.","read_only":true},{"name":"list_sites","title":"List sites","description":"List the sites that SHIP hosts for the organization, newest first: the address, the template, the status and the live deploy of each. A suspension whose end is in the past reads as active. When more sites exist, pass nextCursor back as cursor.","read_only":true},{"name":"get_site","title":"Get site","description":"Fetch one hosted site by id: its project, address, template, status, the end of a suspension, the badge rule, its live deploy and its newest deploy. For the deploy history, use list_site_deploys. For page views, use get_site_usage.","read_only":true},{"name":"list_site_deploys","title":"List site deploys","description":"List the production deploys of a site, newest first: the commit, the status, and for a deploy that did not go live, its cause and what to do. When older deploys exist, pass nextCursor back as cursor.","read_only":true},{"name":"get_site_usage","title":"Get site usage","description":"Read the page views of a hosted site for each UTC day, oldest first, with the monthly cap of the plan if it sets one, and the page views of the current month.","read_only":true},{"name":"create_site","title":"Create a site","description":"Create a SHIP-hosted site for a project and hold its address, https://<slug>.<sites domain>. The kind of the site comes from the template. Each project can hold one site, and the plan of the organization sets how many sites it can hold. A refused slug or a full plan comes back with the reason. This tool calls the SHIP API, documented at https://letsship.ai/docs/api. Requires the config:write capab","read_only":false},{"name":"update_site","title":"Change the badge setting of a site","description":"Set the \"Built with SHIP\" badge rule of a hosted site. With badge true, SHIP refuses a production deploy whose pages do not show the badge. With badge false, the site config decides. The change applies from the next production deploy. A plan that keeps the badge on refuses badge false, and the refusal says what to buy. Requires the config:write capability.","read_only":false}],"server_info":{"name":"ai.letsship/ship","title":"SHIP","version":"0.41.1"},"category":"project","tags":["agents","productivity","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-12","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/ai-letsship-ship/"}