Connections

Connections let Alchex work with the systems your organization already uses — your document stores, identity provider, ticketing, code hosting, and monitoring tools. A connection can do what its app's own connector service offers and what the account you sign in with is allowed to do; Alchex adds no read-only limit of its own.

How changes happen:

• A connection holds every tool its app offers, and the assistant can change things when you ask. Like Claude's own connectors, Alchex keeps no list of allowed tools: a connection gets every tool its app's own connector service offers, and the assistant can do more than read: for example open an issue, comment on one, or update it. Which tools only look and which change something is the app's own word. Each change is one of two kinds:

  • Most changes, such as creating or updating an issue, start on Auto: they run when you ask for them.
  • Changes the app itself marks as destructive start on Ask: they wait for your yes in the conversation, and the assistant never makes one in an unattended run while it is on Ask. Which tools those are is the app's own word, never a guess from a tool's name.

  Both are only where a tool starts. You decide: set any tool to Auto or Ask, or the whole connection to Ask (see Auto or Ask below), and your choice is what runs. Nothing is hidden or refused for being a change. A procedure that asks for a Slack message is no exception: the session that runs it sends through the Slack connection under the same Auto or Ask choice.

  Every change is written to your workspace's history: who asked for it, which change it was, and on which connection. Audits and evidence checks only ever read. They can never change the system they are checking.

  Open the connection to see every tool it holds, by name, each with its own Auto / Ask showing where it stands now. A tool that changes something says so under its name, and one its app marks as destructive says that too. Tools that only look — including ones that download a file or fetch its details — change nothing in the app and carry no such note.

Either way, a change is whatever the app offers and the account you signed in with allows.

Every app connects one way: through its maker's own connector service. Connect opens the app's own sign-in and consent screen, the same for every app on this page, the way Claude's own connectors work. Any member of the workspace can connect an app for themselves; no administrator is needed.

Connections live in Settings → Connections, under Account, and the list is yours. You connect the apps you need; a colleague connects theirs. You might have Salesforce where she has only Gmail, and neither of you sees the other's.

Anyone can add one — it is not an admin job — and what you add is yours to rename, disconnect or delete. Nobody else can manage it, and an admin cannot either.

⚠ Connections made before 13 September 2026 belong to the workspace, not to a person. They were added when a connection was shared, so they are still listed for everyone and only an Owner or Admin can rename, disconnect or remove them. Everything added since belongs to whoever added it.

Your connections and the library

Settings → Connections lists only the apps you have connected. Rows that need you — a connection that lost access — come first, so a broken one is never below the fold. Reconnect sits right on the row; click anywhere else on a row to open its page.

Everything you could connect is in the library: press Add connection. Search there looks across every app, whatever category is selected; the categories on the left narrow the list when you browse instead. An app you already connected stays in the library, marked Connected, so searching for it never reads as "not available".

The catalog, by category

Connectors are grouped into fourteen categories by the kind of evidence they hold, in the order most workspaces should connect them — identity and documents unlock the most, so they lead. The library's category list shows only categories that have an app in them.

Every app is shown with its own official logo, in its own colours, exactly as the vendor publishes it — the same in light and dark mode. A custom server you add yourself has no vendor, so it shows a plug.

Identity & Access

Okta, Microsoft Entra ID, Google Cloud IAM, Google Workspace and Microsoft Azure IAM are no longer offered. Alchex reaches an app only through the app maker's own hosted connector service, and none of these has one Alchex can use today. A connection made to one before shows as needing a reconnect, and the reconnect is refused until one exists.

• JumpCloud — users, devices, groups, SSO applications, policies, patch status and alerts through JumpCloud's own hosted connector service.

  What you approve when you connect: JumpCloud's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in JumpCloud administrator and can use every tool JumpCloud's server offers, including any that change data.

• WorkOS — SSO connections, directories, organizations, users and session settings through WorkOS's own hosted connector service.

  What you approve when you connect: WorkOS's own sign-in and consent screen for its hosted connector service; the connection acts with the signed-in WorkOS user's role, and a WorkOS admin can turn off write access for the whole team.

Documents & Knowledge

Your policies, procedures, and records — the documents your reviews cite.

• Google Drive — find and read Drive files. Evidence: a file, or a folder. A Drive folder can be pointed at whole, or the file inside it; a pinned folder is verified through its own record (Google's connector service retired its folder-contents listing, so the folder proves access to the folder — pin the file inside when the content is what matters). A typed search phrase is never evidence: the field's search finds the real file, and that file is what gets pinned.

• Box — search and read files and folders. Evidence: a file, a folder's contents, or a shared link. A Box folder can be pointed at whole, the same way a Drive folder can.

• Dropbox — browse and search Dropbox content, read a file's revision history, and list the shared links that expose it outside the account, through Dropbox's own hosted connector service.

• Notion — search and read workspace pages, now through Notion's own hosted connector service. Evidence: a page or database — paste its link or id — and the workspace user list. (Evidence authoring returned 2026-08-25, reconciled to the service's verified abilities.)

• Confluence — search and read pages in your Confluence spaces, now through Atlassian's own hosted connector service. Evidence: a page (paste its link, or give your site plus the page id), a space's page list, or your space list — each addressed by your site (for example acme.atlassian.net). The same organization-administrator setting as Jira applies.

• Egnyte — files and folders, document content, metadata, projects, comments and share links through Egnyte's own hosted connector service.

  What you approve when you connect: Egnyte's own sign-in and consent screen for its hosted connector service; the connection can read only the files and folders the signed-in Egnyte user can already access.

• Perfect Wiki — knowledge bases and their pages through Perfect Wiki's own hosted connector service.

  What you approve when you connect: Perfect Wiki's own sign-in and consent screen for its hosted connector service; the connection can read only the knowledge base you approve.

• Lumin — workspace details, templates and signature request status through Lumin's own hosted connector service.

  What you approve when you connect: Lumin's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Lumin user and can use every tool Lumin's server offers, including any that change data.

• Jotform — forms, submissions, teams and the signing status of documents through Jotform's own hosted connector service.

  What you approve when you connect: Jotform's own sign-in and consent screen for its hosted connector service, asking for read-only access; the connection acts as the signed-in Jotform user and can use every tool Jotform's server offers, including any that change data.

• Mintlify — documentation project settings, Git sources, workflows, analytics and branches through Mintlify's own hosted connector service.

  What you approve when you connect: Mintlify's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Mintlify user and can use every tool Mintlify's server offers, including any that change data.

• Contentful — entries, content types, assets, releases, spaces, environments, locales and tags through Contentful's own hosted connector service.

  What you approve when you connect: Contentful's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Contentful user and can use every tool Contentful's server offers, including any that change data.

• NetDocuments — work with legal documents and filed email in NetDocuments — keyword search across documents and email with author and date filters, reading a document's text, and saving new documents into a workspace or folder — through NetDocuments' own hosted connector service.

  What you approve when you connect: NetDocuments' own sign-in and approval screen for its hosted connector service. The connection acts as the signed-in person with no added access: their permissions, ethical walls and the repository's no-AI document rule all apply, and every search and read lands in NetDocuments' activity log.

• Wistia — work with a business video library in Wistia — folders, media and Channels, searching by name and transcript, captions, translations and audio descriptions, play and visitor statistics, webinars and registrations — through Wistia's own hosted connector service.

  What you approve when you connect: Wistia's own sign-in and approval screen for its hosted connector service. Only an account owner or manager can connect. The server can also create, change and delete media, folders, Channels, webinars and captions, and can order paid captions or dubbing, so Alchex asks before any such action runs.

What a Dropbox access review does and does not cover. Shared links are listed as the connected account owns them — a link another member created for the same file is not visible to this connection, so treat the list as a lower bound on external exposure rather than the complete picture. The connection does not list who is a member of a file or folder; check membership in Dropbox itself. Dropbox's search runs on an index that catches up after a change, so a just-added file can be missing from a search that finds everything else — Alchex says so in the answer rather than letting an empty result read as proof that nothing is there.

Not every connected system can produce evidence yet. Gmail cannot: writing a fetch means naming the exact call and the exact details it needs, and for Gmail those details are not yet known here — so rather than guess at a mailbox, Alchex says so and asks you to point at another source. You are always told which case you are in.

Tickets & Projects

Change-management and incident trails.

• Jira — issues and projects, now through Atlassian's own hosted connector service. Evidence: an issue (paste its link, or give your site plus the issue key) and the visible-projects list, each addressed by your site (for example acme.atlassian.net). Audit-log evidence does not return: Atlassian's service offers no audit-records read, so that older evidence shape asks you to pick a different source. Your Atlassian organization's administrator controls which AI tools may connect (Administration → AI settings); if a connection is refused there, that setting — not Alchex — is the door to open.

• Asana — the work itself, through Asana's own hosted connector service. Projects, portfolios and tasks with their assignee, dates, custom fields, subtasks and comments; who is in a team; status overviews and attachments. Evidence: a project, a task, or a portfolio's status.

  What you approve when you connect: Asana's own consent screen for its hosted connector service. Asana does not split this access into permissions: the screen grants access to what the signed-in Asana user can already see and do. What the assistant then does with it follows the connection's Auto / Ask setting below, tool by tool. A connection made before this change is on Asana's older access and asks you to reconnect once.

  Two limits worth knowing. Task search is an Asana Premium feature; on a free workspace Asana refuses it, and Alchex says that is a plan limit rather than letting it read as a broken connection. And an activity stream is what Asana chose to record and keeps under your workspace's retention — an absent entry is not proof the action did not happen, which is the difference between an activity stream and an audit log.

• Linear — issues and projects, now through Linear's own hosted connector service. Evidence: an issue (paste its link or key), a project, and the team, member, document and comment lists. (Evidence authoring returned 2026-08-25, reconciled to the service's verified abilities.)

• Pylon — support issues, accounts, contacts, knowledge base articles, surveys and triggers through Pylon's own hosted connector service.

  What you approve when you connect: Pylon's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Pylon user and can use every tool Pylon's server offers, including any that change data.

• Ybug — bug and feedback reports with their logs, requests, comments and tags through Ybug's own hosted connector service.

  What you approve when you connect: Ybug's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Ybug user and can use every tool Ybug's server offers, including any that change data. Ybug offers this service on its Basic plan and above.

• Fibery — work records, documents, views, reports, automations and the workspace change history through Fibery's own hosted connector service. Evidence of how your organisation plans, tracks and changes its work.

  What you approve when you connect: Fibery's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Fibery user and can use every tool Fibery's server offers, including any that change data.

• Todoist — tasks, projects, comments, collaborators and the activity log through Todoist's own hosted connector service. Evidence for who is working on what and what was completed.

  What you approve when you connect: Todoist's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Todoist user and can use every tool Todoist's server offers, including any that change data.

• Unthread — customer satisfaction surveys, their analytics and responses through Unthread's own hosted connector service. Evidence for how customers rate the support they receive.

  What you approve when you connect: Unthread's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Unthread user and can use every tool Unthread's server offers, including any that change data.

• Jam — bug recordings with their console logs, network requests, user events and metadata, plus folders and members, through Jam's own hosted connector service.

  What you approve when you connect: Jam's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Jam user and can use every tool Jam's server offers, including any that change data.

• ClickUp — tasks, lists, spaces, docs, comments and time entries through ClickUp's own hosted connector service.

  What you approve when you connect: ClickUp's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in ClickUp user and can use every tool ClickUp's server offers, including any that change data.

• Trello — boards, lists, cards, members and activity through Trello's own hosted connector service.

  What you approve when you connect: Trello's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Trello user and can use every tool Trello's server offers, including any that change data.

• Help Scout — customer conversations with their threads, tags and custom fields, customer profiles, inboxes and saved replies, users and teams, workflows and reports through Help Scout's own hosted connector service. New connections are read-only; help-centre (Docs) articles are available only when the person adds a Docs API key at sign-in.

  What you approve when you connect: Help Scout's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Help Scout user and reads only what that user can already see. It needs a Help Scout plan with API access (Standard, Plus or Pro); reports need Plus or Pro. Help-centre (Docs) tools work only if the person pastes a separate Docs API key on the sign-in page. Connections created now are read-only; a small number of accounts from the beta kept write tools, so keep any write tools on approval.

• monday.com — boards, items, their activity log and comments, docs, automations, sprints and the people and teams in the account through monday.com's own hosted connector service.

  What you approve when you connect: monday.com's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in monday.com user and can use every tool monday.com's server offers, including any that change data.

• Qase — work with software test management in Qase — projects, test cases and suites, test plans, test runs and their results, and defects — through Qase's own hosted connector service.

  What you approve when you connect: Qase's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's Qase access; the hosted server comes with Qase's paid plans.

Jira and Confluence are separate cards; connecting either asks only for that product's read permissions on Atlassian's consent screen. Workspaces that connected the older combined Atlassian (Jira + Confluence) card before the split keep their connection listed; reconnecting it goes through Atlassian's hosted connector service like the product cards, and it no longer appears for new connections.

Code & Change

• GitHub — organization members, teams, and the org audit log.

• GitLab — connected through GitLab's own hosted connector service. Evidence: a merge request, pasted by its link. Group, membership and audit-event evidence does not return: GitLab's service reads issues, merge requests and pipelines only, so those older evidence shapes ask you to pick a different source.

• Hugging Face — the models, datasets and Spaces your organisation keeps on Hugging Face, with their model cards and files, through Hugging Face's own hosted connector service. Evidence for an inventory of the AI models you use and their documentation.

  What you approve when you connect: Hugging Face's own sign-in and consent screen; Alchex asks only to read your profile and repositories.

• LaunchDarkly — projects, environments, feature flags and their health, segments, approval requests, release policies, members and the change history through LaunchDarkly's own hosted connector service.

  What you approve when you connect: LaunchDarkly's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in LaunchDarkly user and can use every tool LaunchDarkly's server offers, including any that change data.

• DevCycle — feature flags, variables, each flag's change history and evaluation counts through DevCycle's own hosted connector service. Evidence for how your organisation controls and changes what runs in production.

  What you approve when you connect: DevCycle's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in DevCycle user and can use every tool DevCycle's server offers, including any that change data.

• Replicate — models, predictions, deployments, collections and account details through Replicate's own hosted connector service.

  What you approve when you connect: Replicate's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Replicate user and can use every tool Replicate's server offers, including any that change data.

Cloud & Infrastructure

• Supabase — organizations, projects, tables, migrations, extensions, edge functions, logs and Supabase's own security and performance advisors through Supabase's own hosted connector service.

  What you approve when you connect: Supabase's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Supabase user and can use every tool Supabase's server offers, including any that change data.

• Neon — projects, branches, compute endpoints, database roles, project members and permissions, snapshots and table schemas through Neon's own hosted connector service.

  What you approve when you connect: Neon's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Neon user and can use every tool Neon's server offers, including any that change data.

• Railway — projects, services and feature flags through Railway's own hosted connector service. Evidence for what runs where, and how releases are controlled.

  What you approve when you connect: Railway's own sign-in and consent screen for its hosted connector service, where you choose which workspaces and projects the connection can reach.

• Cloudflare — the account's configuration and change history through Cloudflare's own hosted connector service: zones, DNS records, firewall and WAF rules, TLS certificates, Zero Trust access policies, members, and the audit log of who changed what and when. Evidence: the settings in force and the change log for a period.

  What you approve when you connect: Cloudflare's own sign-in and consent screen for its hosted connector service. The connection can do what the signed-in Cloudflare user can do.

• Control Plane — workloads, deployments, logs, metrics, traces, audit events and quotas through Control Plane's own hosted connector service. Evidence for how your infrastructure is run, monitored and changed.

  What you approve when you connect: Control Plane's own sign-in and consent screen for its hosted connector service; you choose which organisations the connection may access, and it can use every tool Control Plane's server offers within them, including any that change data.

• Heroku — the apps in a Heroku account and their platform settings through Heroku's own hosted connector service.

  What you approve when you connect: Heroku's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Heroku user and can use every tool Heroku's server offers, including any that change data.

• PlanetScale — organizations, databases, branches, schemas and query insights through PlanetScale's own hosted connector service.

  What you approve when you connect: PlanetScale's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in PlanetScale user and can use every tool PlanetScale's server offers, including any that change data.

• Equinix Fabric — inspect and, within the permission level chosen at sign-in, change the Equinix Fabric interconnection estate — connections, ports, Cloud Routers, routing protocols and route filters, networks, service profiles and tokens, telemetry streams, metros, projects and pricing — through Equinix's own hosted connector service (public preview).

  What you approve when you connect: Equinix's own sign-in with Customer Portal credentials, where the person picks a viewer, operator or manager permission level. The connection acts as that user, and the server publishes no delete tools.

• Vercel — teams, projects, deployments with their build logs, runtime logs and errors, web analytics and toolbar comment threads through Vercel's own hosted connector service.

  What you approve when you connect: Vercel's own sign-in and consent screen, reached through Vercel Connect; the connection acts as the signed-in Vercel user and can use every tool Vercel's server offers, including any that change data.

• Remote.It — work with the device and service inventory, online status, connections, sharing and usage of an organisation's remotely accessed devices in Remote.It — through Remote.It's own hosted connector service.

  What you approve when you connect: Remote.It's own sign-in and consent screen for its hosted connector service, where the customer can limit the connection, for example to read-only access to devices without connecting or making changes. Organisation roles and device permissions apply to every call, and destructive actions such as deleting devices or running scripts need an explicit confirmation.

• DigitalOcean — work with Droplets, Kubernetes, apps, databases, Spaces, networking and firewalls, volumes, accounts and insights through DigitalOcean's own hosted connector service, a router that finds, describes and runs tools across DigitalOcean's services. Evidence for which servers, databases and storage exist and how the network is fenced.

  What you approve when you connect: DigitalOcean's own sign-in and consent screen for its hosted connector service (OAuth through the browser); the connection acts as the signed-in DigitalOcean user and can use every tool DigitalOcean's server offers, including any that change data.

Monitoring & Security

• Datadog — monitors, incidents, metrics, logs and dashboards through Datadog's own hosted connector service.

  What you approve when you connect: Datadog's own sign-in and consent screen; there is no key to paste. The connection acts as the signed-in Datadog user and can use every tool Datadog's server offers, including any that change data.

• Sentry — issues and projects from your Sentry organization, now through Sentry's own hosted connector service. Evidence: an issue (paste its link, or give the organization slug plus the issue id), and the organization and project lists. The release list retired with Sentry's own connector update — a release is no longer offered as evidence. Reconnecting an existing Sentry connection asks for a fresh consent — the old installation-based link is retired.

• incident.io — incidents with their timelines and post-mortems, follow-ups, alerts, escalations, on-call schedules and response-time metrics through incident.io's own hosted connector service. Evidence for how your organisation detects, handles and learns from incidents, and for the incident reports some laws require.

  What you approve when you connect: incident.io's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in incident.io user and can use every tool incident.io's server offers, including any that change data. incident.io offers this service on its Team, Pro and Enterprise plans.

• Rootly — incidents, alerts, on-call shifts and handoffs through Rootly's own hosted connector service. Evidence for how your organisation detects, handles and learns from incidents, and for the incident reports some laws require.

  What you approve when you connect: Rootly's own sign-in and consent screen; Alchex asks only for read permissions on incidents, alerts and on-call schedules.

• Braintrust — projects, experiments, datasets, monitoring views, automations and recorded patterns through Braintrust's own hosted connector service.

  What you approve when you connect: Braintrust's own sign-in and consent screen for its hosted connector service; the connection acts with the permissions of the signed-in Braintrust user. Alchex only calls tools that read.

• LangSmith — projects, traces, prompts, datasets, experiments and usage through LangSmith's own hosted connector service.

  What you approve when you connect: LangSmith's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in LangSmith user and can use every tool LangSmith's server offers, including any that change data.

• Grafana Cloud — dashboards, folders, data sources, incidents, on-call schedules, teams and roles through Grafana Cloud's own hosted connector service.

  What you approve when you connect: Grafana Cloud's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Grafana Cloud user and can use every tool Grafana Cloud's server offers, including any that change data.

• Memfault — devices, issues, metrics and projects through Memfault's own hosted connector service.

  What you approve when you connect: Memfault's own sign-in and consent screen for its hosted connector service; the connection can read only the organization and project the signed-in Memfault user picks.

• Raygun — applications, error groups and occurrences, deployments, backend performance issues, sessions and pages through Raygun's own hosted connector service. Evidence for which errors and slowdowns users hit, and which release introduced them.

  What you approve when you connect: Raygun's own sign-in and consent screen for its hosted connector service; the connection reads one Raygun plan and only what the signed-in Raygun user can already see.

• Better Stack — monitors, incidents, on-call schedules, status pages, logs, metrics and tracked errors through Better Stack's own hosted connector service.

  What you approve when you connect: Better Stack's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Better Stack user and can use every tool Better Stack's server offers, including any that change data.

• Cisco ThousandEyes — tests, events, alerts, outages, agents, network paths and dashboards through Cisco ThousandEyes's own hosted connector service.

  What you approve when you connect: Cisco ThousandEyes's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Cisco ThousandEyes user and can use every tool Cisco ThousandEyes's server offers, including any that change data.

• PowerTrack — work with the solar and energy sites monitored in PowerTrack — site details and production data, hardware under each site, alerts, weather and forecast, charts and archived readings, images and environmental equivalents — and update an alert's status or notes, through Stem's own hosted connector service.

  What you approve when you connect: Stem's own sign-in and consent screen (login.stem.eu for the European server) granting access to the PowerTrack Public API. The account must already have Public API access, and the connection follows that account's permissions.

• UptimeRobot — work with uptime monitoring in UptimeRobot — monitors and their uptime and response times, incidents and their comments, maintenance windows, monitor groups, public status pages and their announcements — through UptimeRobot's own hosted connector service.

  What you approve when you connect: UptimeRobot's own sign-in and approval screen for its hosted connector service, where the person chooses read-only or full access. The connection acts on the signed-in account; the server offers no delete actions.

• Sitelemetry — work with website audits in Sitelemetry — security checks (DNS, email, TLS, headers, HTTPS, detected technology), technical SEO, AI-search readiness, static accessibility review against WCAG 2.2, performance and Core Web Vitals, and analytics, tag and consent setup, each with severity, evidence and a recommended fix — through Sitelemetry's own hosted connector service.

  What you approve when you connect: Sitelemetry's own sign-in and approval screen for its hosted connector service. The connection can only run audits and read their results, with no write or delete tools. It works within the signed-in account's plan and usage allowance, deeper security checks need the site to be verified as yours, and its checks can show up in the audited site's logs or alerts.

• Domotz — work with network device inventory, uptime and performance, network topology, configuration backups and their changes, alerts and alert rules, and the account audit log in Domotz — through Domotz's own hosted connector service.

  What you approve when you connect: Domotz's own sign-in and consent screen for its hosted connector service. Tools are read-only until an account administrator turns on write actions, and Domotz records every action in its audit log. It needs a Domotz account (priced per collector).

• Instatus — work with public status pages in Instatus — status pages and their components, incidents and their updates, and scheduled maintenance — through Instatus's own hosted connector service.

  What you approve when you connect: Instatus's own sign-in and approval screen for its hosted connector service, where the person picks read-only or read and write access; choose read only. What the connection reaches follows the signed-in person's Instatus access.

Communication

• Slack — channels, workspace members, and messages you can search, now through Slack's own hosted connector service. A Send a Slack message step does not send yet (see the top of this page). Reconnecting asks for your own read permissions alongside the workspace's — both on Slack's consent screen. Evidence: a channel's member list and a member's profile. Whole-workspace channel and member lists do not return: Slack's service answers name searches, not full listings, so those older evidence shapes ask you to pick a different source.

• Gmail — search and read messages in the connected mailbox. Limited availability: Google classifies mail access as a restricted permission and requires an independent security assessment before an app may offer it broadly, so Gmail currently connects only for accounts we have registered for testing. Ask us to add yours.

• Fellow.ai — meetings with their summaries, transcripts, participants, agendas and action items through Fellow.ai's own hosted connector service. Evidence of how your organisation holds its meetings, records decisions and follows up on them.

  What you approve when you connect: Fellow.ai's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Fellow user and can use every tool Fellow's server offers, including any that change data. A Fellow workspace admin must have allowed MCP connections.

• Krisp — meetings, notes, transcripts and action items through Krisp's own hosted connector service.

  What you approve when you connect: Krisp's own sign-in and consent screen for its hosted connector service; the connection can read only the meetings the signed-in Krisp user can already see.

• Quo — message history, call history and voicemail transcripts through Quo's own hosted connector service. Evidence for how your organisation communicates with customers.

  What you approve when you connect: Quo's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Quo user and can use every tool Quo's server offers, including any that change data.

• Wavix — messages, call records, recordings, verification events, numbers, SIP trunks and billing through Wavix's own hosted connector service. Evidence for what communications ran through the account and what they cost.

  What you approve when you connect: Wavix's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Wavix user and can use every tool Wavix's server offers, including any that change data.

• Customer.io — automations, segments, people, message content and delivery metrics through Customer.io's own hosted connector service.

  What you approve when you connect: Customer.io's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Customer.io user and can use every tool Customer.io's server offers, including any that change data.

• Bird — work with email, SMS, WhatsApp, voice and verify, sender domains, templates, suppressions, contacts, audiences and preferences through Bird's own hosted connector service, which can also send messages and change records. Evidence for who may be messaged and which opt-outs and suppressions are held.

  What you approve when you connect: Bird's own sign-in and consent screen for its hosted connector service, where you choose which workspace or organization permissions to delegate; the connection acts as the signed-in Bird user and can use every tool Bird's server offers, including any that send messages or change data.

HR & People

• Ashby — candidates, applications, jobs, openings, interview plans and hiring pipelines through Ashby's own hosted connector service.

  What you approve when you connect: Ashby's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Ashby user and can use every tool Ashby's server offers, including any that change data.

• Workable — jobs, candidates and their activity, offers, requisitions, members, employees, time off, time entries and review cycles through Workable's own hosted connector service.

  What you approve when you connect: Workable's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Workable user and can use every tool Workable's server offers, including any that change data.

• Shapes — employees and reporting lines, profile change history, performance reviews, time off, surveys, attendance, and the knowledge base and helpdesk through Shapes' own hosted connector service.

  What you approve when you connect: Shapes' own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Shapes user and can use every tool Shapes's server offers, including any that change data.

• Factorial — attendance (clock in and out), tasks, time off and employee lookup, and, on a plan that includes Factorial One, HR policies, contracts, reports, the knowledge base and performance reviews through Factorial's own hosted connector service.

  What you approve when you connect: Factorial's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Factorial user under that user's own permissions, and it can use every tool Factorial's server offers, including ones that change data such as clocking in, creating tasks and requesting time off.

• Greenhouse — work with jobs, candidates, applications, interview stages, scorecards, rejection reasons and users through Greenhouse's own hosted connector service. Evidence for how hiring decisions are recorded and who made them.

  What you approve when you connect: Greenhouse's own sign-in and consent screen for its hosted connector service (OAuth with PKCE, open beta, Core, Plus or Pro tier). A Site Admin must first add the client in Dev Center > MCP Access; the connection is limited to what the signed-in user can see and to the scopes the admin enables. The default scopes are read-only, but an admin can enable scopes that create, edit or manage jobs and applications.

• Gusto — payroll runs, employees, contractors, payment deadlines and tax liabilities, within the data categories the admin allows through Gusto's own hosted connector service.

  What you approve when you connect: Gusto's own sign-in and consent screen for its hosted connector service; a primary or global admin connects it and chooses the data categories to allow, and the connection can use every tool Gusto's server offers, including ones that change data such as logging time, onboarding people and running payroll.

• Leapsome — employees, teams, goals, feedback, reviews, surveys, learning, absences and people analytics through Leapsome's own hosted connector service.

  What you approve when you connect: Leapsome's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Leapsome user and can use every tool Leapsome's server offers, including any that change data.

• Day Off — leave balances, leave requests, team information and the team calendar, and the submitting of leave requests, through Day Off's own hosted connector service.

  What you approve when you connect: Day Off's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Day Off user and can use every tool Day Off's server offers, including any that change data. The server can also submit leave requests, so keep its write tools on approval.

• Teachfloor — courses, modules, learners, cohorts, enrollments, certificates, automations and learning analytics through Teachfloor's own hosted connector service.

  What you approve when you connect: Teachfloor's own sign-in and consent screen for its hosted connector service; the connection acts with the role of the signed-in Teachfloor user. The server can also create courses, enroll learners and build automations, so keep its write tools on approval.

• Vacation Tracker — work with people, leave and time-off-in-lieu, balances and quotas, public holidays, and leave policies per location in Vacation Tracker — through Vacation Tracker's own hosted connector service.

  What you approve when you connect: Vacation Tracker's own sign-in and consent screen for its hosted connector service. Each call is limited to the signed-in user's Vacation Tracker role, and the server also offers write tools (booking, approving and editing leave, changing settings) that are recorded in its user log as made by the AI assistant. It needs a Vacation Tracker account on a paid plan.

Finance & Payments

• Stripe — the Stripe account's details and its payment metrics, and search Stripe's own documentation through Stripe's own hosted connector service.

  What you approve when you connect: Stripe's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Stripe user and can use every tool Stripe's server offers, including any that change data.

• Mercury — accounts, balances, statements, transactions, cards, recipients, users, approval requests and invoices through Mercury's own hosted connector service.

  What you approve when you connect: Mercury's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Mercury user and can use every tool Mercury's server offers, including any that change data.

• Brex — users, departments, cards, spend limits, expenses, bank accounts, vendors, accounting records and travel through Brex's own hosted connector service.

  What you approve when you connect: Brex's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Brex user and can use every tool Brex's server offers, including any that change data.

• Digits — businesses, transactions, departments, locations, categories and users through Digits' own hosted connector service.

  What you approve when you connect: Digits' own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Digits user and can use every tool Digits's server offers, including any that change data.

• Privacy.com — virtual cards with their spend limits and states, and the transactions on them, through Privacy.com's own hosted connector service. Evidence for who can spend, on which cards and limits.

  What you approve when you connect: Privacy.com's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Privacy.com user and can use every tool Privacy.com's server offers, including any that change data. Privacy.com offers this service on its paid plans.

• GoCardless — payments, customers, mandates, subscriptions, payouts, refunds and events through GoCardless's own hosted connector service.

  What you approve when you connect: GoCardless's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in GoCardless user and can use every tool GoCardless's server offers, including any that change data.

• Paddle — products, prices, customers, subscriptions and transactions in a Paddle billing account through Paddle's own hosted connector service.

  What you approve when you connect: Paddle's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Paddle user and can use every tool Paddle's server offers, including any that change data.

• PayPal — invoices and transaction and payment records in a PayPal business account through PayPal's own hosted connector service.

  What you approve when you connect: PayPal's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in PayPal user and can use every tool PayPal's server offers, including any that change data.

• Ramp — transactions, vendors, accounting categories, departments, reimbursements, treasury balances and the org chart through Ramp's own hosted connector service.

  What you approve when you connect: Ramp's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Ramp user and can use every tool Ramp's server offers, including any that change data.

• Carta — work with the private-capital records kept in Carta — fund NAV, cash flows, capital accounts and valuations, cap table ownership, vesting, 409A valuations, financing history and exit waterfalls, and CRM deal pipeline, LP profiles and meeting logs — through Carta's own hosted connector service.

  What you approve when you connect: Carta's own sign-in and consent screen for its hosted connector service. The vendor says access follows the permissions the person already holds in Carta; its sign-in offers read and read-write scopes for firms, companies and CRM.

• Qonto — work with accounts, cards, transactions and statements, attachments, clients, invoices, payment links and requests through Qonto's own hosted connector service, which can also create cards, change card limits and status, and draft and send client invoices. Evidence for who holds cards, how money moved and which invoices and receipts back it.

  What you approve when you connect: Qonto's own sign-in and consent screen for its hosted connector service; owners, admins and accountants can connect by default, managers and employees once an owner or admin enables Qonto MCP for the organization; the connection acts as the signed-in Qonto user and can use every tool Qonto's server offers, including any that change data.

• Sumsub — work with identity verification and anti-money-laundering checks in Sumsub — applicants and their verification status, checks and review results, and transaction monitoring alerts — through Sumsub's own hosted connector service.

  What you approve when you connect: Sumsub's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's Sumsub role, which needs the Use MCP server permission an admin grants.

CRM & Marketing

• Klaviyo — account details, campaigns, flows, lists, segments and event metrics through Klaviyo's own hosted connector service.

  What you approve when you connect: Klaviyo's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Klaviyo user and can use every tool Klaviyo's server offers, including any that change data.

• Close — leads, contacts, opportunities, activities, notes, tasks, workflows and the people, roles and groups in the organization through Close's own hosted connector service.

  What you approve when you connect: Close's own sign-in and consent screen for its hosted connector service, asking only for read access; the connection acts as the signed-in Close user and can use every tool Close's server offers, including any that change data.

• Clarify — companies, people, deals, meetings, tasks, comments, lists, campaigns and agent runs in the workspace through Clarify's own hosted connector service.

  What you approve when you connect: Clarify's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Clarify user and can use every tool Clarify's server offers, including any that change data.

• Attio — CRM records, lists, notes, tasks and comments, and who in the workspace owns them, through Attio's own hosted connector service. Evidence for which customers and partners your organisation tracks and how relationships are followed up.

  What you approve when you connect: Attio's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Attio user and can use every tool Attio's server offers, including any that change data.

• Outreach — accounts, prospects, opportunities, sequences, tasks, users, teams, recorded meetings and emails through Outreach's own hosted connector service.

  What you approve when you connect: Outreach's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Outreach user and can use every tool Outreach's server offers, including any that change data.

• Sybill — sales conversations and meetings, deals and accounts through Sybill's own hosted connector service. Evidence for what was discussed and agreed with customers, and who took part.

  What you approve when you connect: Sybill's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Sybill user and can use every tool Sybill's server offers, including any that change data.

• Givebutter — analyze fundraising campaigns and explore supporter data held in Givebutter, a nonprofit fundraising platform, through Givebutter's own hosted connector service.

  What you approve when you connect: Givebutter's own sign-in and consent screen for its hosted connector service. The vendor says connecting is optional and data handling inside the AI tool follows that tool's own policies.

Data & Analytics

• PostHog — error-tracking issues, product and web analytics, logs and the data schema through PostHog's own hosted connector service. Evidence for which errors users hit and how the product behaves in use.

  What you approve when you connect: PostHog's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in PostHog user and can use every tool PostHog's server offers, including any that change data.

• Airtable — workspaces, bases, tables, views, records, interface pages and automations through Airtable's own hosted connector service.

  What you approve when you connect: Airtable's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Airtable user and can use every tool Airtable's server offers, including any that change data.

• ClickHouse Cloud — organizations, services, backups, ClickPipes, database and table structure, and cost data through ClickHouse Cloud's own hosted connector service.

  What you approve when you connect: ClickHouse Cloud's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in ClickHouse Cloud user and can use every tool ClickHouse Cloud's server offers, including any that change data.

• MotherDuck — databases, tables, views, columns, shares and macros through MotherDuck's own hosted connector service.

  What you approve when you connect: MotherDuck's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in MotherDuck user and can use every tool MotherDuck's server offers, including any that change data.

• Atlan — data assets, their metadata, owners, tags, users and groups through Atlan's own hosted connector service.

  What you approve when you connect: Atlan's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Atlan user and can use every tool Atlan's server offers, including any that change data.

• Amplitude — charts, dashboards, experiments, feature flags, the event tracking plan and data-warehouse import and export jobs through Amplitude's own hosted connector service. Evidence for what your organisation measures about its product and how that data is governed.

  What you approve when you connect: Amplitude's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Amplitude user and can use every tool Amplitude's server offers, including any that change data. Workspace admins can switch this service off in Amplitude's organisation settings.

• Pendo — applications, pages, features, guides, surveys, accounts, AI agent analytics and feedback through Pendo's own hosted connector service.

  What you approve when you connect: Pendo's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Pendo user and can use every tool Pendo's server offers, including any that change data.

• Databox — work with accounts, data sources, datasets, ingestion history and metrics through Databox's own hosted connector service, which can also create, update and delete data sources and datasets. Evidence for which systems feed your reporting and how fresh the data is.

  What you approve when you connect: Databox's own sign-in and consent screen (OAuth 2.0) for its hosted connector service. Databox MCP needs an active paid plan or the free trial; free plans must upgrade. The connection can create, update and delete data sources and datasets as well as read, within what the signed-in Databox user is permitted.

• Great Question — research studies, sessions, transcripts, insights, consent forms and teams through Great Question's own hosted connector service.

  What you approve when you connect: Great Question's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Great Question user and can use every tool Great Question's server offers, including any that change data.

• Hex — work with projects, notebook cells, run results, analysis threads and data connections through Hex's own hosted connector service, which can also create projects, create, edit and delete cells and run notebooks. Evidence for which analyses exist and which data sources they read.

  What you approve when you connect: Hex's own sign-in and consent screen for its hosted connector service (Team or Enterprise plan; Explorer role or higher). The connection can start threads and, for users with the Editor role, create projects and create, edit, delete and run cells on projects they can edit.

• Honeydew Semantic Layer — work with the semantic model, warehouse tables, agents, context items and query history through Honeydew's own hosted connector service, which can also import tables, create and delete model objects, and create, update and delete agents and context items.

  What you approve when you connect: Honeydew's own sign-in and consent screen (OAuth) for its hosted connector service; the connection can create, change and delete semantic model objects, agents and context items as well as read, within what the signed-in Honeydew user is permitted.

• Omni Analytics — dashboards and apps, the saved queries behind them, model branches and saved skills through Omni's own hosted connector service.

  What you approve when you connect: Omni's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Omni user and can use every tool Omni's server offers, including any that change data.

• Apaleo — availability and rates, reservations, folios, guest profiles, occupancy and revenue figures, and daily arrivals and departures through Apaleo's own hosted connector service.

  What you approve when you connect: Apaleo's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Apaleo user and can use every tool Apaleo's server offers, including any that change data.

• Bluestone PIM — products, variants, attributes, catalogs and categories, assets, relations, completeness scores and the change history of each record through Bluestone PIM's own hosted connector service.

  What you approve when you connect: Bluestone's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Bluestone user and can use every tool Bluestone's server offers, including any that change data. The server can also create, change, archive and delete records, so keep its write tools on approval.

• Metry — work with energy and utility meter data in Metry — consumption and readings for electricity, district heating and cooling, gas and water, solar and heat-pump production, EV charging and climate and air-quality sensors, with each meter's details and the property and building structure — through Metry's own hosted connector service.

  What you approve when you connect: Metry's own sign-in and consent screen for its hosted connector service. The connection is read-only and sees exactly the meters and properties the signed-in Metry account can already see; it can create, change or delete nothing.

• SurveyMonkey — search surveys and read their content, details and responses through SurveyMonkey's own hosted connector service, which can also create and edit surveys and create web-link collectors to share them. Evidence for which surveys were run, how they were shared and what respondents answered.

  What you approve when you connect: SurveyMonkey's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in SurveyMonkey user and can use every tool SurveyMonkey's server offers, including any that change data.

Legal & Signatures

• PandaDoc — documents, templates and their signature status through PandaDoc's own hosted connector service.

  What you approve when you connect: PandaDoc's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in PandaDoc user and can use every tool PandaDoc's server offers, including any that change data.

Design & Whiteboards

• Miro — boards and the items on them through Miro's own hosted connector service.

  What you approve when you connect: Miro's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Miro user and can use every tool Miro's server offers, including any that change data.

• Whimsical — diagrams, boards and docs in your Whimsical workspace, and search across them, through Whimsical's own hosted connector service.

  What you approve when you connect: Whimsical's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Whimsical user and can use every tool Whimsical's server offers, including any that change data.

• Eraser — files, documents, diagrams and folders, with search, through Eraser's own hosted connector service. Evidence for which architecture and design documentation exists and what it shows.

  What you approve when you connect: Eraser's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Eraser user and can use every tool Eraser's server offers, including any that change data.

• Lucid — diagrams and documents the signed-in user can open, including titles, content, comments and metadata through Lucid's own hosted connector service.

  What you approve when you connect: Lucid's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Lucid user and can use every tool Lucid's server offers, including any that change data.

• Frontify — brands, brand guidelines and their pages, libraries, projects, assets with their copyright and licence information, and templates through Frontify's own hosted connector service.

  What you approve when you connect: Frontify's own sign-in and consent screen for its hosted connector service. A Frontify account admin must first enable the MCP server under Applications > Public Apps. The default pack (discovery) is read-only: it does not make any changes to Frontify data.

• Cloudinary — review a digital asset library in Cloudinary — images, videos and files organised in folders and tags — through Cloudinary's own hosted connector service.

  What you approve when you connect: Cloudinary's own sign-in and approval screen for its hosted connector service, where each person picks the product environment (cloud) to connect and the asset management, upload and media generation permissions to grant. The server can also upload, rename and delete assets, so Alchex asks before any such action runs.

Operations & Logistics

No app in this category is offered yet.

• Facilio — work orders, service requests, assets, tenants, purchase orders and inventory through Facilio's own hosted connector service.

  What you approve when you connect: Facilio's own sign-in and consent screen for its hosted connector service; an admin must first enable Facilio MCP in the workspace, the connection stays inside the signed-in user's Facilio permissions, and it can use every tool Facilio's server offers, including ones that change data (Facilio says destructive actions need the user's confirmation).

• Flexport — shipments, container and customs status, contract and spot freight rates, quote requests, ports and addresses through Flexport's own hosted connector service.

  What you approve when you connect: Flexport's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Flexport user and can use every tool Flexport's server offers, including any that change data.

• Harvest — work with time entries, projects, clients, tasks, team assignments, invoices, expenses and project budgets through Harvest's own hosted connector service, which can start and stop timers, log, edit and delete time entries, and create draft invoices. Evidence for how time, billing and budgets are tracked.

  What you approve when you connect: Harvest's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Harvest user and can start timers, log, edit and delete time entries, manage projects, clients, tasks and expenses and create draft invoices, within that user's Harvest role.

• Productive — projects, tasks, time entries, bookings, invoices, expenses, people and reports through Productive's own hosted connector service.

  What you approve when you connect: Productive's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Productive user and can use every tool Productive's server offers, including any that change data.

• Syncro — tickets, managed devices, monitoring alerts and customers through Syncro's own hosted connector service.

  What you approve when you connect: Syncro's own sign-in and consent screen for its hosted connector service; the connection acts as the signed-in Syncro user and can use every tool Syncro's server offers, including any that change data.

• Huntress — protected endpoints, incident reports, escalations, remediations and organizations through Huntress's own hosted connector service.

  What you approve when you connect: Huntress's own sign-in page for its hosted connector service, where the customer enters a Huntress API key and API secret key; access is read-only and covers only what that key pair can already see.

• TimeCamp — time entries, projects, tasks, tags and users through TimeCamp's own hosted connector service.

  What you approve when you connect: TimeCamp's own sign-in page, where the customer signs in with their TimeCamp account (OAuth with PKCE); access follows that account's permissions and covers time entries, projects, tasks, tags and users.

• MangoApps Workforce — scheduling, leave, attendance, training, safety incidents and inspections and service desk records through MangoApps's own hosted connector service.

  What you approve when you connect: MangoApps's own sign-in page, where the customer picks their MangoApps tenant, signs in through the browser and approves access scope by scope; the connection acts with that person's own permissions.

• MarginEdge — vendors, vendor items, invoices and orders with line items, products, recipes with ingredients and inventory counts through MarginEdge's own hosted connector service.

  What you approve when you connect: MarginEdge's own sign-in and consent screen, where an active MarginEdge Admin or Franchisee Admin signs in and approves access; access is read-only and covers only the locations that user can already see.

• Resource Guru — availability, time off, utilisation and projects over budget through Resource Guru's own hosted connector service.

  What you approve when you connect: Resource Guru's own OAuth sign-in and consent screen, shown after an administrator has enabled the MCP Server in Resource Guru's settings; the connection is read-only.

• Constructable — drawings, RFIs, submittals, daily logs, change events, financials and quality lists through Constructable's own hosted connector service.

  What you approve when you connect: Constructable's own sign-in page, followed by a Confirm step that grants access. The server can also write, for example create a log entry, so keep write tools set to ask for approval.

• Wix — a Wix account's sites and their online-store business data, such as orders, inventory and shipping, through Wix's own hosted connector service.

  What you approve when you connect: Wix's own sign-in and consent screen for its hosted connector service; the connection can reach only the sites the signed-in Wix user can already manage. The server can also create, change and publish sites and write site data, so keep its write tools on approval.

• Eventtia — events, attendees, registration questions, sessions, workshops, speakers, check-ins and payments through Eventtia's own hosted connector service.

  What you approve when you connect: Eventtia's own sign-in screen, where you sign in with your Eventtia account; the connection acts with that user's Eventtia role and can use every tool Eventtia's server offers, including any that change data. The server can also create, change and delete records such as events, attendees, sessions, checkpoints and payments, so keep its write and delete tools on approval.

• dala.care — work with the home care records kept in dala.care — offices and their staff, care recipient profiles, care plans, visits and caregiver assignments, caregiver availability and daily office summaries — through dala's own hosted connector service.

  What you approve when you connect: dala.care's own OAuth sign-in for its hosted connector service. The connection acts as the signed-in dala user, and the vendor says access is limited by the permissions the agency has set.

• SimpleDock — work with dock appointment scheduling in SimpleDock — locations and doors, appointment types and open slots, appointments with their status, arrival and check-in, per-location analytics, and location setup — through SimpleDock's own hosted connector service.

  What you approve when you connect: SimpleDock's own sign-in and approval screen for its hosted connector service. The connection acts as the signed-in person, so it can do only what their role (dock staff, scheduler or admin) allows.

• Uku — work with an accounting firm's practice in Uku — clients, recurring tasks and deadlines, checklists, time entries, client folders and documents, invoices and contracts, reports and the activity log — through Uku's own hosted connector service.

  What you approve when you connect: Uku's own sign-in and approval screen for its hosted connector service. The connection acts as the signed-in person within one firm, so it can do only what their permissions allow; money data (invoices, contracts, prices) is a separate box on that screen.

• ProjectTeam — work with construction and capital projects in ProjectTeam — requests for information, punch list items, field reports, directives, contract exhibits and the project's own custom forms — through ProjectTeam's own hosted connector service.

  What you approve when you connect: ProjectTeam's own sign-in and approval screen for its hosted connector service. The connection acts as the signed-in person, so it sees and changes only what their project, form and field permissions allow, and each change is logged under their name.

• Apicbase — work with a food business's back of house in Apicbase — recipes with allergens and nutrition, ingredients and suppliers, stock and waste, purchase orders and deliveries, production plans, HACCP critical control points and task records, and the audit log — through Apicbase's own hosted connector service.

  What you approve when you connect: Apicbase's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's Apicbase roles and outlets; the server can also change and delete records, so Alchex asks before any such action runs.

• Hospitable — work with a short-term rental business in Hospitable — properties and calendars, reservations and inquiries, guest messages and reviews, transactions and payouts, owner statements, tasks and teammates, alerts, and smart locks — through Hospitable's own hosted connector service.

  What you approve when you connect: Hospitable's own sign-in and approval screen for its hosted connector service (the sign-in page sits on auth.hospitable.com). Only the account owner or a full-access teammate can connect. The connection sees the account's properties, reservations, guest messages, finances and tasks, and the server can also send guest messages, change calendars, reservations, tasks and owner statements, delete records and lock or unlock smart locks, so Alchex asks before any action that changes things.

• HMS Otel — read and manage a Turkish hotel's front office in HMS — reservations with balances and payment history, guest records (found by identity number) and who is staying now, room availability and the housekeeping board, and occupancy, arrivals, departures, forecast, cash and main courante reports — through HMS's own hosted connector service.

  What you approve when you connect: HMS's own sign-in screen, where the person enters their HMS username, password and hotel code. The connection sees only what that user is allowed to see, limited to that one hotel; the server can also create, change and cancel reservations, check guests in and out, edit guest records and mark rooms clean or dirty, so Alchex asks before any such action runs.

• TrackingTime — work with a team's time tracking in TrackingTime — time entries, projects and tasks, customers and users — through TrackingTime's own hosted connector service.

  What you approve when you connect: TrackingTime's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's TrackingTime role; the server can also create and change records, so Alchex asks before any such action runs.

• Miselup — work with a food business's kitchen records in Miselup — inventory and stock, HACCP temperature controls and checks, recipes and production orders — through Miselup's own hosted connector service.

  What you approve when you connect: Miselup's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's Miselup account; the server can also create, change and remove records, so Alchex asks before any such action runs.

• Factbird — work with a factory's production monitoring in Factbird — lines and equipment, OEE, output and speed, stops and their reasons, and shift performance — through Factbird's own hosted connector service.

  What you approve when you connect: Factbird's own sign-in and approval screen for its hosted connector service. What the connection reaches follows the signed-in person's Factbird access; the server only reads, and Factbird turns MCP on for an account on request.

• Redox — review a healthcare integration environment in Redox — audit events, message logs, connection health, alerts, credentials and who holds which role — through Redox's own hosted connector service.

  What you approve when you connect: Redox's own sign-in and approval screen for its hosted connector service, where each person picks the read and write permissions to grant, up to their own Redox role. The server can also create, change and delete configuration, so Alchex asks before any such action runs. Redox turns the server on for an organization that opts in.

• Transportial — work with transport orders, consignments, trips, vehicles and their locations, drivers, alerts, quotes, tenders and invoices in Transportial — through Transportial's own hosted connector service.

  What you approve when you connect: Transportial's own sign-in and consent screen for its hosted connector service. An administrator switches connected apps on for the platform first, and can grant view-only access; with write access the server can also create and change records.

• Genea — work with users, access groups, doors, credentials, visitors, hardware, the event log and alarms through Genea's own hosted connector service, which can also lock, unlock and lock down doors. Evidence for who can enter which doors and what the access event log shows.

  What you approve when you connect: Genea's own sign-in and consent screen for its hosted connector service; a Global Admin must first switch Genea MCP on from the Integrations page (and allow the role); the connection acts as the signed-in Genea user and can use every tool Genea's server offers, including any that change data.

Connecting

Every connector connects the same way: press Add connection, click Connect on the app, approve the consent screen in the popup, and the connection appears in your list. Several connectors now run through the vendor's own hosted connector service behind that same button — the only visible difference is whose consent screen appears, and for some vendors the sign-in registers Alchex automatically instead of using a pre-registered app. The account you approve with is the account whose access Alchex inherits — for the two admin account required connectors above, that means connecting with an admin account, or the connection will look healthy but return no directory or audit data.

There is no connector that asks you to paste an API key. Access is always something you grant on the vendor's own consent screen and can withdraw there, which means you can see exactly what Alchex was given and revoke it without going through us.

If your plan meters connections, only completed connections count — an abandoned consent popup never uses up a slot.

A server that is not in the library

If your team runs its own MCP server, or uses one from a vendor the library does not list yet, you can add it yourself. In Add connection, press Add custom connector, give it a name and the server's address, and press Continue. The next step shows the server you are about to sign in to; press Connect and the server's own sign-in screen opens, exactly as it does for an app in the library.

• The address must start with https:// and point to a public server. Addresses on a private network, or on the machine itself, are refused.
• Sign-in is the only way in. A server that asks for an API key or custom headers instead cannot be added yet.
• Only add a server you trust. Alchex has not reviewed it: the assistant will see whatever it returns, and its tools can change things in that service. Its changes start on Auto like any other connection's, except the ones it marks destructive, so set it to Ask if you want to approve each use.

A custom connector is yours like every other connection: nobody else sees it, and you rename, reconnect or remove it the same way. Many servers recognise Alchex by its published identity, so no app has to be registered with them first.

Your own account

Your connections are yours, so the account behind one is yours by construction: what you connect, you connect with your own sign-in. There is one Connect, and it gives the connection your account — there is no second step to find afterwards.

That is also why a colleague connecting something does not connect it for you. A connection someone else set up is listed for everyone, and it shows as not connected until you connect it; if you open a new account you will see the list that way, and connecting is what changes it. What that stores is yours alone: nobody else can use it, disconnecting it affects nobody else, and an administrator cannot see through it.

Once you have connected yours, it is the one that gets used. A workflow step that reads a connected source, a message a procedure posts, an app the assistant reads for you in chat — each goes out through your account, so what comes back is what you can already see and what you send carries your name.

Your chat turns use it too. Ask the assistant to read a connected app and it reads as you — and it is offered only the apps you have connected, so it can never reach a colleague's.

If you have not connected, you are asked to. Nothing falls back to somebody else's sign-in behind your back — so a read or a send stops and tells you to connect rather than quietly going out as whoever set the connection up. Connecting takes the same popup as everything else on this page, and once it is done the request goes through.

A connector that runs through the vendor's own connector service — the ones where the consent screen that opens is the vendor's rather than ours — takes your own account the same way, and for the same reason: what the workspace registered with that vendor is reused, and the account you approve with is yours. Connecting yours there does not disturb anyone else's, and it is the account your reads go out through afterwards.

Some connectors have no personal account to connect — one that signs in with a shared key, for instance — so the Your account card does not appear on them rather than offering a button that would fail. Those keep running on the workspace's connection, because that is the only account they have.

Renaming a connection

A connection's name is yours to change. Open it from the list and use Rename beside the title — type the new name and press Save or Enter, or Escape to leave it alone. This is a display name only: it renames nothing in the vendor's system, breaks no reference pointing at the connection, and takes effect everywhere the connection is listed. Useful when you connect the same product twice — Drive (Finance) and Drive (Engineering) read better than two rows called Google Drive.

You see Rename on the connections you added. On one that belongs to the workspace — made before 13 September 2026 — only an Owner or Admin does, for the same reason only they can disconnect or remove it: the change lands on everybody.

Auto or Ask: when the assistant uses an app

Each connection has a choice about how the assistant uses it, and so does each of its tools. Open the connection from the list and pick one under When the assistant uses this app:

• Auto — the assistant uses the app directly whenever your conversation needs it. This is where every connection starts.
• Ask — before each use of the app, the assistant asks you in the conversation what it wants to do there. Nothing happens in the app until you say yes; say no and nothing is done.

One tool at a time. Under Tools on the same page, every tool the connection offers has its own Auto / Ask. A tool follows the connection's choice until you set it on its own — except that a tool its app marks as destructive starts on Ask even when the connection is on Auto. For example, keep a connection on Auto but set the one tool that closes tickets to Ask, and only that tool waits for you; or set a destructive tool you trust to Auto, and it runs without asking. Changing the connection's own choice sets every tool back to where it starts. A connection checked before 12 October 2026 learns which of its tools are destructive at its next check; until then every one of its changes starts on Auto.

The choice covers that one connection's use in your conversations and nothing else: your other connections, your documents and their schedules behave exactly as before. A schedule that runs on its own has nobody to ask, so it uses the app as it always has — except a destructive tool still on Ask, which it does not run. You see the choice on the connections you added; on one that belongs to the workspace, only an Owner or Admin changes it.

Finding a connection in the list

Every connection is listed under the product's own name — the same name it carries in the catalog above. The filter box above your list matches on that name and on its category, so typing part of a product name narrows the list to it.

If you have previously seen connections listed as Custom MCP server, or found that searching for a product name returned nothing even though the connection was there, that affected connectors added most recently and is fixed. Their names and search now behave like every other connector's. No action is needed on your side — reopen Settings → Connections and the correct names appear.

From the assistant

Connecting, renaming, switching between Auto and Ask, and disconnecting all happen here, on this page. In Alchex's chat, or in your own AI assistant connected to Alchex, the assistant works inside the apps you have already connected, as you. When it cannot reach one, it says which of three things is wrong and gives you the link:

• Not connected — you have not connected that app yet. The link opens this page and starts its sign-in.
• Sign-in expired — connect it again from this page.
• Could not be reached — a momentary blip at the app's end, not a sign-in problem. Try again in a moment.

Trusting what you see

The panel is designed so a broken connection can't hide behind a green dot:

• Verified, with a time. Each connected row shows when its last real health check ran — "Verified 2h ago" means Alchex made an authenticated round-trip to the vendor and it worked, not merely that a token exists.
• Automatic re-checks. Opening the panel silently re-probes connections whose last check is stale; a dead credential flips to Needs reconnecting instead of sitting green for days.
• Test on demand. Test connection on a connection's own page runs the same authenticated probe and reports healthy, needs-reconnect, or couldn't-verify — a momentary blip is never shown as a confident result either way. The same test reads the list of tools the app offers right now, and the connection holds exactly that list from then on — a tool the app adds appears, and one it removes goes. An app that offers no tools at all reads as needs-reconnect. On a connection's own page the answer is written under the buttons and stays there: one sentence naming the connection and what to do next, with Reconnect offered right in it when that is the fix. (It used to be a message that appeared briefly and could be missed entirely, which made pressing Test feel like it did nothing.) The reason a vendor gave is never shown raw — you get the sentence, not the error code.
• New capabilities banner. When Alchex adds abilities to a connector that need permissions your original consent didn't include, the row says so and one reconnect enables them. Where no new permission is needed, new abilities simply appear.
• What a connection may do is listed on its page. Open a connection and its Tools card names every call Alchex can make through it, each with the app's own one-line description — the full extent of the access, spelled out. A tool that changes something says so; the app decides which ones only look, and one that does not say is treated as a change. The Send a Slack message step is named at the top of this page and is not on that card, because it is not a call the assistant can make by itself. If you saw this card read "No tools available yet" on a healthy connection made through a vendor's hosted connector service — Salesforce showed this — that was a display fault, not missing access, and it is fixed: reopen the page and the list appears. No reconnect is needed.

If a connection you added recently kept flipping to Needs reconnect within hours — Dropbox and Asana did this, with "Access expired and couldn't be renewed" — that was ours: the short-lived access these vendors issue was not being renewed even though your consent granted the means to renew it. It is fixed; reconnect once and the connection stays connected from then on.

Labels are retired

Earlier versions of Alchex let you name one specific thing behind a connection — a folder, a saved list — as a label, with its own CON- or EVD- code. Labels are gone: nothing creates, reads or resolves them any more.

A document does not cite a label — it cites the connection. Typing @ in a document lists the connected apps on this page, by name, and a sentence points at one of those. Nothing has to be made first. See Connectors as references.

An older chip that still points at a label keeps its stored name, so the text reads as it did, but it no longer opens anything: clicking it gives the plain "not available" page, and its popup has nothing to show. Replace it with a chip citing the connection itself.

A chip citing a connection carries a dot for whether that app is answering, and clicking it comes back here — see Connectors as references.

Settings continues to own the connection itself: test it, reconnect it, disconnect it, remove it, rename it.

Removing a connection

Remove a connection from its Configure page. Removal deletes the stored credentials immediately. Revoking Alchex's access from the vendor's side (for example, from your identity provider's app list) has the same effect — the next health check flags the connection as needing attention.