Packkit vs Typeship
A side-by-side look at the Packkit and Typeship MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Packkit for developer tools work as a local process; choose Typeship for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Packkit when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Typeship when
- You need dedicated capabilities in the Developer Tools domain.
- You have the keys it needs:
TYPESHIP_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 44/100 · Fair | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TYPESHIP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Packkit | View Typeship |
Tools & capabilities
Packkit tools
No tool names declared yet. Check the project README from the listing page.
Typeship 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.
Packkit
{
"mcpServers": {
"packkit-2": {
"command": "npx",
"args": [
"-y",
"create-packkit"
]
}
}
}
Typeship
No confirmed install command for Typeship yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Packkit is categorized under Developer Tools and uses a local stdio subprocess. Typeship belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Packkit for developer tools work and Typeship 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.
Packkit has no declared pricing — check the project's own site. Typeship has no declared pricing — check the project's own site. 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 packkit-2 and typeship as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Packkit has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Typeship has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
