by dock-ai
Dock AI: Resolve business domains to discover MCP endpoints for real-world entities quickly and securely.
Discovers MCP servers that can interact with specific businesses by looking up their domains in a registry.
Dock AI is an official MCP server published by dock-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. Dock AI: Resolve business domains to discover MCP endpoints for real-world entities quickly and securely. It is categorized under developer tools.
You can install Dock AI in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
Dock AI is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
According to our notes, Dock AI benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Dock AI reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Dock AI is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Dock AI reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Dock AI has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Dock AI has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Dock AI for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Dock AI surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Dock AI benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Dock AI reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 75
MCP server for Dock AI - discover MCP endpoints for real-world entities.
Dock AI is a registry that maps businesses to their MCP connectors. This MCP server allows AI agents to discover which MCP servers can interact with a given entity (restaurant, hotel, salon, etc.) by querying the Dock AI registry.
Use the hosted version at https://connect.dockai.co/mcp - no installation required.
{
"mcpServers": {
"dock-ai": {
"url": "https://connect.dockai.co/mcp"
}
}
}
# Using uvx
uvx dock-ai-mcp
# Or install and run
pip install dock-ai-mcp
dock-ai-mcp
The server starts on http://0.0.0.0:8080/mcp.
resolve_domainCheck if an MCP connector exists for a business domain.
Input:
domain (string): The business domain to resolve (e.g., "example-restaurant.com")Output:
{
"domain": "example-restaurant.com",
"entities": [
{
"name": "Example Restaurant",
"path": null,
"location": { "city": "Paris", "country": "FR" },
"mcps": [
{
"provider": "booking-provider",
"endpoint": "https://mcp.booking-provider.com",
"entity_id": "entity-123",
"capabilities": ["reservations", "availability"],
"verification": { "level": 2, "method": "dual_attestation" }
}
]
}
],
"claude_desktop_config": {
"mcpServers": {
"booking-provider": { "url": "https://mcp.booking-provider.com/mcp" }
}
}
}
User: "Book a table at Gloria Osteria Paris"
Agent: [searches web for "Gloria Osteria Paris official website"]
-> Finds domain: gloria-osteria.com
[calls resolve_domain("gloria-osteria.com")]
-> Gets MCP endpoint for SevenRooms
-> Connects to the MCP server
-> Books the table
User: "I need a room at The Hoxton in London"
Agent: [searches web for "The Hoxton London website"]
-> Finds domain: thehoxton.com
[calls resolve_domain("thehoxton.com")]
-> Gets MCP endpoints for available booking providers
-> Uses the MCP to check availability and book
User: "Book at Le Paris Paris restaurant"
Agent: [calls resolve_domain("leparisparis.fr")]
-> Response shows pending_providers: [{ "provider": "thefork", ... }]
-> Informs user: "This restaurant uses TheFork for reservations,
but TheFork hasn't published an MCP connector yet.
You can book directly on TheFork's website."
This MCP server queries the Dock AI registry API to resolve domains. No user data is collected or stored. See our Privacy Policy.
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.