Magic MCP vs LienDeadline
A side-by-side look at the Magic MCP and LienDeadline MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LienDeadlineDeveloper Tools · Local subprocess (stdio)Statute-cited lien and notice deadlines for material suppliers; lien guides for 50 states and DC.52GoodAuth: not declaredVerdict: choose Magic MCP for developer tools work as a local process; choose LienDeadline 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 Magic MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
LChoose LienDeadline when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
calculate_supplier_deadlines, get_supplier_questions, calculate_supplier_deadlines_v3.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L LienDeadline | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
LienDeadline tools 7
calculate_supplier_deadlinesPreliminary notice and lien filing deadlines from delivery dates and yes, no or unknown event answersget_supplier_questionsWhether v3 covers a state, project type and hiring relationship, with its questions, sources and rule versionscalculate_supplier_deadlines_v3Deadlines from the facts gathered with `get_supplier_questionsget_state_lien_guideOne state's lien guide: rules, statute citations, deadline table and FAQslist_state_lien_guidesEvery guide (50 states and DC) with its code, title and slugcalculate_lien_deadlineInvoice-based deadlines (local server only)list_supported_statesJurisdictions the invoice calculation accepts (local server only)
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.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
LienDeadline
{
"mcpServers": {
"liendeadline": {
"command": "npx",
"args": [
"-y",
"liendeadline-mcp"
]
}
}
}
Frequently asked questions
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. LienDeadline belongs to Developer Tools and uses a local stdio subprocess. Pick Magic MCP for developer tools work and LienDeadline 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.
Magic MCP is listed as a paid service. Auth: api key required. LienDeadline 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 21st-dev-magic-mcp and liendeadline as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars. LienDeadline has 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars.