MCP server · Landing.ai

ade-docs

LandingAI publishes a hosted, remote MCP server for the ADE documentation surface. It is a streamable-HTTP MCP endpoint — a plain GET returns HTTP 405, which is the expected behavior for a POST-only MCP transport, confirming the endpoint is live.

Open endpoint → Landing.ai provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Landing.ai Type: Hosted endpoint Transport: http Host: docs.landing.ai

Endpoint

https://docs.landing.ai/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "landingai": { "url": "https://docs.landing.ai/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "landingai": { "command": "npx", "args": ["-y", "mcp-remote", "https://docs.landing.ai/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://docs.landing.ai/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.