FluxDesk
โ† All integrations

Integrations ยท AI agent access

MCP (Model Context Protocol)

Let an AI agent read your inbox, mark items read, submit daily updates, query tasks / feedback / projects, and act on requests โ€” all over a single Bearer-authed JSON-RPC endpoint.

Connection

Transport
Streamable HTTP (POST /mcp)
URL
https://fluxdesk.predithub.net/mcp
Auth
Authorization: Bearer $FLUXDESK_MCP_TOKEN
Issuance
Self-serve at /me/agent (any authenticated user) or admin issues via access_credentials with credentialType='ai_gateway_token'.

List available tools

Round-trip a standard JSON-RPC tools/list to discover the live tool set (38+ as of v0.19.x). New tools land here without you bumping any client lib.

shell
curl -X POST https://fluxdesk.predithub.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"}'

Setup order

First choose OS: macOS / Linux / Windows. Then choose client: Codex Desktop / Codex CLI / Claude Desktop / Claude Code / Cursor / Windsurf / VS Code / Other MCP client. Then choose mode: desktop app / terminal CLI / CI-server.

shell
launchctl setenv FLUXDESK_MCP_TOKEN '<token>'
launchctl unsetenv FLUXDESK_MCP_TOKEN
shell
systemctl --user set-environment FLUXDESK_MCP_TOKEN='<token>'
systemctl --user unset-environment FLUXDESK_MCP_TOKEN
powershell
[Environment]::SetEnvironmentVariable("FLUXDESK_MCP_TOKEN", "<token>", "User")
[Environment]::SetEnvironmentVariable("FLUXDESK_MCP_TOKEN", $null, "User")
$env:FLUXDESK_MCP_TOKEN="<token>"

Never put the token in the URL. Do not write the token into config files by default. If a client has no env var/header support, use a bridge/local proxy; hardcoded-token fallback is high risk.

Codex CLI

Set FLUXDESK_MCP_TOKEN first, then run:

shell
codex mcp add fluxdesk --url 'https://fluxdesk.predithub.net/mcp' --bearer-token-env-var FLUXDESK_MCP_TOKEN
codex mcp list

codex mcp list only proves config exists. Then ask Codex to call FluxDesk whoami and ping.

Validation and troubleshooting

  • Config exists: client shows fluxdesk, or Codex lists it.
  • ้ชŒ่ฏๅฎž้™…ๅฏ่ฐƒ็”จ: whoami succeeds, then ping succeeds.
  • Diagnostics: after whoami/ping, call mcp_smoke_test to inspect registered tools, canCall, and missingScopes without creating tasks, feedback, or monitoring routes.
  • Common failures: env not inherited, app not fully restarted, URL wrong, token in URL, list_tools failed, HTTP unsupported needs bridge, proxy/firewall.

Tool families (live count via tools/list)

  • Inbox

    list_inbox, get_notification, mark_*_read.

  • Daily check-in

    submit_daily_update + recall.

  • Tasks

    Create / dispatch / status / blocker.

  • Feedback

    Comment, edit, mark-resolved.

  • Projects

    List, read, dashboard summary.

  • Inbound delivery

    Resolve / supplement / lifecycle.

  • Outbound

    Manage your own webhooks.

  • Team-support

    Approval requests / catalog (admin).

Full guide