Raw MCP server

Use this route when you already have a remote server that speaks MCP, the standard that lets AI tools communicate. DorkOS verifies the configured server and keeps one connection for it.

Raw MCP is an alpha inventory route. DorkOS verifies the real MCP handshake and tool list, but it does not grant those unversioned tools to agents.

What DorkOS verifies

DorkOS opens the configured endpoint, performs an MCP initialization, and requests the server's tool list. It records the connection only after both steps succeed. This proves that the endpoint speaks MCP; it does not prove an authenticated user session. A timeout, changed setup, cancelled flow, or failed probe creates no connection.

The pending check is stored by DorkOS. Restarting the server does not make DorkOS guess from a URL or an in-memory handle. It resumes only the exact owner, configured route, generation, request, and unexpired private flow. DorkOS checks that authority again after the network probe before it records success.

What this route does not do

This route does not start OAuth. Its public configuration has no field for an authentication secret or custom header. The endpoint must accept DorkOS's MCP initialization and tool-list requests with those four settings alone. A service that needs DorkOS to obtain or provide a login cannot use this route.

It also does not expose the remote server or its tools to an agent. A generic MCP tool list does not provide the immutable versions and safe classifications required for exact owner-reviewed access. Use Composio when you need agent actions now.

Configure one server

Add the server to your config

Edit ~/.dork/config.json and add an entry under connectors.rawMcpServers:

{
  "connectors": {
    "rawMcpServers": [
      {
        "slug": "notion",
        "displayName": "Notion",
        "url": "https://mcp.notion.example/mcp",
        "transport": "http"
      }
    ]
  }
}

Check each field

slug is the stable service name. Use lowercase letters, numbers, and hyphens.
displayName is the label shown in Connections.
url is the exact remote server URL.
transport is http for Streamable HTTP or sse for an older server-sent events endpoint.

DorkOS reads this list at startup. Restart it after adding, removing, or changing an entry.

Verify the connection

Open Connections, choose the configured service, and select Connect. This flow has no sign-in URL. DorkOS polls the stored check, performs the MCP probe, and adds the connection only when the configured server responds correctly.

One account per configured server

Each raw MCP entry represents at most one account. Disconnecting it cancels pending checks for that exact service. Other configured services continue independently.

DorkOS does not obtain an OAuth token for this route. The URL is stored as written in your local config.json, without encryption. Avoid putting secrets in it.

DorkOS leaves the whole URL out of configuration snapshots returned by its tools and API, because URLs can contain credentials. The service name, label, and transport remain visible. This does not remove the URL from your local config file.

Raw MCP server

On this page