# Raw MCP server
Source: https://dorkos.ai/docs/connections/raw-mcp

Point DorkOS at a remote tool server that manages its own sign-in





# Raw MCP server [#raw-mcp-server]

Some services run their own remote tool server that speaks MCP (the standard that lets AI tools talk to each other). If you already have one, you can point DorkOS straight at it. No middleman holds your login.

<Callout type="warn">
  This path is built but not yet confirmed end to end. It is in alpha.
</Callout>

## Where your login lives [#where-your-login-lives]

The remote server holds its own sign-in. DorkOS never sees or stores its keys. Before you connect, DorkOS shows you this (with your server's name in place of "that server"):

> This tool connects straight to that server. DorkOS doesn't store or see its keys, that server manages its own sign-in.

## What you get [#what-you-get]

This path connects one account per server. It does not manage several accounts of the same service. If you need two accounts of one service, use the [Composio](/docs/connections/composio) path instead.

## Set it up [#set-it-up]

<Steps>
  <Step>
    ### Have a remote MCP server ready [#have-a-remote-mcp-server-ready]

    You need a server you can reach over the web, with its own sign-in already set up. This is usually a server the service itself runs, or one you host.
  </Step>

  <Step>
    ### Tell DorkOS about it in your config file [#tell-dorkos-about-it-in-your-config-file]

    Raw MCP servers live in DorkOS's config file at `~/.dork/config.json`, under `connectors.rawMcpServers`. Each entry names the service and where its server lives:

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

    The four fields:

    * `slug`: a short id for the service, like `notion`. Lowercase, no spaces.
    * `displayName`: the name you want to see on the Connections page, like `Notion`.
    * `url`: the server's address.
    * `transport`: how DorkOS talks to it. Use `http` for Streamable HTTP (most servers) or `sse` for older servers that stream over SSE (server-sent events, an older streaming style).

    DorkOS reads this list when it starts. After you add or remove an entry, restart DorkOS to pick up the change.
  </Step>

  <Step>
    ### Connect it [#connect-it]

    Open **Connections** in the sidebar. Your server now shows up as a tile in the Services grid. Click **Connect** and read the custody line. Your keys stay on the server, never on your computer.
  </Step>

  <Step>
    ### Use it in a session [#use-it-in-a-session]

    Open a session, then the right panel's **Session** tab. Attach the connection in the **Connections** group to let that session's agent use the server's tools.
  </Step>
</Steps>