The companies behind the tools

Anthropic is an AI safety and research company and the maker of Claude. The Claude API gives programmatic access to Claude models and Claude Managed Agents. Claude Code is its command-line agent: it signs in with a Claude or Console account, or, when `ANTHROPIC_API_KEY` is set, asks you to approve that key instead.

OpenAI builds the GPT models and ChatGPT. Its API generates text and JSON that follows a schema, can call built-in tools such as web search and file search, and creates images, speech and embeddings.

Clerk is user management for developers: sign-up and sign-in with prebuilt UI components, multi-tenant organizations, enterprise SSO, subscription billing and machine-to-machine auth. Its Backend API and CLI read and manage an application's users, invitations and waitlist, so new sign-ups can start a growth workflow.

Make is a visual automation platform for building AI agents, agentic workflows and integrations without writing code. Its workflows, called scenarios, connect 3,500+ pre-built apps or any service with an API. The hosted MCP server signs in with OAuth, where you pick the organization and scopes: every active, on-demand scenario becomes a tool on any plan, and on paid plans management tools view and modify scenarios, connections, webhooks and data stores. The `make-cli` CLI and the REST API take an API token created in your Make profile; the API sends it as `Authorization: Token <token>`. `{zone_url}` is the zone your organization is hosted in, such as `eu1.make.com` or `us2.make.com`, as shown in your Make dashboard's address bar; the CLI reads it from `MAKE_ZONE`.

n8n runs automation workflows, with AI steps, that a team builds visually or in code. It runs on n8n Cloud or self-hosted, so every way in points at your own instance: `{your-n8n-domain}` and `{your-domain}` are its domain without `https://`, such as `your-instance.app.n8n.cloud` on n8n Cloud or the domain that serves your n8n editor when self-hosted. The built-in MCP server is off until an instance owner or admin turns on Settings > Instance-level MCP. It signs in with OAuth, and an agent can run or change only the workflows enabled for MCP access. The `n8n-cli` CLI and the public REST API take an API key from Settings > n8n API, sent in the `X-N8N-API-KEY` header; the CLI reads the instance URL from `N8N_URL`. The API isn't available during the free trial.

Zapier is an automation platform with integrations for 9,000+ apps and 40,000+ actions. Its hosted MCP server and the `zapier-sdk` CLI let an agent find and run those actions, such as sending a Slack message or looking up a contact, through the app connections already saved in a Zapier account, so the agent never handles a third-party API key. The MCP server signs in with OAuth from inside the MCP client, and Zapier creates the server during that sign-in; in its default agentic mode the agent discovers and enables actions itself. The CLI signs in through the browser with `zapier-sdk login`. Each successful MCP tool call uses two tasks from the Zapier plan. Zapier's REST APIs on `api.zapier.com` serve partners that embed Zapier in their own product: running an action through them needs a public Zapier integration or White Label access.

GitHub hosts Git repositories and the issues, pull requests and discussions around them. Its search covers public code, repositories and users, so it is also a way to find the teams that use a technology and the developers who follow a project.

Attio is a CRM for revenue teams. Its hosted MCP server signs in as an Attio user with OAuth, and its REST API takes a workspace access token that an admin creates under Workspace settings, Developers. Both read and write people, companies, deals and custom objects, list entries, notes and tasks.

In Close, the central record is the lead: a company or organization that holds the contacts (people) you sell to, plus their opportunities, tasks and activities such as calls, emails and notes. The hosted MCP server signs in with OAuth and supports Dynamic Client Registration. The scope granted at sign-in decides its tools: `mcp.read` only reads, `mcp.write_safe` also creates records, and `mcp.write_destructive` also updates and deletes them. The REST API uses HTTP Basic auth with an API key as the username and an empty password, so `CLOSE_API_KEY` holds the base64 of the key followed by a colon (`<key>:`). Keys are created per user and organization in Close under Settings, Developer, API Keys.

HubSpot's marketing, sales and service tools share one CRM of contacts, companies, deals and activities. Its hosted MCP server reads and writes CRM records with the signed-in user's permissions. The REST API takes a service key (in public beta) or an app's static access token as a Bearer token, and its current paths carry a dated version such as `2026-09`.

Pipedrive is a sales CRM for small and medium-sized businesses, built around deals, leads, people, organizations, activities and notes. Its hosted MCP server is on every plan, and its usage counts against the plan's token limits. It signs in with OAuth, can only see and change what the signed-in user can, and records every change in the change log. The REST API takes the user's personal API token in the `x-api-token` header; a user has one active token at a time. Each company has its own API host: `GET https://api.pipedrive.com/v1/users/me` returns it as `company_domain`. Persons, organizations, deals and activities are on `/api/v2/`; creating leads and notes is still on `/api/v1/`.

Salesforce is a CRM: accounts, contacts, leads and opportunities, as objects each org can extend. The MCP server is Salesforce's hosted SObject Mutations server for production orgs: it queries, searches, creates and updates records but never deletes them. Sandboxes use `https://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-mutations`, and an admin must first create an External Client App and activate the server. The REST API runs on each org's own My Domain URL, written `https://{MyDomainName}.my.salesforce.com` here (`MyDomainName` in Salesforce's docs), and its paths carry the API version as `vXX.X`; after `sf org login web`, `sf org display` prints both as Instance Url and Api Version.

Twilio Segment is a customer data platform: it collects events and user traits from websites, apps and servers, cleans them, and routes them to the analytics, CRM and marketing tools connected as destinations. The HTTP Tracking API records identify, track, group, page and batch calls for one source and authenticates with that source's write key (in the source, open Settings and then API Keys). Send it as Basic auth: `SEGMENT_API_KEY` holds the base64 of the write key followed by a colon, `<write key>:`. Workspaces in the EU send to `https://events.eu1.segmentapis.com` with a write key from an EU workspace; Segment rejects data sent to the wrong region. The Public API at `https://api.segmentapis.com`, which manages sources, destinations and Engage audiences, takes a separate workspace token and is not the API listed here.

Front is a customer service platform where teams work email, SMS, chat and other channels as shared conversations, with internal comments, tags and assignment. Its hosted MCP server, in open beta, acts as the Front teammate who authorizes it, with that teammate's permissions and the `read`, `write` and `send` scopes. Front does not support Dynamic Client Registration: create a developer app with an OAuth feature (Settings, Company, Developer), enable MCP Server feature access, and connect the AI client with that app's client ID and secret. Claude and ChatGPT can connect from their official connector directories instead. The Core API takes a company-level API token as a Bearer token. An admin creates it under Settings, Developers, API Tokens, and its features, namespaces and permissions decide what it reaches; sending messages needs the Send permission.

Intercom is a helpdesk with a natively integrated AI agent, Fin, built around contacts (users and leads), companies and conversations. Its hosted MCP server signs in with OAuth and searches and reads conversations, contacts, companies and Help Center articles, creates and updates articles, and adds internal notes. It serves US and EU workspaces: EU workspaces (`app.eu.intercom.com`) use `https://mcp.eu.intercom.com/mcp`, and AU workspaces are not supported yet. The REST API takes the access token of an app created in the Developer Hub (Configure, then Authentication) as a Bearer token. EU and Australian workspaces call `https://api.eu.intercom.io` and `https://api.au.intercom.io`. Requests use the API version set on the app unless an `Intercom-Version` header, such as `2.16`, overrides it.

Zendesk is a customer service platform. Its Support API, also called the Ticketing API, manages tickets, users, organizations and search. `{subdomain}` is the account's Zendesk subdomain, as in `acme.zendesk.com`; Zendesk's own CLI reads it from `ZENDESK_SUBDOMAIN`. Requests authenticate with an OAuth access token sent as a Bearer token, `ZENDESK_OAUTH_TOKEN` being the name Zendesk's CLI uses for one. Register an OAuth client in Admin Center, then get the first token with the one-time browser setup. Tokens from clients created on or after April 30, 2026 expire after 30 minutes by default and come with a refresh token. API tokens, sent with Basic auth, are being retired: accounts can't create new ones after October 27, 2026, and all of them stop working on April 30, 2027. Zendesk announced its own MCP server for early access in May 2026.

Apollo is a sales intelligence and engagement platform with a database of over 240 million contacts and 30 million companies. Its MCP server, the `apollo` CLI and the REST API search and enrich people and companies, manage contacts, accounts and deals, and enroll contacts in outbound sequences. The MCP server and the CLI sign in with OAuth; the API takes an API key, and the Apollo plan decides which endpoints it can call and what they cost in credits.

Clay is a go-to-market data and automation platform. From the `clay` CLI or the Public API an agent can search Clay's database of people and companies, run Clay-managed enrichment functions (work email, phone, firmographics, tech stack, funding) or a team's own functions, and set up signals that watch for job changes, hiring and funding news. Tables and custom functions are still built in the Clay app; the CLI and API run and read them.

Crustdata provides a real-time B2B data API for AI agents, covering people and companies for sales, recruiting and investment workflows. Its Company, Person, Job, Web and Social Post APIs search, identify and enrich records, and watches deliver newly matching records on a schedule. Pin every API request to a version with the `x-api-version: 2025-11-01` header; some endpoints and fields depend on the plan. The MCP server's tool names aren't published, so the tools below name only their API or CLI calls; the server lists its own once connected.

Hunter finds and verifies professional email addresses: it lists the people and emails behind a company domain, finds one person's email, checks deliverability, discovers companies that match a profile, enriches people and companies, and runs outreach sequences from saved leads. The hosted MCP server covers all of it; Claude, ChatGPT and Gemini sign in with OAuth, and other clients send the API key in an `X-API-Key` header. The REST API accepts the key in that header, as a Bearer token, or as the `api_key` query parameter. Every plan, including the free one, can use the API and the MCP server. Usage counts against the plan's credits: a search uses 1 credit and a verification half a credit, while Discover (company search) is free.

Lusha is a B2B data platform for prospecting and enrichment: verified emails, direct and mobile phone numbers, company firmographics, and signals such as job changes, promotions, hiring surges and funding news. Its MCP server finds and enriches contacts and companies, searches by ideal customer profile, finds lookalikes and returns signals and scored recommendations. The MCP server signs in with OAuth; a client without OAuth can send a Lusha API key in the `x-api-key` header instead. The REST API (version 3, under `https://api.lusha.com/v3/`) takes the key in an `api_key` header. Searches return previews without emails or phones. Credits are charged per search result, per revealed email or phone and per matched signal, and failed lookups are not charged.

People Data Labs (PDL) is a B2B data provider. Its REST API matches people against a dataset of nearly three billion profiles and companies against its company records, searches both with Elasticsearch or SQL queries, and resolves IP addresses to the companies behind them. Official SDKs cover Python, JavaScript, Ruby, Go and Rust. The API takes a key in the `X-Api-Key` header. Enrichment is charged per match and search per record returned. The free plan is meant for testing and returns contact fields such as emails, phone numbers and street-level locations only as true/false flags; a paid Pro plan returns their values.

ZoomInfo is a go-to-market intelligence platform with data on more than 100 million companies and 500 million professionals, plus buying and business signals such as intent topics, news and scoops. Its MCP server, the `gtm` CLI and the GTM API search and enrich companies and contacts, find companies researching a topic and run AI account research, all on one backend with shared credits. Every way in needs a ZoomInfo license (GTM.ai self-serve or Enterprise), and the plan decides which data, endpoints and credits are available. The MCP server and the CLI sign in with OAuth in a browser. The API takes an OAuth 2.0 access token from an app created in the ZoomInfo Developer Portal, with the client-credentials flow for server-to-server calls. Searches are free; enriching a record costs one credit the first time in any 12 months.

Airtable is a platform for building apps, workflows and agents on shared data: a base holds tables of records, with interfaces, forms and automations on top. Its MCP server, available on every plan, reads, creates and updates records, builds bases, tables, interfaces and automations, and submits forms, always within the permissions you already have. It signs in with OAuth; a personal access token works too. The `airtable-mcp` CLI runs the same MCP tools from a terminal, with hyphens in place of underscores (`list_records_for_table` becomes `airtable-mcp list-records-for-table`). Run `airtable-mcp tools` to see what the server offers now: the CLI is experimental and tool names can change. One personal access token, created with the scopes you need, serves both the CLI and the Web API, which takes it as a bearer token. Record writes through MCP and the CLI key fields by field id: read the ids with `get_table_schema`.

Canva is an online visual communication and collaboration platform. Its MCP server lets an AI assistant generate, edit, search and export a user's designs; its REST APIs, also reachable through `canva api` in the Canva CLI, let an app create, autofill, resize and export designs on the user's behalf. Both act as a signed-in Canva user, and some calls need a paid Canva plan.

Figma is a browser-based design tool for interfaces and prototypes, with FigJam for whiteboards and Figma Slides for decks. Its remote MCP server reads designs and writes to Design, FigJam and Slides files; the REST API reads files and renders their layers as images.

Notion is an AI workspace for docs, wikis and databases, where teams build Custom Agents, search across their apps and automate busywork. A database holds one or more data sources, and each row of a data source is a page. API requests also send a `Notion-Version` header; `ntn api` adds it for you. One personal access token works for the CLI and the API: the CLI reads it as `NOTION_API_TOKEN` and API requests as `NOTION_API_KEY`, each the name that way's docs use.

Brew is an AI-native email platform for teams and AI agents. Describe an email, audience or automation and Brew designs it on brand from your own design system, checks rendering and deliverability, and sends it from your domain. It is built for permission-based marketing and transactional email: cold outreach to lists without opt-in is not permitted.

Customer.io is a messaging automation platform: automations, broadcasts, one-time sends and transactional messages go out by email, push, SMS, in-app and WhatsApp, targeted with segments built from people's attributes and events. The MCP server and the `cio` CLI reach Customer.io's Journeys and Data Pipelines APIs through generic tools: `cio_schema` finds an endpoint, `cio_read_api` makes GET requests and `cio_write_api` makes POST, PUT and PATCH requests (`cio schema` and `cio api <path>` on the CLI). An account admin must first turn MCP on under Settings > AI; each person then signs in with OAuth and grants scopes, and changing live data or sending messages over MCP also needs the admin's permission. The CLI takes a service-account token (`sa_live_...`) in `CIO_TOKEN`. The API above is the App API, which sends transactional messages and broadcasts and reads workspace data with an App API key as a Bearer token. EU accounts use `https://mcp-eu.customer.io/mcp` and `https://api-eu.customer.io`. People and events come in through the separate Track and Pipelines APIs, which use Basic auth.

Klaviyo is a B2C marketing platform: profiles and the events they generate drive email and SMS campaigns, automated flows, lists and segments. The remote MCP server signs in with OAuth and is open to Owner, Admin and Manager roles; add `read-only=true` to its URL to turn off every tool that writes. The `klaviyo` CLI has a command for every JSON API operation and takes a private API key (`pk_...`). The API takes that key as `Authorization: Klaviyo-API-Key <key>` plus a `revision` header with the API version date, such as `2026-07-15`; the CLI sends both for you.

Loops is an email platform for software companies: marketing campaigns, workflows that start when an event arrives or a contact changes, and transactional email, all sent from one product. The MCP server exposes four generic tools: `search` finds a Loops API operation, `describe` shows its request shape, `execute` runs it for a team, and `teams` lists the teams you can reach. It signs in with OAuth, so the client must support Client ID Metadata Documents or be preregistered with Loops. The `loops` CLI and the REST API take an API key. The API allows 10 requests per second per team, and 60 per minute on the content endpoints, campaigns included.

Mailchimp is an email and SMS marketing platform. Its Marketing API manages audiences of contacts, organized with tags, segments and events, and creates and sends campaigns. `{dc}` in the API URL is your account's data center, such as `us6`: the part of the API key after the dash. The key works as a Bearer token (HTTP Basic auth with any username also works), and an account gets 10 simultaneous connections. Transactional email (formerly Mandrill) is a separate API at `https://mandrillapp.com/api/1.0` with its own key; its MCP server at `https://mandrillapp.com/mcp` takes that key as a Bearer token.

Resend is an email API for developers. It sends transactional email and marketing broadcasts from your verified domains, keeps contacts in segments with topic subscriptions, and runs automations that custom events start. The hosted MCP server, the `resend` CLI and the REST API each cover the whole platform. The MCP server signs in with OAuth; an agent that can't open a browser can send an API key as a Bearer token instead. Direct API requests must also send a `User-Agent` header, and a team gets 10 requests per second by default.

Twilio SendGrid sends transactional email through its v3 Mail Send API and runs Marketing Campaigns: contacts, lists and segments, and Single Sends to them. The CLI is the Twilio CLI, whose built-in SendGrid commands send email with `SENDGRID_API_KEY`. EU regional subusers send mail through `https://api.eu.sendgrid.com`. Twilio's MCP server at `https://mcp.twilio.com/docs` indexes SendGrid's docs but can't call the API.

Typeform builds forms, surveys and quizzes, and runs automations on the responses to enrich leads and follow up. Its MCP server builds and publishes forms and automations, manages contacts and analyzes responses; the Create, Responses and Webhooks APIs create forms, read full responses and push new responses to a URL. The MCP server signs in with OAuth only, and almost every tool needs the `account_id` that `accounts-list_accounts` returns. The APIs take a personal access token as a Bearer token. Accounts hosted in an EU data center use `api.eu.typeform.com` or `api.typeform.eu` in place of `api.typeform.com`, for both the MCP server and the APIs. Features depend on the plan, which is checked when a tool is called.

6sense captures anonymous buying signals across the buyer's journey, predicts each account's buying stage, and supplies B2B people and company data to revenue teams. The hosted MCP server is read-only and signs in each user with OAuth. It answers questions about account insights, 6QA trends, keyword intent, website activity, ad campaign performance and segments, and with Sales Intelligence it finds and unlocks contacts. 6sense's docs don't list the server's tool names; the agent discovers them after connecting. An admin must first turn on MCP under Settings, AI and MCP (it is off by default), and what each user can ask depends on their Revenue Marketing or Sales Intelligence license. The REST API takes a 40-character API token in `Authorization: Token`. Tokens are created in Settings, API Token management, and each works only for the APIs of its group; enrichment calls spend 6sense Credits allocated to API (Enrichment). The API allows 100 requests a minute. The Company Identification and Lead Scoring APIs run on other hosts (`epsilon.6sense.com`, `scribe.6sense.com`) and aren't covered here.

G2 is a marketplace where buyers compare business software through user reviews. For vendors listed on it, G2 Buyer Intent shows which companies are researching their product, category or competitors, alongside G2's reviews, product catalog and categories. The hosted MCP server signs in with OAuth 2.0. In Claude and ChatGPT, add the G2 MCP connector from their catalogs. G2's OAuth server doesn't support Dynamic Client Registration, so any other client first registers an OAuth app in the G2 Developer Portal and uses its client ID and secret. What an account can read depends on its G2 subscription: buyer intent needs a Buyer Intent license, and Market Intelligence reviews need an Enterprise package. The REST API takes a G2 access token as a Bearer token. Create one in the G2 Developer Portal under Access Tokens and choose the endpoints it can reach; tokens expire a year after they are created. G2 allows 100 API requests per second from each IP address.

Slack is team messaging: channels, direct messages, files and workflows. The MCP server acts as the signed-in user, and a workspace admin must approve MCP access first. The Web API and the CLI's `slack api` command call the same methods with a bot token (`xoxb-`) from an app installed in the workspace; `slack api` reads it from `SLACK_BOT_TOKEN`.

Twilio provides APIs to send SMS, MMS and WhatsApp messages, place voice calls, look up phone numbers and verify users with one-time codes. The `twilio` CLI reaches every Twilio REST API through `twilio api:...` commands. It reads credentials from `TWILIO_ACCOUNT_SID`, `TWILIO_API_KEY` (an API key SID) and `TWILIO_API_SECRET`, or from a profile that `twilio login` saves. Twilio also documents apt, Scoop, Docker and npm installs of the CLI. The REST APIs behind those commands live on several hosts, such as `https://api.twilio.com` for messages and calls, `https://verify.twilio.com` and `https://lookups.twilio.com`, and take HTTP Basic auth with an API key SID as the username and its secret as the password; each tool names its REST call. Twilio's hosted MCP server at `https://mcp.twilio.com/docs` searches Twilio's API specs and docs but does not make calls.

Chargebee is a billing and revenue management platform: it meters usage, runs subscriptions, turns them into invoices and payments, and recognizes revenue on one commercial record. `{site}` and `{YOUR-CHARGEBEE-SUBDOMAIN}` are your Chargebee site name, such as `acme-test`. The REST API uses HTTP Basic auth with the API key as the username and an empty password, takes form-encoded parameters and returns JSON. Create a key under Settings > Configure Chargebee > API Keys and Webhooks; test and live sites have different keys. The Data Lookup MCP server reads customers, subscriptions, invoices, quotes and payments. Turn on its MCP access and create an OAuth client ID for your MCP client under Settings > Configure Chargebee > Agentic AI > MCP Servers; sites with Multi-Business Entity enabled can't use OAuth. Sites in the EU and AU data centers use `mcp.eu.chargebee.com` and `mcp.au.chargebee.com` in place of `mcp.chargebee.com`. The MCP server's docs list its tools by label, not by name, so the tools below name only their API calls; the server lists its own once connected.

Paddle is a merchant of record for SaaS, mobile app, AI and digital product companies: it takes care of payments, tax, fraud and compliance and manages subscriptions in a single integration. These files cover Paddle Billing; the legacy Paddle Classic is a separate product with a different API. Instead of one tool per API operation, the hosted MCP server has three tools: `search` finds an API method and its parameters, `execute` runs JavaScript that chains one or more API calls, and `report_missing_tool` flags a gap to Paddle. The live server signs in with OAuth and starts with read access to what your Paddle role permits; grant write access, or remove the connection, under Paddle > Connectors > MCP. The sandbox server (`https://sandbox-mcp.paddle.com/mcp`) and sandbox API (`https://sandbox-api.paddle.com`) take a sandbox API key instead. The API uses Bearer API keys created under Paddle > Developer tools > Authentication, each with only the permissions it needs.

Stripe takes payments online and runs billing, invoices and subscriptions. Stripe's MCP server reaches the API through generic tools rather than one tool per method: `stripe_api_read` runs any supported `GET` method and `stripe_api_write` any supported `POST`, `PATCH`, `PUT` or `DELETE` method, while `stripe_api_search` and `stripe_api_details` find a method and its parameters. The CLI signs in with `stripe login` in the browser, or reads a key from `STRIPE_API_KEY`.

Amplitude is an AI analytics platform that tracks what users do in a product and turns it into engagement, retention and revenue insights. Its MCP server queries analytics, user activity and cohorts with your Amplitude permissions; the `amp` CLI and the Developer API behind it manage projects, taxonomy and feature flags and query saved charts. Projects with EU data residency use `https://mcp.eu.amplitude.com/mcp`.

Metabase is open-source analytics software that grounds every answer in your semantic layer (your metrics and business logic), so you can inspect the query behind it. Each Metabase is served from its own address: replace `{your-metabase-url}` with it. An admin turns the MCP server on under Admin > AI > MCP, and it signs in with OAuth. API keys are created under Admin > Settings > Authentication > API keys; a key's group decides what it can read.

Mixpanel is a product intelligence platform that combines event analytics (insights, funnels, flows and retention), session replay, experiments, feature flags and AI-powered insights. The URLs above are for US projects. EU and India projects use `https://mcp-eu.mixpanel.com/mcp` and `https://mcp-in.mixpanel.com/mcp` for MCP, and `https://eu.mixpanel.com/api/query` and `https://in.mixpanel.com/api/query` for the Query API. The Query API authenticates with a service account: `MIXPANEL_SA_TOKEN` holds the base64 of `<username>:<secret>`, and every request carries `project_id`.

PostHog is a product platform that combines product and web analytics, session replay, feature flags, experiments, surveys, error tracking and a CDP in one place. The API URL above is US Cloud; EU Cloud projects use `https://eu.posthog.com`. The hosted MCP server routes to the right region from the account you sign in with. The CLI reads its key as `POSTHOG_CLI_API_KEY` and the API as `POSTHOG_PERSONAL_API_KEY`: each is the name that way's docs use.

Asana is work management software for teams and AI agents. Its V2 MCP server and its REST API read and write the Work Graph: tasks, projects, portfolios, goals and the people they are assigned to. Coding clients such as Claude Code or Cursor connect to the MCP server through an OAuth app you register in the Asana developer console; the API takes a personal access token.

Atlassian makes Jira, for planning and tracking work, and Confluence, for docs and team knowledge, alongside Loom, Bitbucket and Rovo AI agents; Trello is listed on its own. The Rovo MCP server reads and writes Jira, Confluence, Bitbucket, Loom and more with the signed-in user's permissions. It lists a few primary tools up front, including every call named here, and finds the rest at runtime through `discover`, which you then run with `executeRead` or `executeWrite`. Some tools spend Rovo credits. The `acli` CLI covers Jira; sign in with `acli jira auth login --web`. The Jira and Confluence REST APIs live on your own site, where `your-domain` is its name, and Confluence paths start with `/wiki`. They take basic auth: `ATLASSIAN_API_KEY` holds the base64 of `<email>:<api token>` for a token created without scopes. A scoped token calls `https://api.atlassian.com/ex/jira/{cloudId}` instead.

ClickUp keeps tasks, docs, goals and chat in one Workspace, organized into Spaces, Folders and Lists. Its MCP server, in public beta on every plan, searches, creates and updates tasks, and works with comments, docs, time tracking and Chat. It signs in with OAuth only. Without the Everything AI add-on, MCP calls are capped per rolling 24 hours: 50 on the Free Forever plan and 300 on Unlimited and above; with it, the API's own rate limits apply. The REST API takes a personal token, which starts with `pk_`, in the `Authorization` header as is; OAuth apps send `Bearer <token>` instead. Most endpoints are v2 and newer ones, such as Chat, are v3, both under the base URL above. In v2 paths a Workspace is called a team.

Linear is where product teams and AI agents plan and build: issues, projects, cycles, initiatives and documents, plus Customer Requests that tie feedback from customers to the work it asks for. Its hosted MCP server finds, creates and updates issues, projects, comments and documents. It signs in with OAuth, and also accepts a Linear API key as a bearer token; connect to `https://mcp.linear.app/mcp/readonly` for read tools only. The API is GraphQL only: every call is a `POST` to `https://api.linear.app/graphql` with a query or mutation in the body. A personal API key goes in the `Authorization` header as is, without `Bearer`; an OAuth access token is sent as `Bearer <token>`.

monday.com is a work platform where teams run work management, sales CRM, dev and service work on boards: each row is an item, and its columns hold typed values such as a status, a date or an email. The hosted Platform MCP server has more than 60 tools for boards, items, docs, forms, dashboards and automations. It signs in with OAuth or takes a personal API token as a bearer token, and every MCP call runs as a GraphQL API request that counts toward the account's daily API call limit. The API is GraphQL: every call is a `POST` to `https://api.monday.com/v2` with a query or mutation in the body, and the personal API token goes in the `Authorization` header as is. Find the token under your profile picture, then Developers, then API token. Viewer seats can't use the API.

Trello organizes work as cards in lists on boards. The MCP server works on any Trello plan and connects to one workspace per authorization. It can search boards and cards, create and update cards and checklists, move cards and lists, and archive cards, but it cannot delete anything. The REST API takes OAuth 2.0 bearer tokens since September 2026, and still accepts the older API key and token pair. The MCP server's tool names aren't published, so the tools below name only their API calls; the server lists its own once connected.

Gong records and analyzes the calls and emails a revenue team has with customers, ties them to the accounts, deals, contacts and leads in the CRM, and runs Gong Engage flows for outreach. The hosted MCP server is read-only: it answers questions about accounts and deals and writes briefs from their calls and emails, and never returns raw transcripts or email bodies. A Gong tech admin must first register an MCP server integration under Admin center, Settings, Ecosystem, MCP. With automatic registration, people connect by signing in to Gong; a manual integration issues a client ID and secret for the one client allowed to connect. Connecting needs a paid Gong seat, and every answer consumes Gong credits. The API host differs per company: Gong's API settings show it, and OAuth returns it as `api_base_url_for_customer` (the docs' example is `https://company-17.api.gong.io`). A tech admin creates an access key and secret on the Gong API page; `GONG_API_KEY` holds the base64 of `<access key>:<access key secret>`. By default a company can make 3 API calls per second and 10,000 per day.

Instantly runs cold email outreach: it connects and warms up sending accounts, sends campaigns with sequences and subsequences, finds leads in its SuperSearch B2B lead database, verifies email addresses, and keeps replies in its Unibox inbox and CRM. API v2 takes a workspace API key as a Bearer token; each key carries scopes, every path starts with `/api/v2`, and the workspace shares a limit of 100 requests per second and 6,000 per minute. The `instantly` CLI reads the same key from `INSTANTLY_API_KEY`. Instantly also hosts an MCP server at `https://mcp.instantly.ai/mcp` with a tool for every API v2 endpoint, named like `list_campaigns` or `create_lead`. It authenticates with the API key in the `Authorization` header, and `instantly mcp` runs a local MCP server from the CLI.

lemlist is a sales engagement platform for cold outreach: it finds leads in its people and companies databases, enriches them with verified emails and phone numbers, runs multichannel campaigns across email, LinkedIn, phone and WhatsApp, and keeps contacts and replies in its own CRM and inbox. The MCP server and the `lemlist` CLI sign in with OAuth; the MCP server also accepts an API key in an `X-API-Key` header, and `?bucket=` narrows the tools it advertises. The CLI's `lemlist api <METHOD> <path>` calls any endpoint of the REST API. The REST API uses HTTP Basic auth with an empty username and the API key as the password, so `LEMLIST_API_KEY` must hold the base64 encoding of `:` followed by the key. Each key may send 20 requests every 2 seconds, and enrichment spends the team's credits.

Outreach is a sales engagement and revenue platform: reps work prospects and accounts, enroll prospects in multi-step sequences, and track opportunities, recorded meetings and forecasts. Its hosted MCP server searches, creates and deletes those records and answers questions about accounts and opportunities, signing in with OAuth 2.1 as the Outreach user. It needs the Amplify add-on, an admin must switch it on under Administration > Organization > Org Info, and create tools are on while delete tools are off until the admin allows them. The REST API follows JSON:API 1.0: send `Content-Type: application/vnd.api+json` and a bearer token from an Outreach app's OAuth 2.0 flow. It is rate limited to 10,000 requests per hour per user.

Salesloft is a revenue platform: sales teams keep people and accounts, run cadences of email, phone and other steps, record and transcribe conversations, and track opportunities synced from their CRM. Its hosted MCP server is read-only and in beta: it searches and reads people, accounts, opportunities, conversations and users, but can't write anything or read cadences. It comes with Salesloft's Agent packages, an admin must turn on Enable MCP Server under Settings > Artificial Intelligence Settings, users sign in with OAuth, and every MCP call counts against the team's API rate limit. Customers call the REST API with an API key sent as a Bearer token: create one under Your Applications > API Keys in Salesloft and give it the scopes the calls need (partners build OAuth apps instead). Every path starts with `/v2`, and the team shares a limit of 600 cost points per minute.

Cal.com is open-source scheduling software for individuals, businesses that take calls, and developers building scheduling into their own products. Its hosted MCP server, the `calcom` CLI and API v2 check availability, create, reschedule and cancel bookings, and manage event types, schedules and private booking links. The MCP server signs in with OAuth 2.1. The CLI and the API take an API key (`cal_live_` in live mode, `cal_` in test mode) as a Bearer token: run `calcom login` once, or set `CAL_API_KEY`. Every API v2 request needs the `cal-api-version` header, set to the version its endpoint's reference names. Checking slots and creating a booking are public and need no key.

Calendly is meeting scheduling software that covers the work around a meeting, from scheduling and payments to meeting prep, notetaking, contact management and follow-up. Its hosted MCP server and REST API v2 read and update event types and availability, create single-use scheduling links, book invitees directly through the Scheduling API, and list scheduled events and their invitees. The MCP server is hosted by Calendly and signs in with OAuth 2.1 through dynamic client registration; it does not accept personal access tokens. The API takes a personal access token, or an OAuth app's token, as a Bearer token. Any Calendly plan can connect over MCP, but booking an invitee directly needs a paid plan (Standard or above) and routing forms need Teams or higher.

Apify is a cloud platform for web scraping and automation. Its programs, called Actors, run in the cloud from JSON input and save their results to datasets, and Apify Store lists ready-made Actors such as scrapers for Google Search, Google Maps and Instagram. The MCP server, the `apify` CLI and the REST API search the Store, run Actors and read their results. The MCP server signs in with OAuth in the browser, or takes an Apify API token as a Bearer header. The CLI signs in through Apify Console with `apify login`, and the API takes the token as a Bearer token. Each Actor sets its own pricing, such as Apify platform usage, a price per result or a price per event.

Firecrawl turns websites into data an agent can use. It scrapes a page into markdown or JSON, searches the web, maps and crawls whole sites, and runs an agent that gathers structured data across sources from a prompt.

Dropbox stores and syncs files and folders and shares them by link, with named people, or through file requests that collect uploads from others. Its HTTP API takes OAuth 2 access tokens; its remote MCP server, in beta, gives agents the same kinds of actions: search, shared links, file requests and file management.

Loom, now part of Atlassian, records screen and camera videos and meetings and adds transcripts, AI briefs and meeting action items. Agents reach Loom through the Atlassian Rovo MCP server, which reads videos with their transcripts, comments and action items, and uploads, shares and organizes videos as the signed-in user. Only Loom workspaces linked to an Atlassian site are available, and Loom has no open API. The server lists a few primary tools, such as `getLoomVideo`, directly; the other Loom tools are deferred: find them with `discover` and run them through `executeRead`, `executeWrite` or `executeDestructive`, by risk tier. A client that needs every tool listed up front can connect to `https://mcp.atlassian.com/v2/mcp?tools=all`. The server signs in with OAuth 2.1; an API token also works once an organization admin enables it.

Zoom runs video meetings and webinars, with team chat and phone alongside. Both the MCP server and the API sign in through an OAuth app you create on the Zoom App Marketplace. The MCP server does not support dynamic client registration, so the agent's client needs that app's client ID and secret. Webinar calls need a Pro or higher plan with the Webinar add-on.

Exa is a web search engine built for AI agents. Its API searches the web in natural language, with categories for company pages and people profiles, returns clean page contents, answers questions with citations, reruns searches on a schedule as monitors, and runs Exa Agent for multi-step research, list building and enrichment with structured output. The hosted MCP server also works without a key at free rate limits. Signing in with OAuth (the `?login` URL) uses your team's plan and turns on `agent_run`; a client without OAuth can send an API key in the `x-api-key` header instead. The API takes the key as a Bearer token or in `x-api-key`. Usage is pay-as-you-go, and new accounts start with free credits.

Perplexity's API platform brings real-time, web-wide research and Q&A to your products. The Search API returns ranked web results; the Agent API answers and researches with web search using models from several providers; the Router and Embeddings APIs cover open-weight models and embeddings. Sonar Chat Completions was replaced by the Agent API and reached its end of support on September 27, 2026. The hosted MCP server offers `perplexity_search`, `perplexity_ask`, `perplexity_research` and `perplexity_reason`. It signs in with your Perplexity account and bills tool calls to the API organization you pick, which you must administer. The `pplx` CLI returns Search API results and page snippets as JSON.

Webflow is a platform for designing, building and hosting websites, with a CMS, forms and SEO settings built in. Its remote MCP server, the `webflow` CLI and the Data API v2 create, update and publish CMS items, publish sites and read form submissions; the MCP server can also build pages, styles and components. The MCP server signs in with OAuth, one workspace per authorization, and an agent can do only what the user's Webflow role allows. `webflow auth login` opens a browser sign-in and saves a `WEBFLOW_API_TOKEN` to the project's `.env`; the CLI needs Node.js 22.13.0 or later. The Data API takes a site token as a Bearer token: a site administrator creates it per site under the site's settings, in Apps & integrations, API access.