Integrations

Create a read-only MySQL user for the AI:

CREATE USER 'clearfox'@'%' IDENTIFIED BY 'your-password';
GRANT SELECT ON your_database.* TO 'clearfox'@'%';

If MySQL runs on the host machine, use host.docker.internal as the host.

If MySQL runs in Docker, use the container name as the host.

In ClearFox Admin UI → Integrations, find MySQL → click '+' to add a config. Fill in host, user, pass, db.

Optionally set key_tables to highlight important tables.

Create a read-only PostgreSQL user for the AI:

CREATE USER clearfox WITH PASSWORD 'your-password';
GRANT CONNECT ON DATABASE your_db TO clearfox;
GRANT USAGE ON SCHEMA public TO clearfox;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO clearfox;

If PostgreSQL runs on the host machine, use host.docker.internal as the host.

In ClearFox Admin UI → Integrations, find PostgreSQL → click '+' to add a config. Fill in host, user, pass, db.

Optionally set schema and key_tables.

Create a read-only MongoDB user for the AI:

use admin
db.createUser({ user: "clearfox", pwd: "your-password", roles: [{ role: "read", db: "your_database" }] })

In ClearFox Admin UI → Integrations, find MongoDB → click '+' to add a config. Set the URI (include database name in the path).

If MongoDB runs on the host machine, use host.docker.internal as the host. If in Docker, use the container name.

Go to Google Cloud Console → Service Accounts and create a new service account (e.g. clearfox-analytics). No roles needed during creation.

Enable the Google Analytics Data API for your Google Cloud project.

Open the created service account → Keys tab → Add Key → Create new key → JSON. Download the JSON file.

⚠️ If you get an iam.disableServiceAccountKeyCreation error, your organization blocks key creation. Ask your Organization Policy Administrator to temporarily disable the iam.disableServiceAccountKeyCreation constraint in Organization Policies, or create the key for you.

In Google Analytics, go to Admin → Property Access Management → + → Add users. Add the service account email with Viewer role. The email is in the downloaded JSON file — look for the client_email field (looks like clearfox-analytics@your-project.iam.gserviceaccount.com). ⚠️ Without this step you will get a 403 PermissionDenied error even if the JSON key is valid.

Find your GA4 Property ID: Google Analytics → Admin → Property Settings → Property ID (9-digit number).

In ClearFox Admin → Integrations, find Google Analytics → click '+'. Paste the contents of the JSON key file and enter the Property ID.

Prerequisite: Google OAuth must be configured in ClearFox (Client ID + Secret). See Google OAuth Setup.

Enable the BigQuery API in your Google Cloud project (the same project where your OAuth app lives).

Find your GCP project ID in Google Cloud Console — it’s next to the project name at the top.

Make sure the Google account you’ll connect has at least the BigQuery Data Viewer + BigQuery Job User roles on the project (IAM & Admin → IAM).

Each user goes to Integrations → BigQuery, clicks Connect Google Account, signs in, then pastes the GCP project ID. The AI can immediately list datasets, inspect schemas and run SELECT queries.

Admin alternative — service account (no per-user sign-in): paste one shared service-account key instead of OAuth. In IAM & Admin → Service Accounts create a service account, grant BigQuery Data Viewer + BigQuery Job User, add a JSON key, paste it into Admin → Integrations → BigQuery. Queries run as that shared identity; tokens never expire.

With a Workspace Internal OAuth app (see Google OAuth Setup) there is no unverified-app warning and no 7-day token revoke. Scope is bigquery.readonly — DML/DDL is blocked; use the BigQuery console for writes.

Go to Atlassian API Tokens.

Click 'Create API token', name it (e.g. 'ClearFox AI'), and copy the token.

In ClearFox Admin UI → Integrations, find Jira → click '+' to add a config. Fill in base_url, email, api_token, and optionally default_projects.

Go to Atlassian API Tokens.

Click 'Create API token', name it (e.g. 'ClearFox AI'), and copy the token.

In ClearFox Admin UI → Integrations, find Confluence → click '+' to add a config. Fill in url, email, api_token.

Pick one of two setups: (A) shared workspace Internal Integration token — simplest if one Notion workspace is exposed to all employees; (B) OAuth — when each user has their own Notion or you want per-user access control.

(A) Internal Integration token (recommended for one shared workspace). In Notion, open Settings → Integrations → Develop or manage integrations, create an Internal integration, and under Capabilities enable content read/update/insert plus Read comments and Insert comments (needed for the comment tools). Copy its ntn_… token. In ClearFox Admin → Configs → Notion → + Add, paste it into the api_key field. Then in Notion, share each relevant page with the integration: page … → Connections → add it (top-level pages cascade to children).

(B) OAuth — per-user. Goes through ClearFox's managed proxy (oauth.clearfox.ai) by default; nothing to configure on the admin side. Or register your own Public integration at notion.so/profile/integrations and paste its Client ID/Secret in Admin → OAuth → Notion. Each user then connects in Integrations → Notion and shares the pages they want to expose.

(B) OAuth — shared workspace. If you want a single OAuth-based account shared across all users (instead of an Internal token): Admin → Configs → Notion → + Add, click Connect Notion, authorize once. Grant role access in Admin → Roles.

Resolution order at runtime: personal OAuth → workspace OAuth → workspace api_key. Whichever is set first wins; the others act as fallbacks.

Prerequisite: finish Google OAuth Setup (Workspace Internal app, Gmail API enabled, Gmail scopes added). Client ID and Secret must already be saved in Admin → OAuth.

If you skipped APIs earlier, enable the Gmail API in the same Google Cloud project as your OAuth client.

Gmail uses per-user OAuth — each employee connects their own mailbox. There is no shared admin spreadsheet-style config.

Each user opens Integrations and clicks Connect Google Account next to Gmail. Sign in with their Workspace account. On Google’s consent screen each permission is a separate checkbox — they can grant read-only and skip send/compose if they want a safer subset.

After connecting, the AI can search and read mail, manage labels, create drafts, and send mail — only for that user’s mailbox, within the scopes they approved.

Tip: If Connect fails with accessNotConfigured, the Gmail API is not enabled (step 2). If users outside your Workspace try to connect, Internal audience correctly blocks them — that is expected.

Go to Slack API Apps and click 'Create New App' → 'From scratch'.

Name it (e.g. 'ClearFox AI') and select your workspace.

Go to 'OAuth & Permissions' → 'Scopes' → add Bot Token Scopes:

channels:read, channels:history, groups:read, groups:history,
users:read, search:read, chat:write (if you want the AI to post).

Click 'Install to Workspace' and authorize.

Copy the 'Bot User OAuth Token' (starts with xoxb-...).

In ClearFox Admin UI → Integrations, find Slack → click '+' to add a config. Paste the bot token.

Invite the bot to channels it should access: /invite @ClearFox AI

Log in to Freshservice as an admin.

Go to your profile icon → Profile Settings.

On the right side, find your API Key and copy it.

Your domain is the subdomain (e.g. 'mycompany' from mycompany.freshservice.com).

In ClearFox Admin UI → Integrations, find Freshservice → click '+' to add a config. Fill in url and api_key.

Go to Stripe Dashboard → API Keys.

Click '+ Create restricted key' (recommended over the secret key for security).

Give it a name (e.g. 'ClearFox AI Read-Only').

Set permissions: All Read access. Do NOT enable any Write permissions unless needed.

Click 'Create key' and copy it (starts with rk_live_... or sk_live_...).

In ClearFox Admin UI → Integrations, find Stripe → click '+' to add a config. Paste the API key.

For test mode, use keys from 'Test mode' toggle (starts with sk_test_...).

Go to HubSpot → Settings (gear icon) → Integrations → Private Apps.

Click 'Create a private app', name it (e.g. 'ClearFox AI').

Go to 'Scopes' tab and enable read scopes you need:

crm.objects.contacts.read, crm.objects.deals.read, crm.objects.companies.read, etc.

Click 'Create app' and copy the access token.

In ClearFox Admin UI → Integrations, find HubSpot → click '+' to add a config. Paste the access token.

Log in to your Bitrix24 cloud account as an administrator.

Go to Developer resources → Other → Inbound webhook.

Grant the scopes you want exposed: crm (leads, deals, companies, contacts), lists (Lists / Списки), tasks, user.

Copy the full webhook URL — it ends with a trailing slash, e.g. https://yourcompany.bitrix24.ru/rest/1/abc123token/.

In ClearFox Admin UI → Integrations, find Bitrix24 → click '+' to add a config. Paste the webhook URL.

The webhook inherits the permissions of the user who created it. Use an admin user for full read access.

In Customer.io, go to Settings → Account Settings → API Credentials.

Open the App API Keys tab, click 'Create App API Key', name it (e.g. 'ClearFox AI') and copy it. This powers all reads.

Note your data region — US accounts use customer.io, EU accounts use the EU data center. Pick the matching Region in the config.

Optional (for writes): on the Track API Keys tab, copy your Site ID and a Track API Key — these enable identifying people and tracking events.

In ClearFox Admin UI → Integrations, find Customer.io → click '+' to add a config. Paste the App API key, set the region, and (optionally) the Track Site ID and Track API key.

Log in to BambooHR as an admin.

Click your name → API Keys.

Click 'Add New Key', name it (e.g. 'ClearFox AI'), and copy the key.

Your subdomain is the part before .bamboohr.com (e.g. 'mycompany').

In ClearFox Admin UI → Integrations, find BambooHR → click '+' to add a config. Fill in subdomain and api_key.

Log in to HiBob as an admin.

Go to Settings → Integrations → Service Users.

Create a new service user and grant it read access to the employee data categories you need — at minimum Basic info, Work and Employment / Lifecycle — plus Time off. ⚠️ HiBob silently omits any category the service user cannot read, so without Work / Employment access the assistant sees employee names but empty department, title, site and status — headcount and org-structure answers come back blank.

For hiring / ATS tools (candidates, applications, job ads), also grant the service user read access to the Hiring data categories. Without it the hiring tools return permission errors while employee tools keep working.

Copy the Service User ID and Token.

In ClearFox Admin UI → Integrations, find HiBob → click '+' to add a config. Fill in api_token and service_user_id.

Prerequisite: finish Google OAuth Setup (Workspace Internal app + Sheets API + spreadsheet scopes).

If needed, enable the Google Sheets API in the same Google Cloud project as your OAuth client.

Go to Admin → OAuth (or Integrations) and Connect Google Account with a Workspace user that can open the spreadsheets you need.

Go to Admin → Integrations → Google Sheets → click +. Select the connected account and paste the spreadsheet URL or ID. Users can also add their own sheets under Integrations → Google Sheets — the connected Google account must have access (owner or shared).

Prerequisite: finish Google OAuth Setup (Workspace Internal app + Calendar API + calendar scopes).

If needed, enable the Google Calendar API in your Google Cloud project.

Google Calendar uses per-user OAuth — each user connects their own account. No admin-level config in Integrations.

Each user opens Integrations → Connect Google Account next to Google Calendar, signs in with their Workspace account, and approves access.

The AI can then list events, check free/busy, create events with Google Meet links and reminders, and search the calendar — scoped to that user's account.

Prerequisite: finish Google OAuth Setup (Workspace Internal app + Drive API + drive scopes).

If needed, enable the Google Drive API in your Google Cloud project.

Google Drive uses per-user OAuth — each user connects their own account. No admin-level config in Integrations.

Each user opens Integrations → Connect Google Account next to Google Drive. On the consent screen each permission is a separate checkbox — they can grant read-only and skip full Drive access.

The AI can then search and read files (Docs/Sheets/Slides exported as text), create folders, upload, move, rename, share and trash — scoped to that user's Drive.

Prerequisite: finish Google OAuth Setup (Workspace Internal app + Docs API + Drive API + documents scopes).

If needed, enable the Google Docs API and the Google Drive API (used to search documents).

Google Docs uses per-user OAuth — each user connects their own account under Integrations → Connect Google Account next to Google Docs.

The AI can then search documents, read full text, create docs, append and replace text — scoped to that user's account.

Prerequisite: finish Google OAuth Setup (Workspace Internal app + Slides API + Drive API + presentations scopes).

If needed, enable the Google Slides API and the Google Drive API (used to search presentations).

Google Slides uses per-user OAuth — each user connects under Integrations → Connect Google Account next to Google Slides.

The AI can then search and read presentations, create decks, add slides, replace template text, and delete slides — scoped to that user's account.

Prerequisite: Microsoft 365 OAuth must be configured first. See Microsoft 365 OAuth Setup.

In Azure Portal → App registrations, open your ClearFox app → API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add: Files.ReadWrite.All, User.Read, offline_access. Click Grant admin consent — some tenants require a tenant admin to approve Files.ReadWrite.All before users can connect.

Go to Admin → Integrations → Microsoft Excel (or Integrations for a personal connection) → click +. Connect a Microsoft account that can open the workbook, then paste the SharePoint or OneDrive Excel link into Workbook URL or ID. SharePoint sharing links (e.g. …sharepoint.com/:x:/r/…) work — ClearFox resolves them via Microsoft Graph.

The connected Microsoft account must have access to the workbook (owner or shared with edit/view rights matching the tools you use).

The AI can then list worksheets, read ranges, search cells, write values and append rows — scoped to that workbook.

Tip: If consent fails with an admin-approval error, an Azure AD admin must grant admin consent for the app (step 2) for the whole organization.

Prerequisite: Microsoft 365 OAuth must be configured first. See Microsoft 365 OAuth Setup.

In Azure Portal → App registrations, open your ClearFox app → API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add: Files.Read.All, Sites.Read.All, User.Read, offline_access. Click Grant admin consent — Sites.Read.All and Files.Read.All often require tenant admin approval.

Microsoft Files uses per-user OAuth — each user connects their own account under Integrations next to Microsoft OneDrive & SharePoint. There is no per-file config; the AI searches across that user's OneDrive and SharePoint sites.

The AI can search files, list folders and SharePoint sites, read metadata, and extract text from Word, PDF and plain-text files. For Excel workbooks, connect the file via Microsoft Excel instead.

Tip: If users see a permissions error after connecting, make sure admin consent was granted in step 2 for the entire organization.

Prerequisite: Microsoft 365 OAuth must be configured first. See Microsoft 365 OAuth Setup.

In Azure Portal → App registrations, open your ClearFox app → API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add: Calendars.ReadWrite, User.Read, People.Read, offline_access. Click Grant admin consent.

Microsoft Calendar uses per-user OAuth — each user connects their own account. There is no admin-level config needed in Integrations.

Each user goes to Integrations and clicks Connect Microsoft Account next to Microsoft Calendar. This opens a Microsoft login popup. After approving, their calendar is immediately available to the AI.

The AI can then list events, check availability, create meetings, and search the calendar — all scoped to that user's own account.

Tip: If users see a permissions error after connecting, make sure admin consent was granted in step 2 for the entire organization.

Prerequisite: Microsoft 365 OAuth must be configured first. See Microsoft 365 OAuth Setup.

In Azure Portal → App registrations, open your ClearFox app → API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add: Team.ReadBasic.All, Channel.ReadBasic.All, ChannelMessage.Send, Chat.ReadWrite, User.Read, offline_access. Click Grant admin consent.

Microsoft Teams uses per-user OAuth — each user goes to Integrations and clicks Connect Microsoft Account next to Microsoft Teams. Messages the AI sends appear in Teams as sent by that user.

The AI can then list the user's teams, channels and chats, read chat history, send messages to channels, and start one-on-one chats with colleagues by email.

Bot-style notifications (recommended for scheduled reports): create a dedicated Microsoft 365 user such as ai@yourcompany.com named e.g. ‘ClearFox AI’ (a license with Teams is required), add it to the teams and channels it should post to, and connect it in Admin → Integrations → Microsoft Teams as a workspace connection. Messages sent through this connection appear as the ‘ClearFox AI’ user — in channels and in one-on-one chats with any employee.

Note: Microsoft Graph only allows sending Teams messages on behalf of a signed-in user (delegated permissions). App-only tokens cannot send messages — this is a Microsoft platform restriction, which is why the service-account approach above is used for bot-style messaging.

Log in to Odoo as an admin.

Go to Settings → Users & Companies → your user → Preferences tab.

Scroll to 'API Keys' section → click 'New API Key', name it, and copy the key.

Your Odoo URL is the base URL of your instance (e.g. https://mycompany.odoo.com).

The database name is visible in the URL or in Settings → Database Manager.

In ClearFox Admin UI → Integrations, find Odoo → click '+' to add a config. Fill in url, db, username, api_key.

Log in to Make.com → click your profile icon (bottom-left) → Profile.

Scroll to the API section → click 'Add API token'. Select all scopes you need (at minimum: scenarios, connections, organizations) → click 'Save'. Copy the token immediately (it is shown only once).

Find your Organization ID: go to Organization settings → the ID is in the URL: make.com/organization/ORG_ID/....

Find your Team ID (optional): click on a team → the ID is in the URL: make.com/organization/.../team/TEAM_ID/....

In ClearFox Admin UI → Integrations, find Make → click '+' to add a config. Fill in api_token, and optionally team_id and zone.

Log in to Zapier → go to Settings (gear icon) → API Keys.

Click 'Create API Key', name it (e.g. 'ClearFox AI'), and copy the key.

In ClearFox Admin UI → Integrations, find Zapier → click '+' to add a config. Paste the API key.

The API key provides read access to your Zaps, task history, and folders.

Datadog read APIs require both an API key and an Application key. Use a dedicated read-only service account where possible — the Application key inherits the user's permissions.

Find your Site (region): log in to Datadog and check the URL bar. app.datadoghq.com → site is datadoghq.com (US1, default). Other sites: datadoghq.eu (EU), us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com, ddog-gov.com. ⚠️ Using the wrong site returns 403 Forbidden even with valid keys.

Create the API key: go to Organization Settings → API Keys → + New Key. Name it (e.g. ClearFox AI) and copy the value.

Create the Application key: go to Organization Settings → Application Keys → + New Key. Name it (e.g. ClearFox AI) and copy the value. ⚠️ The API key alone is not enough for read endpoints; the Application key is mandatory.

⚠️ Don't confuse Key ID with Key value. The Application Keys table shows the Key ID (UUID with dashes, 36 chars) — that is not the key. Click the row to open the details panel and copy the Key field (40 hex chars, no dashes). If the value is no longer shown there, create a new key — Datadog reveals the full value only at creation time. Pasting the Key ID produces 401 Unauthorized on every endpoint while the API key validation still appears to succeed.

Scope the Application key (recommended): open the new key → Scopes tab → switch from Inherit user permissions to Custom scopes. Enable read-only scopes for what the AI needs: monitors_read, metrics_read, logs_read_data, events_read, dashboards_read, incident_read, slos_read, hosts_read. Without scopes the key has full access of the user that created it.

In ClearFox Admin UI → Integrations, find Datadog → click '+' to add a config. Set site (e.g. datadoghq.com or datadoghq.eu), paste api_key and app_key.

Common errors: 403 Forbidden → wrong site, missing scope on the App key, or the user that created the App key was deactivated. 401 Unauthorized → API key is invalid or revoked.

ClearFox reads Sentry only — issues, stack traces, releases and error volume stats. It never resolves, assigns or modifies anything.

Recommended token type: an internal integration — it is org-scoped and keeps working if an employee leaves. In Sentry go to Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration. Name it (e.g. ClearFox AI).

Set Permissions: Issue & Event → Read, Project → Read, Organization → Read. Leave everything else at No Access, then Save Changes.

On the integration page scroll to Tokens → New Token and copy the value — it is shown only once.

Alternative: a personal User Auth Token with scopes event:read, project:read, org:read also works, but it is tied to your user account.

Find your organization slug in the Sentry URL: sentry.io/organizations/SLUG/... or the subdomain SLUG.sentry.io. You can skip it if the token sees exactly one organization — ClearFox detects it automatically.

Self-hosted Sentry: set url to your instance base URL (e.g. https://sentry.yourcompany.com). The API is identical; create the token the same way in your instance settings.

In ClearFox Admin UI → Integrations, find Sentry → click '+' to add a config. Paste auth_token; fill url and org only if needed.

Common errors: 401 Unauthorized → token invalid or revoked. 403 Forbidden → missing Read permission on the integration. "Token sees multiple organizations" → set the org slug explicitly.

Log in to Grafana as an admin and open Administration → Users and access → Service accounts (Grafana 9+). On older versions use Configuration → API keys.

Click Add service account, name it (e.g. ClearFox AI), and set role to Viewer. Viewer is enough to query datasources, dashboards, and alert state — the AI never writes to Grafana.

On the service account page, click Add service account token, give it any name, and copy the token (starts with glsa_). The token is shown only once.

Datasources must already be configured in Grafana itself — ClearFox queries them through Grafana's datasource proxy. Typical setup: Loki for logs, Prometheus for metrics. No extra credentials needed on ClearFox side.

Your URL is the Grafana base URL, e.g. https://grafana.yourcompany.com. If Grafana is on the same private network as ClearFox you can also use the internal URL.

In ClearFox Admin UI → Integrations, find Grafana → click + to add a config. Fill in url and api_key (paste the glsa_ token).

Querying logs: the AI uses LogQL via Loki, e.g. {app="api"} |= "error". It can list available labels and values automatically. If you have multiple Loki datasources, the AI will ask which one to use.

Self-hosted Grafana with self-signed TLS: use a publicly trusted certificate (Caddy / Let's Encrypt) or expose Grafana over plain HTTP on the internal network — ClearFox does not skip TLS verification by design.

ClearFox reads Cloudflare analytics only (HTTP traffic, security/WAF events, DNS queries, origin 5xx errors) — it never changes DNS, firewall, or any settings. A single scoped, read-only API token covers every zone in the account.

Create the token: go to My Profile → API Tokens → Create Token → Create Custom Token.

Add these Permissions (all Read): Account → Account Analytics → Read; Zone → Analytics → Read; Zone → Zone → Read. Zone Read lets the AI list your domains and find zone IDs; Analytics Read powers the reports.

Under Account Resources select your account, and under Zone Resources choose All zones (or pick specific zones). Continue, then Create Token and copy the value — it is shown only once.

In ClearFox Admin UI → Integrations, find Cloudflare → click '+' to add a config and paste api_token.

Note on numbers: Cloudflare samples high-volume traffic, so request and bandwidth figures are sampling-adjusted estimates and may differ slightly from the dashboard. Common errors: Authentication error → token missing Analytics Read or Zone Read; empty security results → the dataset window is limited (often ~72h on lower plans) — narrow the time range.

Generate a dedicated SSH deploy key (no passphrase):

ssh-keygen -t ed25519 -C "clearfox-git" -f ~/.ssh/clearfox_git -N ""

Copy the public key — you will need it in the next step:

cat ~/.ssh/clearfox_git.pub

Add the public key as a deploy key in your Git hosting. Grant read-only access.
GitHub: Managing deploy keys · GitLab: Deploy keys

Base64-encode the private key (the value ClearFox needs):

cat ~/.ssh/clearfox_git | base64 -w0 ; echo

On macOS use base64 without -w0 and strip line breaks:

cat ~/.ssh/clearfox_git | base64 | tr -d '\n' ; echo

In ClearFox Admin UI → Integrations, find Git → click '+' to add a config. Paste the base64 SSH key and repos (comma-separated URL|branch).

The server will clone repos on startup and provide code search and file reading tools.

ClearFox connects to GitLab (self-hosted or gitlab.com) via the REST API: merge requests with diffs and comments, issues (read and create), CI pipelines with job logs, repository files and search.

Create an access token. Recommended: a project or group access token so it is not tied to a person — in GitLab open the project/group → Settings → Access tokens. A personal token from Preferences → Access tokens also works.

Select the scope: api for full functionality (the AI can post MR comments and create issues) or read_api for strictly read-only access. Role Reporter is enough for reading, Developer for commenting.

Copy the token (glpat-...) — it is shown only once.

In ClearFox Admin UI → Integrations, find GitLab → click + to add a config. Fill in base_url (e.g. https://gitlab.yourcompany.com) and token. Self-hosted instances on a private network work — use the internal URL.

Common errors: 401 Unauthorized → token invalid, expired or revoked (GitLab tokens have an expiry date — check it). 403 Forbidden → the token role is too low for the action (e.g. commenting needs Developer). 404 on an existing project → the token cannot see that project — use a group token or widen the scope.

Generic connector for any HTTP API that has no dedicated ClearFox integration — internal services, niche SaaS, self-hosted tools. The AI can call GET/POST/PUT/PATCH/DELETE endpoints relative to a base URL you configure.

In ClearFox Admin UI → Integrations, find REST API → click + to add a config. Fill in base_url (e.g. https://api.example.com/v1).

If the API needs authentication, set auth_header (e.g. Authorization or X-Api-Key) and auth_value (e.g. Bearer xxx or the raw key). The auth header is only ever sent to the configured host — the AI cannot redirect it elsewhere.

Optional: set openapi_url to the API's OpenAPI/Swagger JSON — the AI can then discover available endpoints by itself instead of guessing paths.

Add a short label and a description so the AI knows what the API is for — this strongly improves how well it uses the integration.

Tip: add one config per API. Multiple configs appear to the AI as separate named instances.

No configuration needed. This server fetches URLs and extracts content as markdown.

It works out of the box with no API keys required.

No configuration needed. This server provides structured step-by-step reasoning.

It works out of the box with no API keys required.

No configuration needed. This server provides persistent memory storage for the AI.

It works out of the box with no API keys required.

On top of the built-in integrations, each user can connect their own remote MCP servers. Go to Integrations → Custom MCP servers.

Click + Add server and fill in: a short name (lowercase, used as the tool prefix — e.g. context7), the server URL (must be https://), and a short description of what it is for (the assistant uses this to decide when to call it — or click Fill with AI to generate one).

Choose Authentication: None for open servers; Authorization header to paste a token (e.g. Bearer xxx); or OAuth when the provider asks you to sign in (see the Customer.io example below).

For header/none servers, click Test connection to list the tools, then Save. For OAuth, Save first, then Authorize and complete the sign-in popup — the status turns to ✓ Connected.

The server's tools become available in your own chats and personal agents only, named name_tool (e.g. context7_query-docs). They are not shared with other users or admins.

Security: a custom server is third-party code you choose to trust — its tools and responses reach the assistant the same as built-in ones. The portal only accepts public https:// URLs (internal/private addresses are blocked) and never sends a custom server any other integration's data or credentials.

Many hosted MCP servers (e.g. Customer.io, Notion, Linear) authenticate with OAuth — you sign in to grant access instead of pasting a token.

In Integrations → Custom MCP servers, add a server with the provider's MCP URL (e.g. https://mcp-eu.customer.io/mcp) and set Authentication to OAuth. No client ID or secret is needed — the portal registers itself automatically.

Click Save, then Authorize. A popup opens the provider's sign-in / consent screen; approve access to your workspace.

After the popup closes the server shows ✓ Connected and its tools are ready. Use Disconnect to revoke, or Re-authorize to switch accounts. Tokens are refreshed automatically.

Context7 serves up-to-date documentation for thousands of libraries and frameworks as MCP tools.

(Optional) Create an API key at context7.com/dashboard for higher rate limits. Context7 also works without a key.

In Integrations → Custom MCP servers, add a server: name context7, URL https://mcp.context7.com/mcp, and (if you made a key) Authorization Bearer ctx7sk-….

Save. The assistant can now resolve a library and pull its docs on demand via the context7_* tools.