Chatpack MCP vs No License Nearby
A side-by-side look at the Chatpack MCP and No License Nearby MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredN
No License NearbyDeveloper Tools · Local subprocess (stdio)Search 880+ artist-owned tracks and get sync licenses for social, TV and film.53GoodAuth: no auth requiredVerdict: choose Chatpack MCP for developer tools work as a local process; choose No License Nearby 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?
CChoose Chatpack MCP 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.
- You want tools like
search_docs, get_document, get_integration_guide.
NChoose No License Nearby 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.
- You have the keys it needs:
NOLICENSE_API_BASE. - You want tools like
search_tracks, get_track, get_preview_url.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Chatpack MCP | N No License Nearby |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | NOLICENSE_API_BASE |
| Verified owner | Verified | Community listing |
| GitHub stars | 224 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 6 |
| Full listing | View Chatpack MCP | View No License Nearby |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
No License Nearby tools 6
search_tracksSearch by title, genre, mood, energy and musical key (filters combine)get_trackDetails for one trackget_preview_urlAudition link for a tracklist_license_tiersLive prices: Social Media, TV + Streaming, Filmquote_licenseQuote for one or more tracks, including the multi-track discountget_license_checkout_linkThe license page pre-filled with the track, plus the steps to finish
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.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
No License Nearby
{
"mcpServers": {
"no-license-nearby": {
"command": "uvx",
"args": [
"nolicense-nearby-mcp"
],
"env": {
"NOLICENSE_API_BASE": "YOUR_NOLICENSE_API_BASE_HERE"
}
}
}
}
Frequently asked questions
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. No License Nearby belongs to Developer Tools and uses a local stdio subprocess. Pick Chatpack MCP for developer tools work and No License Nearby 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.
Chatpack MCP is listed as free. Auth: no auth required. No License Nearby 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 chatpack-mcp and no-license-nearby as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars. No License Nearby has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.