A
licenseB
qualityC
maintenanceMCP server to publish HTML/Markdown docs, upload assets, and reply to stakeholder comments on uselink.app directly from AI tools like Claude and Cursor.
34
6 npm
MIT
mcp-lindoai
Officialby lindoai
Related Servers
Alternatives to mcp-lindoai
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP Server for Web2MD — convert webpage URLs to clean Markdown from Claude Desktop, Cursor, or any MCP-compatible agent.66 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Averra Extract — lets AI agents like Claude, Cursor, and ChatGPT convert any webpage into clean, LLM-ready Markdown.541 npmMIT
- AlicenseAqualityCmaintenanceVendor-agnostic MCP server that audits, scores, and rewrites web pages for AI-citation eligibility. No API keys. No registration. Works in Claude Desktop, Cursor, Cline, Windsurf, VS Code (Copilot / Continue), and any client that speaks the Model Context Protocol.2058 npm3MIT
- AlicenseAqualityAmaintenanceMCP server for VibeKit — build, deploy, and manage hosted apps and chat with each app's persistent server-side AI agent from Claude Desktop, Cursor, or any MCP client. Every app gets its own agent and a live URL; bring your own Claude/OpenAI key or pay-as-you-go.3634 npm1MIT
- AlicenseBqualityCmaintenanceMCP server for Contextium — pipe team SOPs, coding standards, agents, skills, and workflows directly into Claude, Cursor, and other AI coding assistants.67MIT
TDQS
B3/5.0
Scored across 50 tools
Disambiguation4/5
Tools are broadly separated by resource (workspace, client, website, page, blog) and action, and the async workflow/batch variants are clearly scoped. Minor ambiguity exists between create_blog (AI-generated) and publish_blog (static markdown), and get_credits vs get_client_credits requires reading descriptions to distinguish.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (list_websites, create_client, delete_page, unpublish_blog), with batch/check variants following the same convention. Small inconsistencies like get_workspace_team vs add_workspace_team_member and unprefixed get_credits vs get_client_credits keep it from a 5.
Tool Count1/5
At 50 tools, this is an extreme count for a single MCP server; even with a broad CMS scope, the agent surface is very large. Many workflow starters and their polling/batch counterparts inflate the surface and would be better grouped behind fewer tools or explicit sub-resources.
Completeness5/5
The surface covers nearly full lifecycles for workspaces, clients, websites, pages, and blogs, including CRUD, publishing, analytics, team management, credits, custom domains, and async workflows with batch status polling. No obvious dead ends or critical missing operations exist for the stated platform domain.
Maintenance
ActivityInactive
ResponsivenessNo issues