FluxDesk
← All integrations

Integrations · AI access

Connect an AI with MCP

Connect your own AI client to the Projects you choose. Start with OAuth sign-in, then discover what this connection can do.

Your connection address

Use the address shown on your FluxDesk connection card. The main entry is https://my.fluxdesk.net/mcp. If a Project supplies another endpoint, use that endpoint.

Transport: Streamable HTTP. OAuth uses PKCE and automatic client registration. Permission choices are Can view only, Can create and Can act for me. Available choices depend on your Project permissions.

High-impact decisions remain yours. A connection cannot grant itself access or reach a Project you cannot access.

Connect your client

These steps follow the shipped FluxDesk connection cards. Client versions differ; these instructions do not certify a completed connection in every client.

Claude

  1. Copy the MCP address: https://my.fluxdesk.net/mcp.
  2. Open your client’s remote MCP connection settings and add FluxDesk. Use the address above; leave OAuth Client ID and Client Secret empty for automatic registration.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

ChatGPT

  1. Copy the MCP address: https://my.fluxdesk.net/mcp.
  2. Open your client’s remote MCP connection settings and add FluxDesk. Use the address above; leave OAuth Client ID and Client Secret empty for automatic registration.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

Codex

  1. shell
    codex mcp add fluxdesk --url https://my.fluxdesk.net/mcp
  2. Run the command in your terminal and open the client’s MCP sign-in prompt.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

Cursor

  1. Add FluxDesk to Cursor using its address-only install link.
  2. Open your client’s remote MCP connection settings and add FluxDesk. Use the address above; leave OAuth Client ID and Client Secret empty for automatic registration.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

Gemini

  1. shell
    gemini mcp add --transport http fluxdesk https://my.fluxdesk.net/mcp
  2. Run the command in your terminal and open the client’s MCP sign-in prompt.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

OpenClaw

  1. Copy the MCP address: https://my.fluxdesk.net/mcp.
  2. Open your client’s remote MCP connection settings and add FluxDesk. Use the address above; leave OAuth Client ID and Client Secret empty for automatic registration.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.

Other MCP client

  1. Copy the MCP address: https://my.fluxdesk.net/mcp.
  2. Open your client’s remote MCP connection settings and add FluxDesk. Use the address above; leave OAuth Client ID and Client Secret empty for automatic registration.
  3. Sign in to FluxDesk and choose the Projects, access level and expiry, then allow the connection.
Developer options · token fallback and Claude Code

Prefer OAuth when your client supports it. For the shipped Claude Code card, or a client without OAuth, open Home → AI assistant → Connected AIs → Connect a new AI. Choose Claude Code, or Other → Developer options → Use Token.

  1. In Home → AI assistant → Connected AIs → Connect a new AI → Claude Code, choose a Project and what the connection may do.
  2. Generate the command in FluxDesk. Its token stays masked until you choose to copy or reveal it once.
  3. Copy the generated command, run it privately in your terminal, then ask Claude Code to call fluxdesk_help.

Tokens stay masked. Copy or reveal only when needed. Use a private bearer header or a secret environment variable such as FLUXDESK_MCP_TOKEN; never put a token in a URL, OAuth client field, repository or log.

shell
curl -X POST https://my.fluxdesk.net/mcp \
  -H "Authorization: Bearer $FLUXDESK_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Uses your private environment variable. tools/list is discovery; no business tool is invoked.

Verify access before writing

Ask your client to call fluxdesk_help, then whoami and ping. A saved configuration alone proves no tool call. Help lists every registered tool eligible for this key, grouped by object; object permissions are checked again when you call a tool.

After whoami and ping, mcp_smoke_test reports canCall and missingScopes without creating tasks, feedback, or monitoring routes. Use it for read-only diagnostics before enabling writes.

Read input schemas with tools/list. Examples contain synthetic placeholders and execute nothing. Use dry-run previews and idempotency keys where the tool offers them. New business writes must support both; existing tools are still being brought into line.

Missing scope: reconnect with the needed level. Expired or revoked: reconnect. Suspended: contact your administrator. Missing or inaccessible object: check the Project and reference; do not guess other IDs.

OAuth currently advertises read and write, returns expanded internal scopes, and has no refresh token or expires_in. Connection expiry is still enforced. General quota numbers are pending an enforced admission contract. External clients can poll eligible inbox tools; general Project event subscriptions and replay are not yet offered.

AI connection guide (/agents.md) · Full MCP protocol guide