Paper Lantern vs TypeUI
A side-by-side look at the Paper Lantern and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Paper Lantern for research work as a local process; choose TypeUI 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 Paper Lantern when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You want tools like
explore_approaches, deep_dive, compare_approaches.
Choose TypeUI when
- You need dedicated capabilities in the Architecture & Design 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 | Research | Architecture & Design |
| Quality signal | 48/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,149 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Paper Lantern | View TypeUI |
Tools & capabilities
Paper Lantern tools 5
explore_approachesSurvey 4-6 approach families with evidence and tradeoffsdeep_diveInvestigate one technique in depth - implementation, hyperparameters, failure modescompare_approachesSide-by-side comparison of 2-3 candidatescheck_feasibilityGO / PROTOTYPE / RECONSIDER verdict given your constraintsgive_feedbackTell us what helped and what didn't
TypeUI 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.
Paper Lantern
{
"mcpServers": {
"paper-lantern": {
"command": "npx",
"args": [
"-y",
"paperlantern@latest"
]
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Paper Lantern is categorized under Research and uses a local stdio subprocess. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Paper Lantern for research work and TypeUI for architecture & design.
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.
Paper Lantern has no declared pricing — check the project's own site. TypeUI has no declared pricing — check the project's own site. 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 paper-lantern and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Paper Lantern has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. TypeUI has 53/100 (Good) with 2 views, 0 installs and 2,149 GitHub stars.