# Other clients

> Connect any MCP client or your own code to GetIntel's MCP server, directly over HTTP or through mcp-remote for stdio-only clients.

Source: https://getintel.ai/docs/mcp/clients/other-clients/

Any MCP client can connect. Use whichever of these your client supports.

## Clients that support sign-in

If your client supports remote MCP with OAuth, point it at `https://app.getintel.ai/mcp` with no token. It discovers GetIntel's OAuth server from `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`, registers itself, and sends you to sign in and approve. See the [protocol reference](/docs/mcp/protocol/#discovery) for the endpoints.

## Clients with remote HTTP support

Point the client at the endpoint and send the token as a header:

- **URL:** `https://app.getintel.ai/mcp`
- **Header:** `Authorization: Bearer YOUR_TOKEN`
- **Transport:** Streamable HTTP

## Stdio-only clients

Bridge through `mcp-remote` (requires Node.js):

```json
{
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://app.getintel.ai/mcp",
    "--header", "Authorization: Bearer YOUR_TOKEN"]
}
```

## Your own code

Call the server directly with JSON-RPC 2.0. List the tools:

```sh
curl -s https://app.getintel.ai/mcp \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Call one:

```sh
curl -s https://app.getintel.ai/mcp \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_topics","arguments":{"days":30}}}'
```

See the [protocol reference](/docs/mcp/protocol/) for every method and error.

<Aside>
Client config formats change between versions. If your client's file looks different from these examples, check its own MCP documentation and use the URL and header above.
</Aside>