Typeship vs Build
A side-by-side look at the Typeship and Build MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Typeship for developer tools work; choose Build for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Typeship when
- You need dedicated capabilities in the Developer Tools domain.
- You have the keys it needs:
TYPESHIP_TOKEN.
Choose Build when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 33/100 · Emerging | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | TYPESHIP_TOKEN | None listed |
| Verified owner | Community listing |
Tools & capabilities
Typeship tools
No tool names declared yet. Check the project README from the listing page.
Build tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Typeship
No confirmed install command for Typeship yet — follow the setup steps linked from its listing page rather than a guessed package name.
Build
{
"mcpServers": {
"build": {
"command": "npx",
"args": [
"-y",
"@paretools/init"
]
}
}
}
Frequently asked questions
Typeship is categorized under Developer Tools and uses an install path we have not confirmed yet. Build belongs to Developer Tools and uses a local stdio subprocess. Pick Typeship for developer tools work and Build for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Typeship has no confirmed install command yet — follow its own setup instructions.
Typeship has no declared pricing — check the project's own site. Build is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add typeship and build as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Typeship has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Build has 51/100 (Good) with 5 views, 0 installs and 139 GitHub stars.