
Dock AI
OfficialDiscovers MCP servers that can interact with specific businesses by looking up their domains in a registry.
Discover MCP endpoints for real-world entities by resolving business domains.
What it does
- Resolve business domains to find available MCP connectors
- Discover which services integrate with restaurants, hotels, and other businesses
- Get MCP server endpoints for real-world entities
- Retrieve business location and capability information
Best for
About Dock AI
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.
How to install
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.
License
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.
Dock AI MCP
MCP server for Dock AI - discover MCP endpoints for real-world entities.
What is this?
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.
Hosted Version
Use the hosted version at https://connect.dockai.co/mcp - no installation required.
{
"mcpServers": {
"dock-ai": {
"url": "https://connect.dockai.co/mcp"
}
}
}
Self-Hosting
Deploy to Vercel
Run locally
# 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.
Tools
resolve_domain
Check 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" }
}
}
}
Examples
Example 1: Restaurant Reservation
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
Example 2: Hotel Booking
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
Example 3: Business with No MCP Yet
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."
Support
- Documentation: dockai.co/docs
- Issues: GitHub Issues
- Email: [email protected]
Privacy
This MCP server queries the Dock AI registry API to resolve domains. No user data is collected or stored. See our Privacy Policy.
License
MIT
Alternatives
Related Skills
Browse all skillsUI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.