← Back to workspace · All guides

Pro · owner access · Reviewed November 8, 2026

Connect an app with REST or MCP

Connect your own integration or an MCP-compatible assistant to the QR codes you authorize. This is a scoped API credential, not a native app marketplace connection.

Before you start

Use a Pro owner account. Start with a read-only connection for one client. Keep credentials out of public pages, QR destinations, shared documents and browser-side code.

Check current plans and signup offers
Choose a connection scope and permissions before creating an app credential. Product screenshot · demo data
  1. Create a scoped connection

    Open Connected apps. Give it a recognizable name, choose one client or your entire account, and leave write permission off for your first test. Choose Create credential.

  2. Save the credential privately

    The credential is displayed once and expires after 30 days. Save it in a secret manager. On staging, use the staging endpoints; production credentials and accounts are separate. Never print a credential on merchandise.

  3. Try a read-only REST request

    Set FQ_TOKEN in your local secret environment, then run:

    curl https://futureqr.app/api/connected/resources  -H "Authorization: Bearer $FQ_TOKEN"
    The response contains resources and nextCursor. Follow a returned cursor with ?cursor=VALUE. To inspect one authorized code: GET /api/connected/analytics?code=CODE_ID&days=30. Responses exclude private inquiries and billing. GET /api/connected/design?code=CODE_ID returns a versioned render specification with the saved style and branded QR payload, not an image file. Use the supplied renderer_url with FQDesign.render(payload, FQDesign.clean(design)) in a trusted browser integration. Wi-Fi credentials are excluded; use Design Studio for Wi-Fi artwork.

  4. Configure an MCP client

    Use https://futureqr.app/api/mcp and the custom header Authorization: Bearer YOUR_CREDENTIAL in a client supporting remote MCP and custom headers. The endpoint supports MCP revision 2025-11-25 with stateless JSON responses. Test tools/list first:

    curl https://futureqr.app/api/mcp  -H "Authorization: Bearer $FQ_TOKEN"  -H "Content-Type: application/json"  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
    Read-only tools are list_resources and scan_analytics. This does not sign in to ChatGPT or Claude automatically; clients without custom-header support cannot use this setup directly.

  5. Enable writes only when needed, then test revocation

    A separate write-enabled credential can expose create_code and update_destination. Each write requires confirm: true and stays within its selected client scope. Review the target code and destination before authorizing a write. Revoke an old credential in Connected apps; its next request must return 401. Credentials allow 300 requests per hour.

Check your result

A read-only request lists only the intended client’s codes, write requests are blocked, and revoking the connection stops further access.

If something goes wrong

401 means missing, expired or revoked credentials. 403 can indicate read-only permission, out-of-scope access or an inactive owner Pro plan. Never broaden scope merely to fix an error. Rotate a leaked credential immediately; do not send it to support.

Get help

Open Connected apps

Related guides