NeoTask MCP Provider Reference
This page is generated from the current Electron MCP registry, reviewed auth classifications, and provider OAuth setup truth. Use it when support needs a provider-specific answer about auth mode, callback URLs, setup fields, scopes, or required fields.
Coverage
Total providers covered: 238
Auth provider
api_key: 39Auth provider
credentials: 39Auth provider
none: 11Auth provider
oauth: 149Reviewed classification
api_key: 39Reviewed classification
custom_url_first: 12Reviewed classification
local_dcr: 1Reviewed classification
managed_dcr: 120Reviewed classification
managed_dcr_broken: 1Reviewed classification
managed_oauth: 1Reviewed classification
manual_credentials: 38Reviewed classification
manual_oauth: 17Reviewed classification
no_auth: 9
Support Rules
- Use the provider card in NeoTask as the first source of truth for the current setup mode.
- Do not improvise callback URLs, scopes, or required fields.
- Keep provider-admin steps separate from NeoTask staff-only config. Callers should never be told to edit proxy environment variables.
- If a provider is marked
managed_dcr_broken,unreachable, or lacks a committed setup guide, do not guess. Escalate or create a support case. - For providers with custom URLs or manual credentials, verify every required field and the instance URL before blaming OAuth.
Provider Reference
Amplitude
- Provider key:
amplitude - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.amplitude.com/mcp
- Auth docs: https://amplitude.com/docs/amplitude-ai/amplitude-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Amplitude account when prompted.
- Authorize NeoTask to access your Amplitude data.
- The connection is completed automatically.
Asana
- Provider key:
asana - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.asana.com/v2/mcp
- Auth docs: https://developers.asana.com/docs/integrating-with-asanas-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Asana account when prompted.
- Authorize NeoTask to access your Asana data.
- The connection is completed automatically.
Box
- Provider key:
box - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.box.com
- Auth docs: https://developer.box.com/guides/authentication/oauth2/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Box account when prompted.
- Authorize NeoTask to access your files.
- The connection is completed automatically.
Canva
- Provider key:
canva - Auth provider:
oauth - Reviewed classification:
local_dcr - Service URL: https://mcp.canva.com/mcp
- Auth docs: https://www.canva.dev/docs/connect/authentication/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Canva account when prompted.
- Authorize NeoTask to access your Canva data.
- The connection is completed automatically.
Notes:
- Canva's authorize endpoint rejects non-allowlisted hosted redirect URIs (HTTP 400, waitlist gate) but accepts localhost loopback DCR clients (register 201 + authorize 302, live-verified 2026-07-03). Device-local loopback OAuth in the gateway; no proxy callback.
Clay
- Provider key:
clay - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.clay.earth/mcp
- Auth docs: https://github.com/clay-inc/clay-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Clay account when prompted.
- Authorize NeoTask to access your Clay data.
- The connection is completed automatically.
Figma
- Provider key:
figma - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.figma.com/mcp
- Auth docs: https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Figma account when prompted.
- Authorize NeoTask to access your Figma data.
- The connection is completed automatically.
Hex
- Provider key:
hex - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://app.hex.tech/mcp
- Auth docs: https://learn.hex.tech/docs/administration/mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Hex account when prompted.
- Authorize NeoTask to access your Hex data.
- The connection is completed automatically.
monday.com
- Provider key:
monday-com - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.monday.com/mcp
- Auth docs: https://developer.monday.com/apps/docs/oauth
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your monday.com account when prompted.
- Authorize NeoTask to access your monday.com data.
- The connection is completed automatically.
Slack
- Provider key:
slack - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.slack.com/mcp
- Auth docs: https://docs.slack.dev/ai/slack-mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Slack workspace when prompted.
- Authorize NeoTask to access messages and channels.
- The connection is completed automatically.
Salesforce
- Provider key:
salesforce - Auth provider:
oauth - Reviewed classification:
custom_url_first - Service URL: https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
- Auth docs: https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/create-external-client-app.html
Setup steps:
- Enter your exact Salesforce Hosted MCP server URL first.
- Create an External Client App in Salesforce and keep the consumer key ready.
- Then continue the NeoTask OAuth connect flow for that server URL.
Notes:
- Salesforce Hosted MCP uses per-server URLs under api.salesforce.com/platform/mcp/v1/.... Use an External Client App with PKCE. Connected Apps are not supported.
Microsoft Teams
- Provider key:
microsoft-teams - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://teams.microsoft.com
- Auth docs: https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/authentication/authentication
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in with your Microsoft account when prompted.
- Authorize NeoTask to access Teams messages and channels.
- The connection is completed automatically.
Notes:
- Uses Microsoft Entra / Azure AD app registration.
Microsoft 365
- Provider key:
microsoft-365 - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.svc.cloud.microsoft/enterprise
- Auth docs: https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in with your Microsoft 365 account when prompted.
- Authorize NeoTask to access Outlook, OneDrive, and SharePoint.
- The connection is completed automatically.
Notes:
- Uses Microsoft Entra / Azure AD app registration.
Infobip
- Provider key:
infobip - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.infobip.com/sms
- Auth docs: https://www.infobip.com/docs/essentials/api-essentials/api-authentication
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Infobip account when prompted.
- Authorize NeoTask to access your Infobip data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
ClickSend
- Provider key:
clicksend - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://rest.clicksend.com/v3
- Auth docs: https://developers.clicksend.com/docs/rest/v3/
- Required fields:
usernamerequired,apiKeyrequired
Setup steps:
- Log into your dashboard at dashboard.clicksend.com.
- Click the key icon in the top-right corner of the page to open the API Credentials panel.
- Your Username is your registration email address. Copy it.
- Your API Key is displayed below it. Click the copy button next to it.
- If you need a new key, click "Regenerate API Key" (this invalidates the old one immediately).
- Enter the required credentials: username (required), apiKey (required).
Notes:
- ClickSend uses HTTP Basic Auth with username + API key, not a bearer header.
LINE
- Provider key:
line - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://line.me
- Auth docs: https://developers.line.biz/en/docs/messaging-api/getting-started/
- Required fields:
apiKeyrequired
Setup steps:
- First, go to manager.line.biz and log in with your LINE account.
- Create a LINE Official Account (enter business name and category).
- In the Official Account Manager, click "Settings" (upper right), then "Messaging API" in the left menu.
- Click "Enable Messaging API", select or create a Provider, click "Agree", then "OK".
- Now go to developers.line.biz/console and log in with the same account.
- Click your Provider name, then click your Messaging API channel.
- Click the "Messaging API" tab, scroll to "Channel access token (long-lived)".
- Click "Issue" to generate a token and copy it. Warning: reissuing invalidates the previous token.
- Enter the required API key: apiKey (required).
Mailgun
- Provider key:
mailgun - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://api.mailgun.net/v3
- Auth docs: https://documentation.mailgun.com/docs/mailgun/api-reference/mg-auth
- Required fields:
apiKeyrequired,domain
Setup steps:
- Log into app.mailgun.com with your Mailgun account.
- In the left sidebar, click "Settings", then "API Security" (or go directly to app.mailgun.com/settings/api_security).
- Your Private API Key is shown at the top (partially hidden). Click "Show" to reveal it, then copy it.
- The key format is: key- followed by 32 hex characters (e.g. key-3ax6xnjp29jd6fds4gc373sgvjxteol0).
- For send-only access, scroll to "Sending API keys" and click "Add sending key" instead.
- Enter the required credentials: apiKey (required), domain.
Notes:
- Mailgun authenticates with HTTP Basic Auth using literal username
apiand the API key as the password.
Mailjet
- Provider key:
mailjet - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://api.mailjet.com
- Auth docs: https://dev.mailjet.com/email/guides/getting-started/
- Required fields:
apiKeyrequired,secretKeyrequired
Setup steps:
- Log into app.mailjet.com and click your account name in the top-right corner.
- Click "Account Settings", then go to "API Key Management" (or go directly to app.mailjet.com/account/apikeys).
- Your API Key (public, 32 hex characters) is shown on this page. Copy it.
- The Secret Key is only shown once at creation time. If you need a new one, click the cogwheel and select "Reset Secret Key".
- Copy and save both the API Key and Secret Key immediately when shown, the Secret Key cannot be retrieved later.
- For restricted access, scroll to "Sub API keys" and click "Create a Sub API key" to set specific permissions.
- Enter the required credentials: apiKey (required), secretKey (required).
Notes:
- Mailjet uses HTTP Basic Auth with API Key as the username and Secret Key as the password.
Courier
- Provider key:
courier - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://mcp.courier.com
- Auth docs: https://www.courier.com/docs/reference/authorization
- Required fields:
apiKeyrequired
Setup steps:
- Log into app.courier.com with your Courier account.
- Click the gear icon in the top-right corner, then click "API Keys".
- Or go directly to app.courier.com/settings/api-keys.
- Copy the key for your environment. Keys use prefixes: pk_prod_ (production published), dk_prod_ (production draft), pk_test_ (test published), dk_test_ (test draft).
- For live notifications, use a pk_prod_ key. For testing, use a pk_test_ key.
- To create a new key, click "Generate API Key".
- Enter the required API key: apiKey (required).
Notes:
- Courier MCP uses the api_key header on the hosted https://mcp.courier.com endpoint.
Knock
- Provider key:
knock - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://knock.app
- Auth docs: https://docs.knock.app/developer-tools/mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Knock account when prompted.
- Authorize NeoTask to access your Knock data.
- The connection is completed automatically.
Notion
- Provider key:
notion - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.notion.com/mcp
- Auth docs: https://developers.notion.com/docs/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Notion account when prompted.
- Authorize NeoTask to access your Notion data.
- The connection is completed automatically.
Linear
- Provider key:
linear - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.linear.app/mcp
- Auth docs: https://linear.app/docs/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Linear account when prompted.
- Authorize NeoTask to access your Linear data.
- The connection is completed automatically.
ClickUp
- Provider key:
clickup - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.clickup.com/mcp
- Auth docs: https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your ClickUp account when prompted.
- Authorize NeoTask to access your ClickUp data.
- The connection is completed automatically.
Atlassian
- Provider key:
atlassian - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.atlassian.com/v1/mcp
- Auth docs: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Atlassian account when prompted.
- Authorize NeoTask to access your Atlassian data.
- The connection is completed automatically.
Airtable
- Provider key:
airtable - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.airtable.com/mcp
- Auth docs: https://airtable.com/developers/web/guides/personal-access-tokens
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Airtable account when prompted.
- Authorize NeoTask to access your Airtable data.
- The connection is completed automatically.
Anytype
- Provider key:
anytype - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: http://localhost:31009
- Auth docs: https://developers.anytype.io/docs/examples/featured/mcp/
- Required fields:
apiKeyrequired
Setup steps:
- Make sure you have Anytype desktop version 0.46.0 or later installed and running.
- Open the Anytype app, click the gear icon in the sidebar to open Settings.
- Navigate to "API Keys" in the Settings panel.
- Click "Create new", give it a name (e.g. "NeoTask"), and copy the generated key.
- The API runs locally at http://localhost:31009, the desktop app must be running for it to work.
- Enter the required API key: apiKey (required).
Notes:
- Anytype runs locally and exposes its MCP-compatible API on localhost:31009 while the desktop app is running.
Archbee
- Provider key:
archbee - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.archbee.com
- Auth docs: https://www.archbee.com/docs/api-endpoints
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Archbee account when prompted.
- Authorize NeoTask to access your Archbee data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Atono
- Provider key:
atono - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://atono.io
- Auth docs: https://docs.atono.io/docs/manage-api-keys
- Required fields:
apiKeyrequired
Setup steps:
- Log into your Atono workspace at app.atono.io.
- Click the circular icon with your initials in the workspace header (top area).
- Select "API keys" from the dropdown menu.
- Click "Create API key", enter a name (e.g. "NeoTask"), and click "Create API key" to confirm.
- Copy the key immediately from the confirmation dialog, it is only shown once at creation time.
- The key authenticates via the X-API-KEY header. Actions taken with it appear as your Atono user account.
- Enter the required API key: apiKey (required).
Dart
- Provider key:
dart - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.dartai.com/mcp
- Auth docs: https://docs.itsdart.com/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Dart account when prompted.
- Authorize NeoTask to access your Dart data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Fibery
- Provider key:
fibery - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://fibery.io
- Auth docs: https://the.fibery.io/@public/User_Guide/Guide/REST-API-Authentication-260
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Fibery account when prompted.
- Authorize NeoTask to access your Fibery data.
- The connection is completed automatically.
Plane
- Provider key:
plane - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.plane.so/http/mcp
- Auth docs: https://developers.plane.so/api-reference/introduction
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Plane account when prompted.
- Authorize NeoTask to access your Plane data.
- The connection is completed automatically.
Notes:
- Hosted Plane MCP supports DCR and public PKCE in proxy config.
Cal.com
- Provider key:
cal-com - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.cal.com/mcp
- Auth docs: https://cal.com/docs/api-reference/v2/introduction
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Cal.com account when prompted.
- Authorize NeoTask to access your Cal.com data.
- The connection is completed automatically.
Notes:
- Official Cal.com MCP endpoint advertises OAuth resource metadata at https://mcp.cal.com/.well-known/oauth-protected-resource. The Cal.com auth server publishes https://mcp.cal.com/oauth/register and token_endpoint_auth_methods_supported [none], so NeoTask should treat it as managed DCR.
Buildable
- Provider key:
buildable - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://bldbl.dev/api
- Auth docs: https://bldbl.dev/docs/user-guide/ai-assistants
- Required fields:
apiKeyrequired,projectIdrequired
Setup steps:
- Log into Buildable at bldbl.dev and open your project.
- Navigate to Project Settings → AI Assistants → Generate API Key.
- Select a permission level: Read-only, Read/Write, or Admin.
- Copy the generated key immediately. Keys start with "bp_" and are project-scoped.
- You also need your Project ID (shown in the project dashboard URL or settings).
- Store the key as BUILDABLE_API_KEY and the project ID as BUILDABLE_PROJECT_ID.
Notes:
- Buildable setup requires both the API key and project ID; the reviewed docs publish BUILDABLE_API_KEY and BUILDABLE_PROJECT_ID runtime variables.
Backdocket
- Provider key:
backdocket - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://ai.backdocket.com/mcp
- Auth docs: https://ai.backdocket.com/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Backdocket account when prompted.
- Authorize NeoTask to access your Backdocket data.
- The connection is completed automatically.
Notes:
- Backdocket is a managed OAuth provider; discard stale generated API-key fields.
WordPress
- Provider key:
wordpress - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://public-api.wordpress.com/wpcom/v2/mcp/v1
- Auth docs: https://developer.wordpress.com/docs/mcp/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your WordPress account when prompted.
- Authorize NeoTask to access your WordPress data.
- The connection is completed automatically.
Zapier
- Provider key:
zapier - Auth provider:
oauth - Reviewed classification:
managed_dcr - Auth docs: https://platform.zapier.com/reference/authentication
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Zapier account when prompted.
- Authorize NeoTask to access your Zapier data.
- The connection is completed automatically.
Zapier MCP
- Provider key:
zapier-mcp - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.zapier.com
- Auth docs: https://zapier.com/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Zapier MCP account when prompted.
- Authorize NeoTask to access your Zapier MCP data.
- The connection is completed automatically.
Notes:
- user-specific-url Separate from original per-user Zapier URL flow. Hosted Zapier MCP supports DCR.
Make
- Provider key:
make - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.make.com
- Auth docs: https://developers.make.com/mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Make account when prompted.
- Authorize NeoTask to access your Make data.
- The connection is completed automatically.
Glean
- Provider key:
glean - Auth provider:
oauth - Reviewed classification:
custom_url_first - Service URL: https://glean.com
- Auth docs: https://developers.glean.com/docs/authentication/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Glean account when prompted.
- Authorize NeoTask to search your company knowledge.
- The connection is completed automatically.
BoldSign
- Provider key:
boldsign - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://boldsign.com
- Auth docs: https://developers.boldsign.com/authentication/api-key/
- Required fields:
apiKeyrequired
Setup steps:
- Log into BoldSign at app.boldsign.com.
- In the left navigation pane, expand "API" and select "API Key".
- Click "Generate API Key". In the dialog, toggle between Sandbox and Live environment.
- Enter a name (e.g. "NeoTask"), optionally set a token expiry date, and click "Generate Token".
- Copy the API key immediately, it will not be shown again. Max 2 keys per environment (4 total).
- Use the key in the X-API-KEY header for all API requests.
- Enter the required API key: apiKey (required).
Nutrient
- Provider key:
nutrient - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.nutrient.io
- Auth docs: https://www.nutrient.io/api/documentation/developer-guides/authentication/
- Required fields:
apiKeyrequired
Setup steps:
- Go to dashboard.nutrient.io and create an account (free tier: 200 credits/month).
- After logging in, click the gear icon (Settings) in the upper-right corner.
- Click "API Keys", then click "Create API Key". Optionally set an expiration date and description.
- Copy the key immediately from the "Private Key" field, it will not be shown again.
- Use the key as: Authorization: Bearer YOUR_API_KEY.
- Enter the required API key: apiKey (required).
Notes:
- Nutrient DWS MCP docs publish NUTRIENT_DWS_API_KEY; remove the fabricated YOUR_API_KEY env placeholder.
Penpot
- Provider key:
penpot - Auth provider:
none - Reviewed classification:
custom_url_first - Auth docs: https://help.penpot.app/technical-guide/integration/
Setup steps:
- Open Penpot → Settings → Integrations → MCP Server.
- Copy the exact MCP server URL from Penpot Cloud, or use http://localhost:4401/mcp for a local Penpot instance.
- Paste that full MCP URL into NeoTask. The cloud URL already carries the userToken, so NeoTask should not ask for a second token field.
Notes:
- Penpot documents MCP as a full URL flow: hosted Penpot Cloud issues a server URL with userToken already embedded, and local Penpot exposes http://localhost:4401/mcp. Treat Penpot as a custom-URL-first provider instead of inventing separate apiKey/YOUR_TOKEN fields.
21st.dev Magic
- Provider key:
21st-dev-magic - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://21st.dev
- Auth docs: https://21st.dev/magic/console
- Required fields:
apiKeyrequired
Setup steps:
- Go to 21st.dev/magic/console and log in (or create an account).
- After login, your API key is displayed prominently on the Magic Console dashboard.
- Copy the key directly from the dashboard page.
- Free tier includes 5 API requests; paid plan is $10/month for additional usage.
- Set the key as the API_KEY environment variable for MCP server configuration.
- Enter the required API key: apiKey (required).
Notes:
- 21st Agents docs publish the API_KEY_21ST environment variable; remove the generic API_KEY placeholder.
Webflow
- Provider key:
webflow - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.webflow.com/mcp
- Auth docs: https://developers.webflow.com/mcp/reference/overview
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Webflow account when prompted.
- Authorize NeoTask to access your Webflow data.
- The connection is completed automatically.
Cloudinary
- Provider key:
cloudinary - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://asset-management.mcp.cloudinary.com/sse
- Auth docs: https://cloudinary.com/documentation/how_to_integrate_cloudinary#create_and_explore_your_account
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Cloudinary account when prompted.
- Authorize NeoTask to access your Cloudinary data.
- The connection is completed automatically.
GitHub
- Provider key:
github - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://api.githubcopilot.com/mcp/
- Auth docs: https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/set-up-the-github-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your GitHub account when prompted.
- Authorize NeoTask to access your repositories.
- The connection is completed automatically.
GitLab
- Provider key:
gitlab - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://gitlab.com/api/v4/mcp
- Auth docs: https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your GitLab account when prompted.
- Authorize NeoTask to access your GitLab data.
- The connection is completed automatically.
Azure DevOps
- Provider key:
azure-devops - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://dev.azure.com
- Auth docs: https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in with your Microsoft account when prompted.
- Authorize NeoTask to access your Azure DevOps organization.
- The connection is completed automatically.
Notes:
- Uses Microsoft Entra / Azure AD app registration.
Buildkite
- Provider key:
buildkite - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://buildkite.com
- Auth docs: https://buildkite.com/docs/apis/mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Buildkite account when prompted.
- Authorize NeoTask to access your Buildkite data.
- The connection is completed automatically.
CircleCI
- Provider key:
circleci - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://circleci.com
- Auth docs: https://circleci.com/docs/managing-api-tokens/
- Required fields:
apiKeyrequired
Setup steps:
- User Settings → Personal API Tokens → Create New Token
Jenkins
- Provider key:
jenkins - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.jenkins.io
- Auth docs: https://www.jenkins.io/doc/book/using/remote-access-api/
- Required fields:
baseUrlrequired,usernamerequired,apiKeyrequired
Setup steps:
- Log into your Jenkins instance at your Jenkins URL (e.g. jenkins.example.com).
- Click your username in the top-right corner, then click "Configure" (or go to /user/YOUR_USERNAME/configure).
- Scroll down to the "API Token" section.
- Click "Add new Token", enter a name (e.g. "NeoTask"), and click "Generate".
- Copy the token immediately, it is shown only once. Use it with your username for Basic Auth.
- Enter your Jenkins URL, username, and API token in the fields above.
- User icon → Configure → API Token → Add new Token
Notes:
- Jenkins uses Basic auth with username + API token; remove the fabricated YOUR_USERNAME env placeholder.
JetBrains
- Provider key:
jetbrains - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://www.jetbrains.com
Setup steps:
- No authentication is required for this integration.
Notes:
- Local IDE/plugin path. Tools are only available when a supported JetBrains IDE is open with the plugin active.
Postman
- Provider key:
postman - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.postman.com/mcp
- Auth docs: https://learning.postman.com/docs/developer/postman-api/postman-api-mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Postman account when prompted.
- Authorize NeoTask to access your Postman data.
- The connection is completed automatically.
Heroku
- Provider key:
heroku - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.heroku.com/mcp
- Auth docs: https://devcenter.heroku.com/articles/oauth
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Heroku account when prompted.
- Authorize NeoTask to access your Heroku data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Netlify
- Provider key:
netlify - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://netlify-mcp.netlify.app/mcp
- Auth docs: https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Netlify account when prompted.
- Authorize NeoTask to access your Netlify data.
- The connection is completed automatically.
Bitrise
- Provider key:
bitrise - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.bitrise.io
- Auth docs: https://devcenter.bitrise.io/en/api/authentication.html
- Required fields:
apiKeyrequired
Setup steps:
- Account Settings → Security → Personal access tokens → Generate
Apify
- Provider key:
apify - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.apify.com
- Auth docs: https://docs.apify.com/platform/integrations/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Apify account when prompted.
- Authorize NeoTask to access your Apify data.
- The connection is completed automatically.
Firecrawl
- Provider key:
firecrawl - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.firecrawl.dev/v2/mcp
- Auth docs: https://docs.firecrawl.dev/introduction#api-key
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Firecrawl account when prompted.
- Authorize NeoTask to access your Firecrawl data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
LaunchDarkly
- Provider key:
launchdarkly - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://app.launchdarkly.com
- Auth docs: https://launchdarkly.com/docs/home/account/api-create
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your LaunchDarkly account when prompted.
- Authorize NeoTask to access your LaunchDarkly data.
- The connection is completed automatically.
DevCycle
- Provider key:
devcycle - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://devcycle.com
- Auth docs: https://docs.devcycle.com/cli-mcp/mcp-getting-started/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your DevCycle account when prompted.
- Authorize NeoTask to access your DevCycle data.
- The connection is completed automatically.
ConfigCat
- Provider key:
configcat - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://configcat.com
- Auth docs: https://configcat.com/docs/advanced/public-api/
- Required fields:
usernamerequired,passwordrequired
Setup steps:
- Dashboard → ConfigCat Management API → Get credentials
JFrog
- Provider key:
jfrog - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://jfrog.com
- Auth docs: https://jfrog.com/help/r/jfrog-platform-administration-documentation/access-tokens
- Required fields:
baseUrlrequired,apiKeyrequired
Setup steps:
- Enter your JFrog platform base URL first.
- Create or copy a JFrog access token/API key from your JFrog profile or access management settings.
- Paste that credential into NeoTask. Do not add a second placeholder token field.
- Enter the required credentials: baseUrl (required), apiKey (required).
Notes:
- JFrog setup is instance-specific, so baseUrl must come from the user’s own SaaS/self-hosted platform URL. Reviewed truth removes the fabricated YOUR_TOKEN env field and keeps only the real baseUrl + token pair.
Gitea
- Provider key:
gitea - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://gitea.io
- Auth docs: https://docs.gitea.com/development/api-usage
- Required fields:
baseUrlrequired,apiKeyrequired
Setup steps:
- Enter the URL for your Gitea instance.
- Generate an access token from Settings → Applications.
- Paste that token into NeoTask. Gitea does not need a second placeholder token field.
- Enter the required credentials: baseUrl (required), apiKey (required).
Notes:
- Gitea is self-hosted / tenant-specific, so the base URL must come from the user’s own instance. Use the documented Authorization: token <access-token> header and remove the fabricated YOUR_TOKEN env field.
Nango
- Provider key:
nango - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://api.nango.dev/mcp
- Auth docs: https://docs.nango.dev/reference/api/authentication
- Required fields:
secretKeyrequired,connectionIdrequired,providerConfigKeyrequired
Setup steps:
- Copy your Nango secret key from Settings → API.
- Enter the connection ID for the account you want this MCP to use.
- Enter the provider config key (integration ID) that Nango should expose as tools.
- app.nango.dev → Settings → Environment Settings → Secret Key
Notes:
- Nango MCP uses three required headers: Authorization bearer secret key, connection-id, and provider-config-key.
Liveblocks
- Provider key:
liveblocks - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://api.liveblocks.io/v2
- Auth docs: https://liveblocks.io/docs/api-reference/rest-api-endpoints#authentication
- Required fields:
apiKeyrequired
Setup steps:
- Go to liveblocks.io/dashboard and log in (or create an account).
- Select your project (or create one), then click the "API keys" tab at the top.
- Your Secret Key is displayed there. For development projects it starts with "sk_dev_", for production "sk_prod_".
- Dev keys remain visible anytime. Production keys are shown only once at creation, copy immediately.
- Use it as: Authorization: Bearer sk_dev_YOUR_KEY. Store as LIVEBLOCKS_SECRET_KEY env var.
- liveblocks.io/dashboard → API keys → Copy secret key
Notes:
- Liveblocks documents the secret key as LIVEBLOCKS_SECRET_KEY; keep the runtime env aligned with that instead of inventing a second secretKey field.
Mixpanel
- Provider key:
mixpanel - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mixpanel.com
- Auth docs: https://docs.mixpanel.com/docs/features/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Mixpanel account when prompted.
- Authorize NeoTask to access your Mixpanel data.
- The connection is completed automatically.
PostHog
- Provider key:
posthog - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.posthog.com/mcp
- Auth docs: https://posthog.com/docs/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your PostHog account when prompted.
- Authorize NeoTask to access your PostHog data.
- The connection is completed automatically.
Microsoft Clarity
- Provider key:
microsoft-clarity - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://clarity.microsoft.com
- Auth docs: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
- Required fields:
apiKeyrequired
Setup steps:
- Open the Clarity AI assistant / MCP server settings page.
- Copy the Clarity API token.
- Paste that token into NeoTask. Do not add a second placeholder token field.
- clarity.microsoft.com → Settings → API access
Notes:
- Microsoft’s Clarity docs expose a single clarity_api_token credential; the extra YOUR_TOKEN field was fabricated by the generic parser and has been removed.
Audiense Insights
- Provider key:
audiense-insights - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp-audiense-insights.audiense.net/mcp
- Auth docs: https://developers.audiense.com
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Audiense Insights account when prompted.
- Authorize NeoTask to access your Audiense Insights data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
PowerBI
- Provider key:
powerbi - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://powerbi.microsoft.com
- Auth docs: https://learn.microsoft.com/en-us/power-bi/developer/embedded/register-app
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in with your Microsoft account when prompted.
- Authorize NeoTask to access your Power BI dashboards and reports.
- The connection is completed automatically.
Notes:
- Uses Microsoft Entra / Azure AD app registration.
Snowflake
- Provider key:
snowflake - Auth provider:
oauth - Reviewed classification:
custom_url_first - Service URL: https://www.snowflake.com
- Auth docs: https://docs.snowflake.com/en/developer-guide/sql-api/authenticating
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Snowflake account when prompted.
- Authorize NeoTask to query your data warehouse.
- The connection is completed automatically.
Databricks
- Provider key:
databricks - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.databricks.com
- Auth docs: https://docs.databricks.com/en/dev-tools/auth/pat.html
- Required fields:
hostUrlrequired,accessTokenrequired
Setup steps:
- Workspace → User Settings → Developer → Access tokens → Generate new token
MongoDB
- Provider key:
mongodb - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.mongodb.com
- Auth docs: https://www.mongodb.com/docs/mcp-server/
- Required fields:
connectionStringrequired
Setup steps:
- MongoDB Atlas → Database → Connect → Get connection string, OR use local connection URI
Supabase
- Provider key:
supabase - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.supabase.com/mcp
- Auth docs: https://supabase.com/docs/guides/getting-started/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Supabase account when prompted.
- Authorize NeoTask to access your Supabase data.
- The connection is completed automatically.
Neon
- Provider key:
neon - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://neon.tech
- Auth docs: https://neon.com/docs/ai/connect-mcp-clients-to-neon
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Neon account when prompted.
- Authorize NeoTask to access your Neon data.
- The connection is completed automatically.
Astra DB
- Provider key:
astra-db - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://astra.datastax.com
- Auth docs: https://docs.datastax.com/en/astra-db-serverless/administration/manage-application-tokens.html
- Required fields:
apiKeyrequired,databaseId
Setup steps:
- astra.datastax.com → Settings → Token Management → Generate Token
Elasticsearch
- Provider key:
elasticsearch - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.elastic.co
- Auth docs: https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-api-key.html
- Required fields:
hostUrlrequired,username,password,apiKey
Setup steps:
- Log into cloud.elastic.co and open your deployment.
- In Kibana, go to Stack Management → Security → API Keys.
- Click "Create API key", enter a name (e.g. "NeoTask"), optionally set an expiration and role restrictions.
- Click "Create API key" and copy the Base64-encoded key from the response.
- Your Elasticsearch URL is on the Cloud Console deployment overview page (format: https://xxx.es.region.aws.elastic.cloud:443).
- Enter both the URL and API key in the fields above.
- Enter the required credentials: hostUrl (required), username, password, apiKey.
ClickHouse
- Provider key:
clickhouse - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.clickhouse.cloud/mcp
- Auth docs: https://clickhouse.com/docs/en/cloud/manage/openapi
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your ClickHouse account when prompted.
- Authorize NeoTask to access your ClickHouse data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Neo4j
- Provider key:
neo4j - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://neo4j.com
- Auth docs: https://neo4j.com/docs/operations-manual/current/authentication-authorization/
- Required fields:
urirequired,usernamerequired,passwordrequired
Setup steps:
- Log into console.neo4j.io (Neo4j Aura) and open your database instance.
- Click "Connect" to see the connection URI (format: neo4j+s://xxxxx.databases.neo4j.io).
- The default username is "neo4j". The password was shown once at database creation.
- If you lost the password, click the three-dot menu on your instance and select "Reset password".
- For self-hosted Neo4j, use your Bolt URI (bolt://host:7687), username, and password.
- Enter the URI, username, and password in the fields above.
- Enter the required credentials: uri (required), username (required), password (required).
Pinecone
- Provider key:
pinecone - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.pinecone.io
- Auth docs: https://docs.pinecone.io/guides/get-started/authentication
- Required fields:
hostrequired,apiKeyrequired
Setup steps:
- Copy the Assistant host URL from Pinecone.
- Generate or copy a Pinecone API key.
- Paste both values into NeoTask. There is no separate YOUR_KEY field.
- app.pinecone.io → API Keys → Copy key
Notes:
- Pinecone MCP setup uses the assistant host plus a bearer API key. Remove the fabricated YOUR_KEY env/header field and keep only host + apiKey.
Chroma
- Provider key:
chroma - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.trychroma.com
- Auth docs: https://docs.trychroma.com/docs/cloud/authentication
- Required fields:
apiKeyrequired,host
Setup steps:
- Sign up at trychroma.com and log into the Chroma Cloud dashboard.
- Your API credentials (API Key, Tenant ID, Database name) are shown on the dashboard overview.
- Click the copy icon next to each value to copy them.
- For self-hosted Chroma, no API key is needed by default, set CHROMA_SERVER_AUTHN_CREDENTIALS if you enabled auth.
- Store the key as CHROMA_API_KEY, tenant as CHROMA_TENANT, database as CHROMA_DATABASE.
Qdrant
- Provider key:
qdrant - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://qdrant.tech
- Auth docs: https://qdrant.tech/documentation/cloud/authentication/
- Required fields:
apiKeyrequired,host
Setup steps:
- cloud.qdrant.io → Cluster → API Keys
MotherDuck
- Provider key:
motherduck - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.motherduck.com/mcp
- Auth docs: https://motherduck.com/docs/sql-reference/mcp/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your MotherDuck account when prompted.
- Authorize NeoTask to access your MotherDuck data.
- The connection is completed automatically.
Baserow
- Provider key:
baserow - Auth provider:
none - Reviewed classification:
custom_url_first - Auth docs: https://baserow.io/docs/apis/rest-api
Setup steps:
- Open Workspace settings → Baserow AI & MCP.
- Copy the unique MCP server URL for that workspace.
- Paste that exact URL into NeoTask. Baserow’s workspace MCP URL already carries the auth context, so no extra token field is required.
Notes:
- Baserow publishes a unique per-workspace MCP URL instead of a reusable API-key header form. Treat Baserow as custom-URL-first/no-auth-at-form-time so NeoTask stops inventing Authorization/Token fields.
Couchbase
- Provider key:
couchbase - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.couchbase.com
- Auth docs: https://docs.couchbase.com/cloud/get-started/connect.html
- Required fields:
connectionStringrequired,usernamerequired,passwordrequired
Setup steps:
- Log into Couchbase Capella at cloud.couchbase.com and open your cluster from the Operational Clusters page.
- Click the "Connect" tab at the top of the cluster page, then select the "SDK" sub-tab.
- Copy the public connection string displayed on the page (format: couchbases://cb.xxxxx.cloud.couchbase.com).
- To create credentials, click the "Settings" tab, then click "Cluster Access".
- Click "Create Access", enter an Access Name (your username), and set or auto-generate a password.
- Select the buckets, scopes, and access level (Read/Write) for this user, then click "Create Cluster Access".
- Important: copy the password immediately, you cannot view it again after creation.
- Enter the required credentials: connectionString (required), username (required), password (required).
Meilisearch
- Provider key:
meilisearch - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.meilisearch.com
- Auth docs: https://www.meilisearch.com/docs/learn/security/basic_security
- Required fields:
hostrequired,masterKeyrequired
Setup steps:
- For Meilisearch Cloud: log into meilisearch.com/cloud, open your project, go to project settings, and click "API Keys" in the sidebar.
- Copy the "Default Admin API Key" for full access or "Default Search API Key" for search-only access.
- For self-hosted: set the MEILI_MASTER_KEY environment variable (min 16 bytes) before starting Meilisearch.
- Retrieve auto-generated API keys via: curl -X GET http://localhost:7700/keys -H "Authorization: Bearer YOUR_MASTER_KEY".
- Use the Admin API key for NeoTask, never use the master key directly for operations.
- cloud.meilisearch.com → Project → Settings → API Keys
Notes:
- Meilisearch docs use MEILI_HTTP_ADDR and MEILI_MASTER_KEY; remove the fabricated YOUR_MASTER_KEY placeholder.
Algolia
- Provider key:
algolia - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://{applicationId}.algolia.net
- Auth docs: https://www.algolia.com/doc/guides/security/api-keys/
- Required fields:
applicationIdrequired,adminApiKeyrequired
Setup steps:
- Log into the Algolia dashboard at dashboard.algolia.com.
- Your Application ID is shown in the top center of the page (also visible in the URL after /apps/).
- In the left sidebar, click "Settings", then under "Team and Access" click "API Keys".
- Or go directly to dashboard.algolia.com/account/api-keys/all.
- The Admin API Key is hidden by default, click the lock/eye icon to reveal it, then copy it.
- For better security, create a scoped API key with only the permissions you need instead of using the Admin key.
- dashboard.algolia.com → Settings → API Keys → Copy Application ID + Admin API Key
Notes:
- Algolia authenticates with X-Algolia-Application-Id and X-Algolia-API-Key headers against the application-specific host.
FalkorDB
- Provider key:
falkordb - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.falkordb.com
- Auth docs: https://docs.falkordb.com/cloud/
- Required fields:
hostrequired,port
Setup steps:
- Log into FalkorDB Cloud at app.falkordb.cloud and go to the "Instances" tab.
- Click on your instance name to open the Instance Detail page.
- Click the "Connectivity" tab to find your Host and Port.
- The Username and Password are what you set when creating the instance (default username: "falkordb").
- If you need to create a new instance: click "Create Deployment Instance", choose a plan and region, set a username and password, then click "Create".
- Enter the required credentials: host (required), port.
Atlan
- Provider key:
atlan - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://atlan.com
- Auth docs: https://developer.atlan.com/getting-started/create-api-token/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Atlan account when prompted.
- Authorize NeoTask to access your Atlan data.
- The connection is completed automatically.
Milvus
- Provider key:
milvus - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://milvus.io
- Auth docs: https://docs.zilliz.com/docs/manage-api-keys
- Required fields:
urirequired,apiKeyrequired
Setup steps:
- Log into Zilliz Cloud at cloud.zilliz.com.
- In the left sidebar, navigate to Security > Authentication > API Keys.
- Your personal API key (auto-generated at registration) is listed at the top, click the copy icon.
- To create a custom key: click "+ API Key", enter a name (max 64 chars), assign organization/project roles, and save.
- Copy the key immediately, it is only shown once after creation.
- Use the key as: Authorization: Bearer YOUR_API_KEY.
- Enter the required credentials: uri (required), apiKey (required).
Notes:
- Milvus docs use MILVUS_URI plus optional MILVUS_TOKEN; remove the fabricated YOUR_API_KEY placeholder.
BrightData
- Provider key:
brightdata - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://brightdata.com
- Auth docs: https://docs.brightdata.com/api-reference/introduction
- Required fields:
apiKeyrequired
Setup steps:
- brightdata.com → Control Panel → Settings → API token
Stripe
- Provider key:
stripe - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.stripe.com
- Auth docs: https://docs.stripe.com/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Stripe account when prompted.
- Authorize NeoTask to access your Stripe data.
- The connection is completed automatically.
Shopify Storefront
- Provider key:
shopify-storefront - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://{shop}.myshopify.com/api/mcp
- Auth docs: https://shopify.dev/docs/apps/build/storefront-mcp/servers/storefront
Setup steps:
- No authentication is required for this integration.
Notes:
- Storefront MCP uses a per-store https://{shop}.myshopify.com/api/mcp endpoint and does not require auth.
Shopify Customer Accounts
- Provider key:
shopify - Auth provider:
oauth - Reviewed classification:
custom_url_first - Service URL: https://{shop-domain}/customer/api/mcp
- Auth docs: https://shopify.dev/docs/apps/build/storefront-mcp/servers/customer-account
Setup steps:
- Paste the exact Shopify Customer Accounts MCP endpoint first.
- Save your Shopify Client ID and Client Secret.
- Then continue the OAuth flow for that exact Customer Accounts endpoint.
Notes:
- Shopify Customer Accounts MCP uses a per-store /customer/api/mcp endpoint. The exact Customer Accounts MCP URL must be saved before OAuth capability/auth probing can run. Customer Accounts uses OAuth 2.0 Authorization Code with PKCE after the exact Shopify URL is saved.
Shopify Catalog
- Provider key:
shopify-catalog - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://discover.shopifyapps.com/global/mcp
- Auth docs: https://shopify.dev/docs/agents/catalog/mcp
- Required fields:
apiKeyrequired
Setup steps:
- Generate the Shopify Catalog MCP bearer token from your developer setup.
- Paste the token into NeoTask to connect the global Catalog MCP.
Notes:
- Shopify Catalog MCP uses the hosted global endpoint https://discover.shopifyapps.com/global/mcp. It authenticates with a bearer token rather than Customer Accounts OAuth.
Shopify Checkout
- Provider key:
shopify-checkout - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://{shop-domain}/api/ucp/mcp
- Auth docs: https://shopify.dev/docs/agents/checkout/mcp
- Required fields:
apiKeyrequired
Setup steps:
- Paste the exact Shopify Checkout MCP endpoint first.
- Generate the Checkout MCP bearer token from your Shopify developer setup.
- Paste the token into NeoTask to connect that checkout surface.
Notes:
- Shopify Checkout MCP uses a per-store /api/ucp/mcp endpoint and bearer-token auth. The exact store checkout MCP URL must be saved before the token can be used.
Alpaca
- Provider key:
alpaca - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://alpaca.markets
- Auth docs: https://docs.alpaca.markets/docs/getting-started
- Required fields:
apiKeyrequired,secretKeyrequired
Setup steps:
- app.alpaca.markets → Paper/Live → API Keys → Generate
AlphaVantage
- Provider key:
alphavantage - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.alphavantage.co
- Auth docs: https://www.alphavantage.co/support/#api-key
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your AlphaVantage account when prompted.
- Authorize NeoTask to access your AlphaVantage data.
- The connection is completed automatically.
Airwallex
- Provider key:
airwallex - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp-demo.airwallex.com/developer
- Auth docs: https://www.airwallex.com/docs/developer-tools/ai/developer-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Airwallex account when prompted.
- Authorize NeoTask to access your Airwallex data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Adfin
- Provider key:
adfin - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.adfin.com
- Auth docs: https://docs.adfin.com/reference/welcome-1
- Required fields:
apiKeyrequired
Setup steps:
- Log into your Adfin console and open the API settings for your account.
- Generate or copy the Adfin API key used for MCP/API access.
- Paste that API key into NeoTask to connect the Adfin MCP endpoint.
Chargebee
- Provider key:
chargebee - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.chargebee.com
- Auth docs: https://www.chargebee.com/docs/2.0/api_keys.html
- Required fields:
apiKeyrequired,siterequired
Setup steps:
- Log into your Chargebee site (e.g. your-site.chargebee.com).
- In the left sidebar, click "Settings", then click "Configure Chargebee".
- Under "API Keys and Webhooks", click "API Keys".
- To create a new key: click "Add an API Key", select the key type (Read-Only or Full Access), name it, and click "Create Key".
- Copy the API key. You must be an admin or site owner to view/create keys.
- Note: test site and live site have separate API keys.
- Also enter the Chargebee site name for the account you want NeoTask to use.
Flutterwave
- Provider key:
flutterwave - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://flutterwave.com
- Auth docs: https://developer.flutterwave.com/docs/integration-guides/authentication
- Required fields:
apiKeyrequired
Setup steps:
- dashboard.flutterwave.com → Settings → API → Secret Key
Paystack
- Provider key:
paystack - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://paystack.com
- Auth docs: https://paystack.com/docs/api/
- Required fields:
apiKeyrequired
Setup steps:
- dashboard.paystack.com → Settings → API Keys & Webhooks → Secret Key
Razorpay
- Provider key:
razorpay - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.razorpay.com/mcp
- Auth docs: https://razorpay.com/docs/payments/dashboard/account-settings/api-keys/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Razorpay account when prompted.
- Authorize NeoTask to access your Razorpay data.
- The connection is completed automatically.
CoinGecko
- Provider key:
coingecko - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.coingecko.com
- Auth docs: https://docs.coingecko.com/reference/setting-up-your-api-key
- Required fields:
apiKeyrequired
Setup steps:
- coingecko.com → API → Get started → Generate key (free tier available)
Commerce Layer
- Provider key:
commerce-layer - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://commercelayer.io
- Auth docs: https://docs.commercelayer.io/core/authentication
- Required fields:
clientIdrequired,clientSecretrequired,baseEndpointrequired
Setup steps:
- Log into the Commerce Layer Dashboard at dashboard.commercelayer.io.
- In the left sidebar, click "Developers", then select "API credentials".
- Click the "+ New" button in the top-right corner.
- Select the "Integration" card (for server-to-server access), enter a name, and choose a role (Read-only or Admin).
- Click "Create" and copy the Client ID, Client Secret, and Base Endpoint from the details page.
- The Base Endpoint is your organization-specific API URL (e.g. https://yourdomain.commercelayer.io).
- Enter the required credentials: clientId (required), clientSecret (required), baseEndpoint (required).
Aiera
- Provider key:
aiera - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.aiera.com
- Auth docs: https://docs.aiera.com/docs/authentication
- Required fields:
apiKeyrequired
Setup steps:
- Aiera does not offer self-service signup, access is obtained through a sales-led process.
- Request a demo at aiera.com/demo/ by filling out the contact form.
- After completing the sales process and account provisioning, Aiera provides your API key.
- All API requests use the X-API-Key header. Base URL: premium.aiera.com/api/.
- Enter the required API key: apiKey (required).
HubSpot
- Provider key:
hubspot - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.hubspot.com/anthropic
- Auth docs: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your HubSpot account when prompted.
- Authorize NeoTask to access your CRM and marketing data.
- The connection is completed automatically.
Apollo.io
- Provider key:
apollo-io - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.apollo.io/mcp
- Auth docs: https://apolloio.github.io/apollo-api-docs/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Apollo.io account when prompted.
- Authorize NeoTask to access your Apollo.io data.
- The connection is completed automatically.
Notes:
- Official provider-owned MCP at mcp.apollo.io/mcp; DCR verified 2026-05-30 (client_id issued). Registry previously pointed at api.apollo.io (REST API).
Outreach
- Provider key:
outreach - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.outreach.io
- Auth docs: https://developers.outreach.io/api/oauth/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Outreach account when prompted.
- Authorize NeoTask to access your Outreach data.
- The connection is completed automatically.
Hunter
- Provider key:
hunter - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://hunter.io
- Auth docs: https://hunter.io/api-documentation/v2
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Hunter account when prompted.
- Authorize NeoTask to access your Hunter data.
- The connection is completed automatically.
Explorium
- Provider key:
explorium - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.explorium.ai
- Auth docs: https://docs.explorium.ai/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Explorium account when prompted.
- Authorize NeoTask to access your Explorium data.
- The connection is completed automatically.
Zoho
- Provider key:
zoho - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.zoho.com/mcp
- Auth docs: https://www.zoho.com/crm/developer/docs/api/v7/oauth-overview.html
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Zoho account when prompted.
- Authorize NeoTask to access your Zoho data.
- The connection is completed automatically.
ActiveCampaign
- Provider key:
activecampaign - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.activecampaign.com/mcp
- Auth docs: https://help.activecampaign.com/hc/en-us/articles/22566179229596-Get-started-with-the-ActiveCampaign-MCP-Server
- Required fields:
baseUrlrequired,apiKeyrequired
Setup steps:
- ActiveCampaign → Settings → Developer → API Access → Copy URL + Key
Klaviyo
- Provider key:
klaviyo - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.klaviyo.com/mcp
- Auth docs: https://developers.klaviyo.com/en/docs/klaviyo_mcp_server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Klaviyo account when prompted.
- Authorize NeoTask to access your Klaviyo data.
- The connection is completed automatically.
Meta Ads
- Provider key:
meta-ads - Auth provider:
oauth - Reviewed classification:
managed_oauth - Service URL: https://mcp.facebook.com/ads
- Auth docs: https://www.facebook.com/business/help/1456422242197840
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Meta Ads account when prompted.
- Authorize NeoTask to access your Meta Ads data.
- The connection is completed automatically.
Notes:
- Meta Ads MCP is a hosted remote MCP at https://mcp.facebook.com/ads. OAuth protected-resource metadata advertises scopes ads_management, ads_read, catalog_management, and business_management. OAuth authorization-server metadata advertises PKCE S256 and a registration endpoint, but direct registration currently returns invalid_client_metadata: Dynamic registration is not available for this client. Do not show custom service URL, API key, client ID, or client secret fields to users; NeoTask should use proxy-managed OAuth credentials for this provider.
Customer.io
- Provider key:
customer-io - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://customer.io
- Auth docs: https://docs.customer.io/ai/mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Customer.io account when prompted.
- Authorize NeoTask to access your Customer.io data.
- The connection is completed automatically.
Ahrefs
- Provider key:
ahrefs - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.ahrefs.com/mcp/mcp
- Auth docs: https://ahrefs.com/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Ahrefs account when prompted.
- Authorize NeoTask to access your Ahrefs data.
- The connection is completed automatically.
AirOps
- Provider key:
airops - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://app.airops.com/mcp
- Auth docs: https://docs.airops.com/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your AirOps account when prompted.
- Authorize NeoTask to access your AirOps data.
- The connection is completed automatically.
BuiltWith
- Provider key:
builtwith - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://builtwith.com
- Auth docs: https://api.builtwith.com/
- Required fields:
apiKeyrequired
Setup steps:
- api.builtwith.com → Sign up → Get API key
AWS
- Provider key:
aws - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://aws.amazon.com
- Auth docs: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html
- Required fields:
accessKeyIdrequired,secretAccessKeyrequired,regionrequired
Setup steps:
- AWS Console → IAM → Users → Security credentials → Create access key
Azure
- Provider key:
azure - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://azure.microsoft.com
- Auth docs: https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in with your Microsoft Azure account when prompted.
- Authorize NeoTask to access your Azure resources.
- The connection is completed automatically.
Notes:
- Uses Microsoft Entra / Azure AD app registration.
Cloudflare
- Provider key:
cloudflare - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.cloudflare.com/mcp
- Auth docs: https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Cloudflare account when prompted.
- Authorize NeoTask to access your Cloudflare data.
- The connection is completed automatically.
Terraform
- Provider key:
terraform - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.terraform.io
- Auth docs: https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens
- Required fields:
organizationrequired,apiTokenrequired
Setup steps:
- app.terraform.io → Settings → API Tokens → Generate
Firebase
- Provider key:
firebase - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://firebase.google.com
- Auth docs: https://firebase.google.com/docs/admin/setup#initialize_the_sdk_in_non-google_environments
- Required fields:
projectIdrequired,serviceAccountJsonrequired
Setup steps:
- Go to the Firebase Console at console.firebase.google.com and select your project.
- Click the gear icon next to "Project Overview" and select "Project settings".
- Click the "Service accounts" tab, then click "Generate new private key" and confirm.
- A JSON file downloads, paste its entire content into the Service Account JSON field.
- Your Project ID is shown at the top of the Project Settings page (General tab).
- Enter the required credentials: projectId (required), serviceAccountJson (required).
Confluent
- Provider key:
confluent - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://confluent.cloud
- Auth docs: https://docs.confluent.io/cloud/current/access-management/authenticate/api-keys/api-keys.html
- Required fields:
apiKeyrequired,apiSecretrequired,cluster
Setup steps:
- confluent.cloud → API Keys → Create Key
Aiven
- Provider key:
aiven - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://aiven.io
- Auth docs: https://aiven.io/docs/platform/howto/create_authentication_token
- Required fields:
apiKeyrequired
Setup steps:
- console.aiven.io → User Information → Authentication → API tokens
Grafana
- Provider key:
grafana - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://grafana.com
- Auth docs: https://grafana.com/docs/grafana/latest/administration/service-accounts/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Grafana account when prompted.
- Authorize NeoTask to access your Grafana data.
- The connection is completed automatically.
Datadog
- Provider key:
datadog - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.datadoghq.com
- Auth docs: https://docs.datadoghq.com/bits_ai/mcp_server/setup/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Datadog account when prompted.
- Authorize NeoTask to access your Datadog data.
- The connection is completed automatically.
Sentry
- Provider key:
sentry - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.sentry.dev/mcp
- Auth docs: https://docs.sentry.io/product/sentry-mcp/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Sentry account when prompted.
- Authorize NeoTask to access your Sentry data.
- The connection is completed automatically.
Dynatrace
- Provider key:
dynatrace - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.dynatrace.com
- Auth docs: https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-intelligence-integrations/dynatrace-mcp
- Required fields:
environment_urlrequired,platform_tokenrequired
Setup steps:
- Log into your Dynatrace Platform environment.
- Go to Account Management > Identity & access management > Platform Tokens, then click "Add new Platform token".
- Assign the required scopes, save, and copy the generated token immediately.
- Copy your environment URL (e.g. https://abc12345.apps.dynatrace.com) and the token.
- Enter the required credentials: environment_url (required), platform_token (required).
PagerDuty
- Provider key:
pagerduty - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.pagerduty.com
- Auth docs: https://support.pagerduty.com/docs/api-access-keys
- Required fields:
apiKeyrequired
Setup steps:
- PagerDuty → Integrations → API Access Keys → Create New API Key
Honeycomb
- Provider key:
honeycomb - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.honeycomb.io/mcp
- Auth docs: https://docs.honeycomb.io/integrations/mcp/configuration-guide
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Honeycomb account when prompted.
- Authorize NeoTask to access your Honeycomb data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Axiom
- Provider key:
axiom - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://axiom.co
- Auth docs: https://axiom.co/docs/console/intelligence/mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Axiom account when prompted.
- Authorize NeoTask to access your Axiom data.
- The connection is completed automatically.
Netdata
- Provider key:
netdata - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.netdata.cloud
- Auth docs: https://learn.netdata.cloud/docs/netdata-cloud/authentication-and-authorization/api-tokens
- Required fields:
apiKeyrequired
Setup steps:
- app.netdata.cloud → Settings → API tokens
Auth0
- Provider key:
auth0 - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://auth0.com
- Auth docs: https://auth0.com/docs/get-started/auth0-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Auth0 account when prompted.
- Authorize NeoTask to access your Auth0 data.
- The connection is completed automatically.
CrowdStrike Falcon
- Provider key:
crowdstrike-falcon - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.crowdstrike.com
- Auth docs: https://falcon.crowdstrike.com/documentation/46/crowdstrike-oauth2-based-apis
- Required fields:
clientIdrequired,clientSecretrequired,baseUrl
Setup steps:
- Log into the CrowdStrike Falcon console as an administrator.
- In the left sidebar, click the "Support and resources" icon, then under "Resources and tools" select "API Clients and Keys".
- Click "Add new API client", enter a name and description.
- Under API Scopes, toggle the permissions you need (e.g. Detections: Read, Hosts: Read).
- Click "Add" and copy the Client ID and Secret immediately, the secret is shown only once.
- Enter the required credentials: clientId (required), clientSecret (required), baseUrl.
Contrast Security
- Provider key:
contrast-security - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.contrastsecurity.com
- Auth docs: https://docs.contrastsecurity.com/en/personal-keys.html
- Required fields:
apiKeyrequired,serviceKeyrequired,organization_idrequired,base_url
Setup steps:
- Log into Contrast Security TeamServer.
- Click your user avatar in the top-right corner and select "User Settings".
- On the Profile page, scroll down to the "Your Keys" section.
- Copy your Organization ID, API Key, Service Key, and Username. The Org ID and API Key are shared; the Service Key is unique per user.
- Click "Rotate" next to the Service Key if you need to regenerate it.
- Enter the required credentials: apiKey (required), serviceKey (required), organization_id (required), base_url.
GitGuardian
- Provider key:
gitguardian - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.gitguardian.com
- Auth docs: https://docs.gitguardian.com/api-docs/authentication
- Required fields:
apiKeyrequired
Setup steps:
- dashboard.gitguardian.com → API → Personal access tokens → Create
Endor Labs
- Provider key:
endor-labs - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://www.endorlabs.com
- Auth docs: https://docs.endorlabs.com/secure-ai-coding/mcp-server/
- Required fields:
apiKeyrequired
Setup steps:
- Log into Endor Labs and generate an API key or access token for MCP/API access.
- Paste that key into NeoTask to connect the Endor Labs MCP endpoint.
- Enterprise customers can still use their preferred SSO mode, but the MCP credential stored in NeoTask should be the issued API token.
BoostSecurity
- Provider key:
boostsecurity - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://www.boostsecurity.io
- Auth docs: https://docs.boostsecurity.io/user-guide/reference-guides/agentic-ai/boost-mcp-server.html
Setup steps:
- No authentication is required for this integration.
Asgardeo
- Provider key:
asgardeo - Auth provider:
credentials - Reviewed classification:
custom_url_first - Service URL: https://wso2.com/asgardeo
- Auth docs: https://wso2.com/asgardeo/docs/sdks/asgardeo-mcp-server/
- Required fields:
base_urlrequired,client_idrequired,client_secretrequired
Setup steps:
- Enter your exact Asgardeo tenant or base URL first.
- Create or reuse an Asgardeo application for the MCP server.
- Paste the client ID and client secret from that application.
- Enter the required credentials: base_url (required), client_id (required), client_secret (required).
Drata
- Provider key:
drata - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://drata.com
- Auth docs: https://developers.drata.com/docs/openapi/reference/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Drata account when prompted.
- Authorize NeoTask to access your Drata data.
- The connection is completed automatically.
Hugging Face
- Provider key:
hugging-face - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://huggingface.co/mcp?login&gradio=none
- Auth docs: https://huggingface.co/docs/hub/security-tokens
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Hugging Face account when prompted.
- Authorize NeoTask to access your Hugging Face data.
- The connection is completed automatically.
Arize Phoenix
- Provider key:
arize-phoenix - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://phoenix.arize.com
- Auth docs: https://arize.com/docs/phoenix/integrations/frameworks-and-platforms/model-context-protocol/phoenix-mcp-server
- Required fields:
apiKeyrequired
Setup steps:
- Sign up at app.phoenix.arize.com (or log into your self-hosted Phoenix instance).
- Click "Settings" in the left navigation sidebar, then click "Keys".
- Create a System API Key (requires admin) or User API Key.
- Copy the key immediately, it is shown only once. Your base URL is the URL you use to access Phoenix.
AgentOps
- Provider key:
agentops - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.agentops.ai
- Auth docs: https://docs.agentops.ai/quickstart
- Required fields:
apiKeyrequired
Setup steps:
- Sign up at app.agentops.ai and log in.
- Click "Settings" in the sidebar, then click "Projects & API Keys".
- Your API key is displayed on this page, copy it.
- Enter the required API key: apiKey (required).
E2B
- Provider key:
e2b - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://e2b.dev
- Auth docs: https://e2b.dev/docs
- Required fields:
apiKeyrequired
Setup steps:
- e2b.dev → Dashboard → Copy API Key
Composio
- Provider key:
composio - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://connect.composio.dev/mcp
- Auth docs: https://docs.composio.dev/introduction/intro/quickstart
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Composio account when prompted.
- Authorize NeoTask to access your Composio data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Label Studio
- Provider key:
label-studio - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://labelstud.io
- Auth docs: https://labelstud.io/guide/access_tokens
- Required fields:
base_urlrequired,api_keyrequired
Setup steps:
- Enter the URL for your Label Studio instance.
- Generate a Label Studio API key / personal access token.
- Paste both values into NeoTask. Remove the fabricated YOUR_TOKEN field.
- Enter the required credentials: base_url (required), api_key (required).
Notes:
- Label Studio MCP setup uses LABEL_STUDIO_URL plus LABEL_STUDIO_API_KEY-style credentials. NeoTask now keeps only the real base_url + api_key pair and stops inventing a YOUR_TOKEN env field.
Exa
- Provider key:
exa - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.exa.ai/mcp
- Auth docs: https://docs.exa.ai/reference/getting-started
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Exa account when prompted.
- Authorize NeoTask to access your Exa data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Perplexity
- Provider key:
perplexity - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.perplexity.ai/rest/computer/mcp
- Auth docs: https://docs.perplexity.ai/guides/getting-started
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Perplexity account when prompted.
- Authorize NeoTask to access your Perplexity data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Kagi Search
- Provider key:
kagi-search - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://kagi.com
- Auth docs: https://help.kagi.com/kagi/api/overview.html
- Required fields:
apiKeyrequired
Setup steps:
- Log into Kagi at kagi.com.
- Go to Settings > Advanced > API portal (or go directly to kagi.com/settings/api).
- Click "Generate API Token" and copy it.
- Add API credits at kagi.com/settings/billing_api ($25 per 1,000 queries).
- Enter the required API key: apiKey (required).
AllVoiceLab
- Provider key:
allvoicelab - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.allvoicelab.com
- Auth docs: https://docs.allvoicelab.com/
- Required fields:
apiKeyrequired
Setup steps:
- Sign up at allvoicelab.com and go to your Workbench at allvoicelab.com/workbench/api-keys.
- Your API key is displayed on this page, copy it.
- Your API domain depends on your account region: Global = api.allvoicelab.com, China = api.allvoicelab.cn.
Cartesia
- Provider key:
cartesia - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://cartesia.ai
- Auth docs: https://docs.cartesia.ai/getting-started/overview
- Required fields:
apiKeyrequired
Setup steps:
- Sign up at play.cartesia.ai (free tier available with 20,000 credits/month).
- Navigate to "API Keys" in the left sidebar (or go to play.cartesia.ai/keys).
- Click "New" to create a new API key and copy it.
- Enter the required API key: apiKey (required).
PlayAI
- Provider key:
playai - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://play.ai
- Auth docs: https://docs.play.ai/api-reference/authorization
- Required fields:
userIdrequired,secretKeyrequired
Setup steps:
- Sign up at play.ai and log in.
- Navigate to the "For Developers" page at play.ai/api/keys.
- Your API Key and User ID are both displayed on this page, copy both values.
- Enter the required credentials: userId (required), secretKey (required).
DeepL
- Provider key:
deepl - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.deepl.com
- Auth docs: https://developers.deepl.com/docs/getting-started/auth
- Required fields:
apiKeyrequired
Setup steps:
- deepl.com → Account → Authentication Key for DeepL API
Grain
- Provider key:
grain - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.grain.com/_/mcp
- Auth docs: https://grain.com/integrations
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Grain account when prompted.
- Authorize NeoTask to access your Grain data.
- The connection is completed automatically.
Kaltura
- Provider key:
kaltura - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://www.kaltura.com
- Auth docs: https://developer.kaltura.com/api-docs/VPaaS-API-Getting-Started/
- Required fields:
partnerIdrequired,adminSecretrequired
Setup steps:
- Log into the Kaltura Management Console (KMC) at kmc.kaltura.com.
- Click the "Settings" tab in the top navigation, then click the "Integration" sub-tab.
- Copy your Partner ID (numeric) and Administrator Secret from this page.
- Your User ID is your Kaltura admin account email. The Service URL is https://cdnapisec.kaltura.com for SaaS (or your custom URL for on-prem).
- Never expose the Admin Secret in client-side code, generate Kaltura Sessions server-side.
- Enter the required credentials: partnerId (required), adminSecret (required).
2slides
- Provider key:
2slides - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.2slides.com
- Auth docs: https://www.2slides.com/docs
- Required fields:
apiKeyrequired
Setup steps:
- Sign up at 2slides.com and log in.
- Navigate to 2slides.com/api and find the "API Keys" section.
- Click "Create a new API Key", enter a name and set permissions, then click Save/Create.
- Copy the API key immediately (format: sk-2slides-...), it is shown only once and cannot be recovered.
- Enter the required API key: apiKey (required).
10x Genomics Cloud
- Provider key:
10x-genomics-cloud - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.10xgenomics.com
- Auth docs: https://www.10xgenomics.com/support/cloud
- Required fields:
apiKeyrequired
Setup steps:
- Create an account at cloud.10xgenomics.com and enable Multi-Factor Authentication (MFA is mandatory).
- Navigate to cloud.10xgenomics.com/account/security.
- Click "Generate New Access Token" and copy the token immediately using the copy button.
- Store the token securely, treat it like a password. It grants access to all data in your 10x Cloud account.
- Enter the required API key: apiKey (required).
EduBase
- Provider key:
edubase - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.edubase.net/mcp
- Auth docs: https://www.edubase.net/help/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your EduBase account when prompted.
- Authorize NeoTask to access your EduBase data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
PubMed
- Provider key:
pubmed - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://pubmed.mcp.claude.com/mcp
Setup steps:
- No authentication is required for this integration.
Aqara
- Provider key:
aqara - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://www.aqara.com
- Auth docs: https://github.com/aqara/aqara-mcp-server
- Required fields:
apiKeyrequired
Setup steps:
- Visit https://cdn.aqara.com/app/mcpserver/login.html and log in with your Aqara account.
- After login, copy the provided API Key and Base URL.
- Keep your API key secure and do not share it.
- Enter the required API key: apiKey (required).
Baidu Map
- Provider key:
baidu-map - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://lbsyun.baidu.com
- Auth docs: https://lbsyun.baidu.com/apiconsole/key
- Required fields:
apiKeyrequired
Setup steps:
- Register a Baidu account at passport.baidu.com (overseas registration available, the portal is Chinese-only, use browser translation).
- Go to lbsyun.baidu.com/apiconsole/key and complete developer verification when prompted.
- Click "Create Application" (创建应用): enter an Application Name, select "Server" (服务端) as Application Type, and enable "MCP (SSE)" under services.
- Set the IP Whitelist (use * for testing). Click Submit/Create.
- Your AK (Access Key) appears immediately in the application list. Copy it.
- Note: Full production access requires a Chinese business license and phone number.
- Enter the required API key: apiKey (required).
Mapbox
- Provider key:
mapbox - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://www.mapbox.com
- Auth docs: https://docs.mapbox.com/help/getting-started/access-tokens/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Mapbox account when prompted.
- Authorize NeoTask to access your Mapbox data.
- The connection is completed automatically.
Gamma
- Provider key:
gamma - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.gamma.app/mcp
- Auth docs: https://developers.gamma.app/docs/gamma-mcp-server
Setup steps:
- Connect to the Gamma MCP server at mcp.gamma.app/mcp.
- When prompted, click "Allow" to grant access to your Gamma account.
- Select the appropriate workspace if you have multiple.
Granola
- Provider key:
granola - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.granola.ai/mcp
- Auth docs: https://docs.granola.ai/help-center/sharing/integrations/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Granola account when prompted.
- Authorize NeoTask to access your Granola data.
- The connection is completed automatically.
Smartsheet
- Provider key:
smartsheet - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://mcp.smartsheet.com
- Auth docs: https://smartsheet.redoc.ly/tag/APIAuthentication
- Required fields:
apiKeyrequired
Setup steps:
- app.smartsheet.com → Account → Personal Settings → API Access → Generate
Wix
- Provider key:
wix - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.wix.com/mcp
- Auth docs: https://dev.wix.com/docs/sdk/articles/use-the-wix-mcp/about-the-wix-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Wix account when prompted.
- Authorize NeoTask to access your Wix data.
- The connection is completed automatically.
Jotform
- Provider key:
jotform - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.jotform.com/mcp-app
- Auth docs: https://www.jotform.com/developers/mcp/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Jotform account when prompted.
- Authorize NeoTask to access your Jotform data.
- The connection is completed automatically.
Intercom
- Provider key:
intercom - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.intercom.com/mcp
- Auth docs: https://developers.intercom.com/docs/build-an-integration/learn-more/authentication/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Intercom account when prompted.
- Authorize NeoTask to access your Intercom data.
- The connection is completed automatically.
Fireflies
- Provider key:
fireflies - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.fireflies.ai/mcp
- Auth docs: https://docs.fireflies.ai/graphql-api/authentication
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Fireflies account when prompted.
- Authorize NeoTask to access your Fireflies data.
- The connection is completed automatically.
Miro
- Provider key:
miro - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.miro.com/
- Auth docs: https://developers.miro.com/docs/miro-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Miro account when prompted.
- Authorize NeoTask to access your Miro data.
- The connection is completed automatically.
Vercel
- Provider key:
vercel - Auth provider:
oauth - Reviewed classification:
managed_dcr_broken - Service URL: https://mcp.vercel.com
- Auth docs: https://vercel.com/docs/mcp/vercel-mcp
Setup steps:
- Managed OAuth is not fully usable for Vercel yet because the provider rejects our callback host.
- Use the manual setup option for now.
Notes:
- Provider has rejected redirect registration in live testing and should stay on manual/preregistered fallback until corrected.
Context7
- Provider key:
context7 - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.context7.com/mcp
- Auth docs: https://context7.com/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Context7 account when prompted.
- Authorize NeoTask to access your Context7 data.
- The connection is completed automatically.
Ramp
- Provider key:
ramp - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.ramp.com/developer/mcp
- Auth docs: https://docs.ramp.com/developer-api/v1/guides/ramp-mcp-remote
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Ramp account when prompted.
- Authorize NeoTask to access your Ramp data.
- The connection is completed automatically.
PayPal
- Provider key:
paypal - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.paypal.com
- Auth docs: https://developer.paypal.com/tools/mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your PayPal account when prompted.
- Authorize NeoTask to access your PayPal data.
- The connection is completed automatically.
Square
- Provider key:
square - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.squareup.com/sse
- Auth docs: https://developer.squareup.com/docs/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Square account when prompted.
- Authorize NeoTask to access your Square data.
- The connection is completed automatically.
Mercury
- Provider key:
mercury - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.mercury.com/mcp
- Auth docs: https://docs.mercury.com/docs/what-is-mercury-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Mercury account when prompted.
- Authorize NeoTask to access your Mercury data.
- The connection is completed automatically.
S&P Global
- Provider key:
s-p-global - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://kfinance.kensho.com/integrations/mcp
- Auth docs: https://docs.kensho.com/llmreadyapi/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your S&P Global account when prompted.
- Authorize NeoTask to access your S&P Global data.
- The connection is completed automatically.
Morningstar
- Provider key:
morningstar - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.morningstar.com/mcp
- Auth docs: https://developer.morningstar.com/direct-web-services/documentation/morningstar-mcp-server/about
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Morningstar account when prompted.
- Authorize NeoTask to access your Morningstar data.
- The connection is completed automatically.
Attio
- Provider key:
attio - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.attio.com/mcp
- Auth docs: https://docs.attio.com/mcp/overview
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Attio account when prompted.
- Authorize NeoTask to access your Attio data.
- The connection is completed automatically.
Close
- Provider key:
close - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.close.com/mcp
- Auth docs: https://developer.close.com/topics/authentication/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Close account when prompted.
- Authorize NeoTask to access your Close data.
- The connection is completed automatically.
ZoomInfo
- Provider key:
zoominfo - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.zoominfo.com/mcp
- Auth docs: https://api-docs.zoominfo.com/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your ZoomInfo account when prompted.
- Authorize NeoTask to access your ZoomInfo data.
- The connection is completed automatically.
Bitly
- Provider key:
bitly - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api-ssl.bitly.com/v4/mcp
- Auth docs: https://dev.bitly.com/docs/getting-started/authentication/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Bitly account when prompted.
- Authorize NeoTask to access your Bitly data.
- The connection is completed automatically.
AWS Marketplace
- Provider key:
aws-marketplace - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://marketplace-mcp.us-east-1.api.aws/mcp
- Auth docs: https://docs.aws.amazon.com/marketplace/latest/userguide/what-is-marketplace.html
- Required fields:
accessKeyIdrequired,secretAccessKeyrequired,regionrequired
Setup steps:
- Create or reuse an AWS IAM access key pair with the required Marketplace MCP permissions.
- Paste the access key ID, secret access key, and AWS region for the endpoint you are targeting.
- Enter the required credentials: accessKeyId (required), secretAccessKey (required), region (required).
GoDaddy
- Provider key:
godaddy - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://api.godaddy.com/v1/domains/mcp
- Auth docs: https://developer.godaddy.com/keys
Setup steps:
- No authentication is required for this integration.
Notes:
- Official GoDaddy MCP docs state the domain names MCP works without a GoDaddy account or API credentials.
Indeed
- Provider key:
indeed - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.indeed.com/claude/mcp
- Auth docs: https://docs.indeed.com/mcp
Setup steps:
- Connect to the Indeed MCP server at mcp.indeed.com/claude/mcp.
- Sign in with your Indeed account when prompted.
- Authorize access to job search and company data.
Notes:
- Live testing showed Indeed should stay on manual/preregistered OAuth instead of open managed DCR.
Scholar Gateway
- Provider key:
scholar-gateway - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://connector.scholargateway.ai/mcp
- Auth docs: https://docs.scholargateway.ai/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Scholar Gateway account when prompted.
- Authorize NeoTask to access your Scholar Gateway data.
- The connection is completed automatically.
Microsoft Learn
- Provider key:
microsoft-learn - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://learn.microsoft.com/api/mcp
Setup steps:
- No authentication is required for this integration.
PitchBook Premium
- Provider key:
pitchbook-premium - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://premium.mcp.pitchbook.com/mcp
- Auth docs: https://pitchbook.com/platform-data/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your PitchBook Premium account when prompted.
- Authorize NeoTask to access your PitchBook Premium data.
- The connection is completed automatically.
Crypto.com
- Provider key:
crypto-com - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://mcp.crypto.com/market-data/mcp
- Auth docs: https://exchange-docs.crypto.com/exchange/v1/rest-ws/index.html
- Required fields:
apiKeyrequired,secretKey
Setup steps:
- Log into Crypto.com Exchange at crypto.com/exchange.
- Click your profile icon (upper-right), select "Manage Account", then click "API Management".
- Click "Create a new API key", enter a description, and enter your 2FA code.
- Your Public Key (API Key) and Secret Key are displayed. Copy both immediately, the Secret is shown only once.
- Optionally configure IP restrictions and permissions (default: read-only). Trading/withdrawal require IP whitelisting.
- 2FA must be enabled on your account before creating API keys.
- Enter the required credentials: apiKey (required), secretKey.
Daloopa
- Provider key:
daloopa - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.daloopa.com/server/mcp
- Auth docs: https://docs.daloopa.com/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Daloopa account when prompted.
- Authorize NeoTask to access your Daloopa data.
- The connection is completed automatically.
Chronograph
- Provider key:
chronograph - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://ai.chronograph.pe/mcp
- Auth docs: https://chronograph.pe/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Chronograph account when prompted.
- Authorize NeoTask to access your Chronograph data.
- The connection is completed automatically.
LSEG
- Provider key:
lseg - Auth provider:
credentials - Reviewed classification:
manual_credentials - Service URL: https://api.analytics.lseg.com/lfa/mcp/server-cl
- Auth docs: https://developers.lseg.com/
- Required fields:
apiKeyrequired
Setup steps:
- Log in at workspace.refinitiv.com with your RDP (Refinitiv Data Platform) human user ID.
- In the search box (far upper-left), type "appkey" and select "App Key Generator" from the results.
- Enter an App Display Name, check the first three API checkboxes (including "EDP API"/"RDP API"), and click "Register New App".
- Accept the Terms of Use popup. Your App Key appears in the table under the "API Key" column, copy it.
- Enter your App Key, RDP username (machine ID), and RDP password to connect.
- Requires an active LSEG/Refinitiv subscription.
LunarCrush
- Provider key:
lunarcrush - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://lunarcrush.ai/mcp
- Auth docs: https://lunarcrush.com/developers/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your LunarCrush account when prompted.
- Authorize NeoTask to access your LunarCrush data.
- The connection is completed automatically.
MT Newswires
- Provider key:
mt-newswires - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://vast-mcp.blueskyapi.com/mcp
- Auth docs: https://www.mtnewswires.com/api
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your MT Newswires account when prompted.
- Authorize NeoTask to access your MT Newswires data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Moody's
- Provider key:
moody-s - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.moodys.com/genai-ready-data/m1/mcp
- Auth docs: https://www.moodys.com/web/en/us/genai/model-context-protocol.html
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Moody's account when prompted.
- Authorize NeoTask to access your Moody's data.
- The connection is completed automatically.
Vibe Prospecting
- Provider key:
vibe-prospecting - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://vibeprospecting.explorium.ai/mcp
- Auth docs: https://vibeprospecting.explorium.ai/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Vibe Prospecting account when prompted.
- Authorize NeoTask to access your Vibe Prospecting data.
- The connection is completed automatically.
Crossbeam
- Provider key:
crossbeam - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.crossbeam.com
- Auth docs: https://help.crossbeam.com/en/articles/12601327-crossbeam-mcp-server-limited-availability
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Crossbeam account when prompted.
- Authorize NeoTask to access your Crossbeam data.
- The connection is completed automatically.
Similarweb
- Provider key:
similarweb - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.similarweb.com
- Auth docs: https://developers.similarweb.com/docs/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Similarweb account when prompted.
- Authorize NeoTask to access your Similarweb data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Harmonic
- Provider key:
harmonic - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.api.harmonic.ai
- Auth docs: https://docs.harmonic.ai/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Harmonic account when prompted.
- Authorize NeoTask to access your Harmonic data.
- The connection is completed automatically.
Sprouts
- Provider key:
sprouts - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://sprouts-mcp-server.kartikay-dhar.workers.dev
- Auth docs: https://sprouts.ai/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Sprouts account when prompted.
- Authorize NeoTask to access your Sprouts data.
- The connection is completed automatically.
Supermetrics
- Provider key:
supermetrics - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.supermetrics.com/mcp
- Auth docs: https://supermetrics.com/docs/product-api-authentication
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Supermetrics account when prompted.
- Authorize NeoTask to access your Supermetrics data.
- The connection is completed automatically.
Windsor.ai
- Provider key:
windsor-ai - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.windsor.ai
- Auth docs: https://windsor.ai/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Windsor.ai account when prompted.
- Authorize NeoTask to access your Windsor.ai data.
- The connection is completed automatically.
Circleback
- Provider key:
circleback - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://app.circleback.ai/api/mcp
- Auth docs: https://circleback.ai/docs
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Circleback account when prompted.
- Authorize NeoTask to access your Circleback data.
- The connection is completed automatically.
Clockwise
- Provider key:
clockwise - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.getclockwise.com/mcp
- Auth docs: https://support.getclockwise.com/article/238-connecting-to-clockwise-mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Clockwise account when prompted.
- Authorize NeoTask to access your Clockwise data.
- The connection is completed automatically.
Fellow.ai
- Provider key:
fellow-ai - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://fellow.app/mcp
- Auth docs: https://help.fellow.ai/en/articles/12622641-fellow-s-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Fellow.ai account when prompted.
- Authorize NeoTask to access your Fellow.ai data.
- The connection is completed automatically.
Jam
- Provider key:
jam - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.jam.dev/mcp
- Auth docs: https://jam.dev/docs/debug-a-jam/mcp
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Jam account when prompted.
- Authorize NeoTask to access your Jam data.
- The connection is completed automatically.
Guru
- Provider key:
guru - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.api.getguru.com/mcp
- Auth docs: https://help.getguru.com/docs/connecting-gurus-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Guru account when prompted.
- Authorize NeoTask to access your Guru data.
- The connection is completed automatically.
Coupler.io
- Provider key:
coupler-io - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.coupler.io/mcp/
- Auth docs: https://blog.coupler.io/how-to-use-coupler-mcp-server/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Coupler.io account when prompted.
- Authorize NeoTask to access your connected data sources.
Notes:
- Live testing showed Coupler should not be treated as open managed DCR yet.
Egnyte
- Provider key:
egnyte - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp-server.egnyte.com/mcp
- Auth docs: https://developers.egnyte.com/docs/Remote_MCP_Server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Egnyte account when prompted.
- Authorize NeoTask to access your Egnyte data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
CData Connect AI
- Provider key:
cdata-connect-ai - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.cloud.cdata.com/mcp
- Auth docs: https://cloud.cdata.com/docs/MCP.html
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your CData Connect AI account when prompted.
- Authorize NeoTask to access your CData Connect AI data.
- The connection is completed automatically.
Lumin
- Provider key:
lumin - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.luminpdf.com/mcp
- Auth docs: https://github.com/luminpdf/lumin-mcp-server
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Lumin account when prompted.
- Authorize NeoTask to access your Lumin data.
- The connection is completed automatically.
Kiwi.com
- Provider key:
kiwi-com - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.kiwi.com
- Auth docs: https://www.kiwi.com/partners/
- Required fields:
apiKeyrequired
Setup steps:
- Get your API key from the Kiwi.com partner or affiliate portal.
- Paste that key into NeoTask to connect the Kiwi.com MCP endpoint.
lastminute.com
- Provider key:
lastminute-com - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://mcp.lastminute.com/mcp
- Auth docs: https://www.lastminute.com/partners
- Required fields:
apiKeyrequired
Setup steps:
- Generate an API key in the lastminute.com developer portal.
- Paste that API key into NeoTask.
BioRender
- Provider key:
biorender - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.services.biorender.com/mcp
- Auth docs: https://help.biorender.com/hc/en-gb/articles/30870978672157-How-to-use-the-BioRender-MCP-connector
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your BioRender account when prompted.
- Authorize NeoTask to access your BioRender data.
- The connection is completed automatically.
Open Targets
- Provider key:
open-targets - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://mcp.platform.opentargets.org/mcp
Setup steps:
- No authentication is required for this integration.
Synapse.org
- Provider key:
synapse-org - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.synapse.org/mcp
- Auth docs: https://help.synapse.org/docs/Using-Synapse-as-an-OAuth-Server.2048327904.html
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Synapse.org account when prompted.
- Authorize NeoTask to access your Synapse.org data.
- The connection is completed automatically.
Consensus
- Provider key:
consensus - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.consensus.app/mcp
- Auth docs: https://consensus.app/home/mcp/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Consensus account when prompted.
- Authorize NeoTask to access your Consensus data.
- The connection is completed automatically.
Notes:
- Live metadata proof: authorization server publishes registration_endpoint https://consensus.app/oauth/register/. Consensus supports dynamic client registration with PKCE/public-client OAuth.
Udemy Business
- Provider key:
udemy-business - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://api.udemy.com/mcp
- Auth docs: https://business-support.udemy.com/hc/en-us/articles/34213384429335-How-to-Integrate-the-Udemy-Business-MCP-Server-With-Your-AI-Tool
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Udemy Business account when prompted.
- Authorize NeoTask to access your Udemy Business data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Dice
- Provider key:
dice - Auth provider:
oauth - Reviewed classification:
manual_oauth - Service URL: https://mcp.dice.com/mcp
- Auth docs: https://www.dice.com/recruiting/recruiter-products/api
- Required fields:
apiKeyrequired
Setup steps:
- Get your API key from the Dice developer or recruiter portal.
- Paste that key into NeoTask to connect the Dice MCP endpoint.
Stytch
- Provider key:
stytch - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.stytch.dev/mcp
- Auth docs: https://stytch.com/docs/guides/connected-apps/mcp-server-overview
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Stytch account when prompted.
- Authorize NeoTask to access your Stytch data.
- The connection is completed automatically.
Blockscout
- Provider key:
blockscout - Auth provider:
none - Reviewed classification:
no_auth - Service URL: https://mcp.blockscout.com/mcp
Setup steps:
- No authentication is required for this integration.
DevRev
- Provider key:
devrev - Auth provider:
api_key - Reviewed classification:
api_key - Service URL: https://api.devrev.ai/mcp/v1
- Auth docs: https://developer.devrev.ai/public/about/authentication
- Required fields:
apiKeyrequired
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your DevRev account when prompted.
- Authorize NeoTask to access your knowledge graph.
- Enter the required API key: apiKey (required).
Magic Patterns
- Provider key:
magic-patterns - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.magicpatterns.com/mcp
- Auth docs: https://www.magicpatterns.com/docs/documentation/features/mcp-server/overview
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Magic Patterns account when prompted.
- Authorize NeoTask to access your Magic Patterns data.
- The connection is completed automatically.
Notes:
- DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Ticket Tailor
- Provider key:
ticket-tailor - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.tickettailor.ai/mcp
- Auth docs: https://developers.tickettailor.com/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Ticket Tailor account when prompted.
- Authorize NeoTask to access your Ticket Tailor data.
- The connection is completed automatically.
Yardi Virtuoso
- Provider key:
yardi-virtuoso - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.virtuoso.ai/mcp
- Auth docs: https://www.yardi.com/virtuoso/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Yardi Virtuoso account when prompted.
- Authorize NeoTask to access your Yardi Virtuoso data.
- The connection is completed automatically.
Candid
- Provider key:
candid - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.candid.org/mcp
- Auth docs: https://support.claude.com/en/articles/12923235-using-the-candid-connector-in-claude
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Candid account when prompted.
- Authorize NeoTask to access your Candid data.
- The connection is completed automatically.
NetSuite
- Provider key:
netsuite - Auth provider:
credentials - Reviewed classification:
manual_credentials - Auth docs: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_157771733782.html
- Required fields:
accountIdrequired,consumerKeyrequired,consumerSecretrequired,tokenIdrequired,tokenSecretrequired
Setup steps:
- Enter your NetSuite account ID and token-based authentication credentials.
- Use the correct NetSuite account-specific host for your workspace.
- NeoTask will connect with token-based credentials instead of standard OAuth.
Notes:
- User must replace {account_id} with their NetSuite account ID. Uses token-based authentication credentials, not standard OAuth.
Pendo
- Provider key:
pendo - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://app.pendo.io/mcp/v0/shttp
- Auth docs: https://support.pendo.io/hc/en-us/articles/41102236924955
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Pendo account when prompted.
- Authorize NeoTask to access your Pendo data.
- The connection is completed automatically.
Notes:
- Regional variants may apply. Check Pendo login URL for region. Pendo publishes live OAuth metadata and DCR from the MCP endpoint. Regional variants may apply.
Pigment
- Provider key:
pigment - Auth provider:
oauth - Reviewed classification:
custom_url_first - Auth docs: https://kb.pigment.com/docs/mcp-server
Setup steps:
- Copy the exact Pigment MCP URL from your Pigment workspace settings.
- Paste that MCP URL into NeoTask first.
- Then continue the Pigment OAuth flow for that workspace MCP endpoint.
Notes:
- User must configure MCP URL from their Pigment workspace settings. Pigment requires a workspace-provided MCP URL; do not assume the generic mcp.pigment.com host is sufficient.
Workato
- Provider key:
workato - Auth provider:
oauth - Reviewed classification:
custom_url_first - Auth docs: https://docs.workato.com/en/mcp/remote-mcp-servers.html
Setup steps:
- Copy the exact Workato MCP URL from Workato AI Hub > MCP Servers.
- Paste that MCP URL into NeoTask first.
- Then continue the Workato OAuth flow for that server URL.
Notes:
- User must copy MCP URL from Workato AI Hub > MCP Servers. Workato requires a user-copied MCP URL from AI Hub; do not treat the generic workato.com homepage as the runtime endpoint.
Port
- Provider key:
port - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.getport.io/v1/mcp
- Auth docs: https://docs.port.io/ai-interfaces/port-mcp-server/overview-and-installation/
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your Port account when prompted.
- Authorize NeoTask to access your Port data.
- The connection is completed automatically.
Notes:
- US region: https://mcp.us.port.io/v1 DCR re-probe 2026-05-29: live registration issued a client_id; promoted to managed_dcr.
Benchling
- Provider key:
benchling - Auth provider:
oauth - Reviewed classification:
custom_url_first - Auth docs: https://help.benchling.com/hc/en-us/articles/40342713479437
Setup steps:
- Paste your exact Benchling MCP URL first.
- Replace {tenant} with your Benchling tenant name in the hosted MCP URL.
- After the URL is saved, continue the Benchling OAuth flow.
Notes:
- User must replace {tenant} with their Benchling tenant name. Benchling requires the exact tenant-scoped MCP URL: https://{tenant}.mcp.benchling.com/mcp.
Visier
- Provider key:
visier - Auth provider:
oauth - Reviewed classification:
custom_url_first - Auth docs: https://docs.visier.com/developer/agents/mcp/mcp-server-set-up.htm
Setup steps:
- Paste your exact Visier MCP URL first.
- Replace {vanity_name} with your Visier vanity tenant name.
- Then continue the Visier OAuth flow for that tenant-scoped MCP URL.
Notes:
- User must replace {vanity_name} with their Visier tenant name. Visier requires a vanity-name-specific MCP URL: https://{vanity_name}.app.visier.com/visier-query-mcp.
Starburst
- Provider key:
starburst - Auth provider:
oauth - Reviewed classification:
custom_url_first - Auth docs: https://docs.starburst.io/latest/starburst-ai/mcp-server.html
Setup steps:
- Paste your exact Starburst MCP URL first.
- Replace {coordinator_host} with your Starburst coordinator or Galaxy MCP host.
- Then continue the Starburst OAuth flow for that host.
Notes:
- User must replace {coordinator_host} with their Starburst cluster host. Starburst requires a host-specific MCP URL such as https://{coordinator_host}/mcp or the Galaxy-hosted MCP endpoint.
LILT
- Provider key:
lilt - Auth provider:
oauth - Reviewed classification:
managed_dcr - Service URL: https://mcp.lilt.com/mcp
- Auth docs: https://claude.com/connectors/lilt
Setup steps:
- Click Connect to begin the OAuth flow.
- Sign in to your LILT account when prompted.
- Authorize NeoTask to access your LILT data.
- The connection is completed automatically.
Browser Automation
- Provider key:
browser-automation - Auth provider:
none - Reviewed classification:
no_auth
Setup steps:
- No authentication is required for this integration.