---
title: Other clients | FLORA API
description: Connect FLORA MCP from any client that supports remote HTTP MCP servers.
---

FLORA MCP follows the [Model Context Protocol](https://modelcontextprotocol.io) spec exactly, so any client that supports **streamable HTTP** with OAuth 2.1 can connect. This page is the fallback for clients without a dedicated install page above.

If your client is web-based or otherwise lacks shell/filesystem access, FLORA MCP can’t upload local files through it — Techniques can only take inputs that already live at an HTTPS URL. For asset upload workflows, use a client with terminal access: [Claude Code](/mcp/install/claude-code/index.md), [Cursor](/mcp/install/cursor/index.md), or [VS Code](/mcp/install/vscode/index.md). See [Tools → Assets](/mcp/tools/#assets/index.md) for details.

## What every client needs

\| Field | Value | | --- | --- | | Server name | `flora` (anything works — use what makes sense in your client) | | Transport | `http` (also called `streamable-http`) | | URL | `https://agents.flora.ai/mcp` | | Auth | OAuth 2.1 with PKCE — the client handles it |

## Generic JSON config

Most clients accept a JSON config in one of two shapes. Try this first:

```
{
  "mcpServers": {
    "flora": {
      "url": "https://agents.flora.ai/mcp"
    }
  }
}
```

If your client distinguishes transports explicitly, add `"type"`:

```
{
  "mcpServers": {
    "flora": {
      "type": "http",
      "url": "https://agents.flora.ai/mcp"
    }
  }
}
```

## Clients with stdio-only MCP support

Some clients (older builds, certain CLI tools) only support stdio MCP servers locally. For those, use the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) shim to bridge stdio → HTTP:

```
{
  "mcpServers": {
    "flora": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://agents.flora.ai/mcp"]
    }
  }
}
```

`mcp-remote` spawns a local proxy that speaks stdio to the client and HTTP to FLORA. OAuth tokens are cached in `~/.mcp-auth/`. You’ll need Node.js 18+ on the machine.

## Common client config locations

\| Client | Config path | | --- | --- | | Claude Code | `~/.claude.json` (managed via `claude mcp add`) | | Cursor | `~/.cursor/mcp.json` (global), `.cursor/mcp.json` (project) | | VS Code | User settings, `.vscode/mcp.json` (workspace) | | Hermes Agent | `~/.hermes/config.yaml` under `mcp_servers` | | OpenClaw | `~/.openclaw/openclaw.json` under `mcp.servers` (managed via `openclaw mcp` CLI) | | Claude Desktop | Settings → Connectors (UI, not file-based for HTTP) |

## Verifying the connection

Whichever client you use, the smoke test is the same. Ask the assistant:

> List my FLORA Techniques.

If you get a list back, you’re connected. If not, see [Troubleshooting](/mcp/troubleshooting/index.md).

Building a new MCP client and want to test against FLORA? Open `https://agents.flora.ai/.well-known/oauth-authorization-server` to see the discovery document and validate your OAuth flow.

## Next

- [Authentication details](/mcp/authentication/index.md)
- [Tools reference](/mcp/tools/index.md)
- [Troubleshooting](/mcp/troubleshooting/index.md)