TatNet — website deployment vs Lizard MCP
A side-by-side look at the TatNet — website deployment and Lizard MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TatNet — website deploymentCloud Platforms · Remote HTTP/SSEDeploy static and SSR websites via AI; manage Git/Docker apps, builds, logs and domains on TatNet.40FairAuth: not declaredVerdict: choose TatNet — website deployment for cloud platforms work over a hosted endpoint; choose Lizard MCP for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose TatNet — website deployment when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
Choose Lizard MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
PORT, PUBLIC_URL, PLATFORM_URL, LIZARD_TOKEN, LIZARD_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TatNet — website deployment | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 40/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PORTPUBLIC_URLPLATFORM_URLLIZARD_TOKENLIZARD_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TatNet — website deployment | View Lizard MCP |
Tools & capabilities
TatNet — website deployment tools
No tool names declared yet. Check the project README from the listing page.
Lizard 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.
TatNet — website deployment
{
"mcpServers": {
"tatnet-website-deployment": {
"url": "https://mcp.tatnet.cloud/mcp"
}
}
}
Lizard MCP
{
"mcpServers": {
"lizard-build-lizard-mcp": {
"url": "https://employ-woman-g1q2.us-east-1.onlizard.com/mcp"
}
}
}
Frequently asked questions
TatNet — website deployment is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Lizard MCP belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick TatNet — website deployment for cloud platforms work and Lizard MCP for cloud platforms.
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.
TatNet — website deployment has no declared pricing — check the project's own site. Lizard MCP 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 tatnet-website-deployment and lizard-build-lizard-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TatNet — website deployment has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Lizard MCP has 51/100 (Good) with 0 views, 0 installs and 3 GitHub stars.