# Other MCP clients
JustClaw-It is a standard remote MCP server. Any client that speaks Streamable HTTP and can send a custom header works.
| setting | value |
| --- | --- |
| URL | `https://justclaw.it.com/mcp` |
| transport | Streamable HTTP |
| header | `Authorization: Bearer <YOUR_API_KEY>` |
The common JSON shape:
```json
{ "mcpServers": { "justclaw-it": { "url": "https://justclaw.it.com/mcp", "headers": { "Authorization": "Bearer <YOUR_API_KEY>" } } } }
```
Clients with OAuth connectors can skip the key: use `https://justclaw.it.com/mcp/signin` and sign in with your JustClaw-It account (see [Claude.ai](/docs/clients/claude-ai)). The server publishes standard OAuth 2.1 metadata at `/.well-known/oauth-authorization-server`, with dynamic client registration and PKCE (S256).
Some clients call the URL field `serverUrl` or `httpUrl`, and some put headers under `requestInit`. If your client only supports stdio servers, bridge it with `mcp-remote` the same way as [Claude Desktop](/docs/clients/claude-desktop).
## Check it with curl
```sh
curl -s https://justclaw.it.com/mcp \
-H "Authorization: Bearer $JUSTCLAW_IT_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'
```
A `200` with the server's capabilities means the key and URL are right. A `401` means the key is missing, wrong or revoked. Connecting, `initialize` and `tools/list` never cost credits.
Problems: [Troubleshooting](/docs/troubleshooting).