MCP server · Dokki

dokki-one-mcp.yml

Dokki operates hosted, remote MCP servers on its primary domain. The canonical endpoint is the /mcp/v2 FACADE: eight high-level tools (find, read, create, edit, share, message, publish, connect) plus preview_resource, each taking an `action` + top-level ids + `args`, over stateless Streamable HTTP. The legacy flat server at /api/mcp exposes "~37" individual tools (names not published) and per-Org paths /api/mcp/org/ remain as compatibility routes. Workspace Connectors reuse /mcp/v2 (Documents flavor), /api/publish-mcp (Publish) and /api/mem-mcp (Memory) with a fixed workspace id, connector id and one-time token in the generated URL. Both public endpoints return 401 to an anonymous tools/list, so input schemas below are the provider's published action vocabulary, not introspected JSON Schema.

Open endpoint → Dokki 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: Dokki Type: Hosted endpoint Transport: streamable-http Host: dokki.one

Endpoint

https://dokki.one/mcp/v2

Hosted endpoint · transport streamable-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": { "dokki-one": { "url": "https://dokki.one/mcp/v2" } } }

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

# Add to claude_desktop_config.json { "mcpServers": { "dokki-one": { "command": "npx", "args": ["-y", "mcp-remote", "https://dokki.one/mcp/v2"] } } }

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://dokki.one/mcp/v2 \ -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.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this
  • find_mcpBrowse and filter every MCP server in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This MCP server 
curl "https://apis.io/api/v1/mcp/dokki-one-mcp-yml"
All mcp servers 
curl "https://apis.io/api/v1/mcp?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.