Bibelstudium MCP vs Magic MCP
A side-by-side look at the Bibelstudium MCP and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bibelstudium MCP for spirituality & esoterica work; choose Magic MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bibelstudium MCP when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
Choose Magic MCP when
- You need dedicated capabilities in the Architecture & Design 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Spirituality & Esoterica | Architecture & Design |
| Quality signal | 32/100 · Emerging | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 6,217 |
| Directory activity | 3 views 0 installs 0 upvotes | 16 views 1 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bibelstudium MCP | View Magic MCP |
Tools & capabilities
Bibelstudium MCP tools
No tool names declared yet. Check the project README from the listing page.
Magic MCP 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.
Bibelstudium MCP
No confirmed install command for Bibelstudium MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}