---
title: Other clients
description: "Connect any MCP client that speaks Streamable HTTP to the platform with the endpoint URL and an Authorization header, or run the CLIKA CLI as a local stdio server for a client that only starts commands."
---

Any MCP client that speaks Streamable HTTP can connect to the platform. It needs two things: the endpoint URL, `<base-url>/api/mcp` (or a [toolset](index.md#the-mcp-endpoint-and-its-toolsets) below it), and an `Authorization: Bearer` header carrying an [API key](index.md#you-need-an-api-key). The endpoint is stateless, and a request without a valid key is refused before any tool runs.

Where a client takes a JSON server definition, the definition has this shape:

```json
{
  "url": "https://platform.clika.io/api/mcp",
  "headers": {
    "Authorization": "Bearer clika_your_api_key"
  }
}
```

The field names and the file they go in are the client's own, so check its documentation for both. Wherever the key is written, it is readable by anything that can read that file.

A client that only starts local commands (stdio) can run the CLIKA CLI as its server instead. After `clika-cli login`, the command is `clika-cli mcp`, which serves the `api-key` toolset from the CLIKA CLI, or `clika-cli mcp --remote`, which bridges to the deployment's own endpoint. Give the command as an absolute path. In both forms the CLIKA CLI reads the key from its profile, so the client's config holds no key. The [CLI reference](../cli/mcp.md#mcp) describes both modes.

Check the connection with a read-only question, such as which devices in your current project are online. If the client cannot connect, see [Troubleshooting](troubleshooting.md).