Skip to content
FLORA DocsGo to app

Other clients

Connect FLORA MCP from any client that supports remote HTTP MCP servers.

FLORA MCP follows the Model Context Protocol 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.

FieldValue
Server nameflora (anything works — use what makes sense in your client)
Transporthttp (also called streamable-http)
URLhttps://florafauna-ai.stlmcp.com/
AuthOAuth 2.1 with PKCE — the client handles it

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

{
"mcpServers": {
"flora": {
"url": "https://florafauna-ai.stlmcp.com/"
}
}
}

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

{
"mcpServers": {
"flora": {
"type": "http",
"url": "https://florafauna-ai.stlmcp.com/"
}
}
}

Some clients (older builds, certain CLI tools) only support stdio MCP servers locally. For those, use the mcp-remote shim to bridge stdio → HTTP:

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

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.

ClientConfig path
Claude Code~/.claude.json (managed via claude mcp add)
Cursor~/.cursor/mcp.json (global), .cursor/mcp.json (project)
VS CodeUser settings, .vscode/mcp.json (workspace)
Windsurf~/.codeium/windsurf/mcp_config.json
Zed~/.config/zed/settings.json under context_servers
Claude DesktopSettings → Connectors (UI, not file-based for HTTP)

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.