Font Proof MCP vs TypeUI
A side-by-side look at the Font Proof MCP 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 Font Proof MCP for architecture & design 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 Font Proof MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FONT_PROOF_MCP_PATH. - You want tools like
create_proof, create_complete_proof, open_proof.
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 | Architecture & Design | Architecture & Design |
| Quality signal | 52/100 · Good | 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 | FONT_PROOF_MCP_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,149 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | Not listed |
| Full listing | View Font Proof MCP | View TypeUI |
Tools & capabilities
Font Proof MCP tools 17
create_proofcreate_complete_proofopen_proofget_proof_infoopen_in_appadd_sectionupdate_sectiondelete_sectionreorder_sectionsduplicate_sectionset_section_content_bulkupdate_section_settings- +5 more on the listing page
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.
Font Proof MCP
{
"mcpServers": {
"font-proof-mcp": {
"command": "npx",
"args": [
"-y",
"font-proof-mcp"
],
"env": {
"FONT_PROOF_MCP_PATH": "YOUR_FONT_PROOF_MCP_PATH_HERE"
}
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Font Proof MCP is categorized under Architecture & Design and uses a local stdio subprocess. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Font Proof MCP for architecture & design 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.
Font Proof MCP 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 font-proof-mcp and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Font Proof MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. TypeUI has 53/100 (Good) with 3 views, 0 installs and 2,149 GitHub stars.