> ## Documentation Index
> Fetch the complete documentation index at: https://docs.swoop.it/llms.txt
> Use this file to discover all available pages before exploring further.

# Other clients

> Connect any MCP-compatible client to Swoop

export const McpEndpoint = () => <pre><code>https://swoop.it/api/mcp</code></pre>;

Any client that supports the [Model Context Protocol](https://modelcontextprotocol.io/) can connect to Swoop. This guide covers the general setup for clients not listed in the dedicated guides.

## Prerequisites

* A Swoop account at [swoop.it](https://swoop.it)
* An MCP-compatible client that supports Streamable HTTP transport

## Endpoint

Point your client to the Swoop MCP server:

<McpEndpoint />

## Connection methods

<Tabs>
  <Tab title="Direct connection">
    If your client supports Streamable HTTP with OAuth natively:

    <Steps>
      <Step title="Add a new MCP server">
        In your client's MCP configuration, add a new server with the endpoint URL above.
      </Step>

      <Step title="Authenticate">
        Your client will initiate an OAuth flow. Sign in with your Swoop account and approve the consent screen.
      </Step>

      <Step title="Verify">
        Confirm that `ask_swoopAgent` appears in the list of available tools.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Using mcp-remote">
    If your client only supports stdio-based MCP servers, use `mcp-remote` as a bridge:

    ```json theme={null}
    {
      "mcpServers": {
        "swoop": {
          "command": "npx",
          "args": [
            "mcp-remote@latest",
            "https://swoop.it/api/mcp"
          ]
        }
      }
    }
    ```

    This translates the stdio protocol to Streamable HTTP and handles OAuth automatically.
  </Tab>

  <Tab title="API key">
    For clients that don't support OAuth, authenticate with an API key by including it as a Bearer token in each request:

    ```
    Authorization: Bearer ak_your_api_key_here
    ```

    With `mcp-remote`, pass the key via the `--header` flag:

    ```json theme={null}
    {
      "mcpServers": {
        "swoop": {
          "command": "npx",
          "args": [
            "mcp-remote@latest",
            "https://swoop.it/api/mcp",
            "--header",
            "Authorization:Bearer ak_your_api_key_here"
          ]
        }
      }
    }
    ```

    See [Authentication](/mcp/authentication) for details on creating API keys.
  </Tab>
</Tabs>

## Tested clients

The following clients have been verified to work with the Swoop MCP server:

| Client                             | Transport              | Auth  |
| ---------------------------------- | ---------------------- | ----- |
| [Claude Desktop](/mcp/claude)      | stdio via `mcp-remote` | OAuth |
| [Claude Web & Mobile](/mcp/claude) | Streamable HTTP        | OAuth |

<Note>
  If your client isn't listed above, it should still work as long as it supports MCP over Streamable HTTP (directly or via `mcp-remote`). If you run into issues, check [Troubleshooting](/mcp/troubleshooting).
</Note>