MCP tools services for AI agents

Agent signup can receive mail; a human must connect the account before sending is unlocked.

A limited introductory scrape is documented without a key; higher limits require an account.

Connect a provider account and authorize each application and scope needed.

Authenticate with email OTP; the owner funds the wallet and sets spending limits.

Authorize an Apify account with OAuth or an API token; optional agent payment routes require approved funds.

Configure Nango, have account owners authorize their integrations, and create a session restricted to the intended tenant and tools.

Create an organization and project, authorize CLI access, deploy task code and configure the required secrets.

Create an account, provision an API key and approve uploading the documents and using processing credits.

Create a Connect project and OAuth client; have each user connect the intended accounts and approve production billing.

Create a Bright Data account, configure its API token and approve the public-data scope and usage budget.

Create a Browserless account, authorize OAuth or configure a token, and choose a plan with suitable session limits.

Authorize a Neon account and project, choose database permissions and billing, and review MCP-requested actions before execution.

Create a Kernel account and API key; authorize the target websites, account access and resource budget.

Create a Unipile account, obtain a DSN and token, and have each account owner authorize the intended connection and actions.

Create an Arcade account, choose the tools for your workflow and obtain the account owner’s OAuth authorization.

Connect an existing Bland account or use agent onboarding with owner phone verification. Approve the calling scope and any payment or subscription.

Create a Coresignal account with credits; authorize the team through the MCP browser sign-in or configure an API credential.

Agent Access documents a challenge-based trial key without a dashboard account. Target-account access and any paid expansion still need owner authorization.

Create a Tigris account, authorize the intended organization and buckets, and choose access and retention settings.

Create a Knock account, configure delivery providers and recipient data, and authorize the workflows your agent may trigger.

Authorize an existing organization, or use the agent-created organization flow for a temporary environment. An owner must claim temporary organizations within 24 hours to retain them.

Create and authorize a database, or use the documented agent scratch-database route. Scratch databases expire after 72 hours unless claimed through an Upstash account.

Create a Sentry organization and project, instrument the application, and authorize access to the relevant project.

Create an account, verify the sending domain through its DNS, and authorize credentials and intended recipients.

Choose a Cloudinary product environment and authorize access. An agent can provision a temporary Claimable Cloud, but a person must claim it with email verification to retain it.

Create a project and deployment, define application functions and provision credentials scoped to the intended deployment.

Set up the Stripe account and sandbox, authorize the agent’s permissions, and complete any required business activation before live payment operations.

Create a project and authorize the intended organization. Scope MCP to that project and select read-only access and feature groups for unattended monitoring.

Create a ScrapingBee account, supply its API key and choose the allowed research targets and credit budget.

Create or select an ElevenLabs workspace, authorize the connection and choose permitted voices, content and a usage budget.

Select a fal account or workspace, authorize the connection, fund the required credits and set a permitted model and spending scope.

Create an Oxylabs account, enable Agent Browser credentials and set permitted targets, session concurrency and a traffic budget.

Create or select a PostHog project, instrument the events needed for your question, and authorize the agent connection to the appropriate account.

Select a Vercel account, team and project, connect a supported MCP client and authorize the intended team access. Define which production changes need review.

Select a supported US or EU workspace and authorize the required read and write scopes. Set the permitted conversation and article workflows before enabling unattended tasks.

Create a Deepgram project, issue a scoped API key or sign in through the CLI, and choose an audio-processing budget and permitted input files.

Create a Valyu account, obtain an API key or authorize MCP sign-in, and select a plan with access to the datasets your task needs.

Create a Nylas application and connect an authorized account or provision an Agent Account. Grant only the account resources and actions needed for the workflow.

Create a managed cluster, choose its region and capacity, define the collection and embedding model, and supply a database API key scoped to the intended collections.

Create an Inngest account, integrate the SDK and deploy or connect the application code that executes your functions. Scope agent access to the intended environment.

Create a Replicate account and API token, configure billing when required, and choose a model with suitable input requirements, usage rights and a task budget.

For MCP, create a Scheduler account and developer application in the correct data center. Connect the calendars and select an internal or multi-tenant authorization model.

Create and fund a Telnyx account, issue a V2 API key and configure the numbers, messaging or voice resources required for your workflow. Complete applicable provider onboarding before production use.

Configure an MCP-compatible client with the HTTPS endpoint https://mcp.algolia.com/1/docsearch/mcp. No Algolia account, application ID or API key is required.

Create a Railway account, choose a workspace and billing plan, and authorize the projects the agent may access. Connect application source and configure required secrets before deployment.

Create a Render account and workspace, connect the intended source repository, choose resource plans and authorize your agent. Select the workspace explicitly before operating resources.

Create a regional Recall.ai account and REST API key. Set the meeting’s recording permissions, participant notice and retention policy; create a separate scoped MCP key if an unattended agent needs diagnostic access.

Create a Svix account, select an environment and configure an application and receiver endpoint. Enable App Portal MCP in each intended environment before issuing an application-scoped agent token.

Create a Cloudflare account, choose the services and billing plans required by the workload, and authorize only the accounts and resources the agent should operate.

Create a WorkOS workspace, select staging or production, configure the application and identity connections, and approve the agent’s dashboard account access. Production requires billing information.

Create a SerpApi account, obtain an API key and select a search plan. Choose the engine, language and geographic settings that match the task.

Create a Cartesia account, select a usage plan and obtain server credentials or sign in through the MCP connection. Choose the voice, model and audio format required by the destination.

Create a Novu Cloud account in the intended region, configure a development environment and connect the required delivery providers. Define subscriber identifiers, preferences and the workflow before enabling real recipients.

Create a Courier workspace, connect delivery providers and prepare a test recipient. Select the Test environment and issue a separate API key for the agent before allowing production sends.

Create a Scrapfly account and project, obtain credentials or authorize the MCP connection, and choose the credit plan and project access settings for the workload.

Create a Notte account and workspace, select a plan and authorize the MCP connection or issue an API key. Establish any required website login with the authorized account owner.

Create an account, obtain an API key and configure credits. Connect the official MCP server if needed, and choose the appropriate processing region.

Create an IPinfo account, choose the data tier and configure overage billing. Authorize the MCP client or issue a server-side API token.

Have the account owner authorize signup and the current terms, then store the returned account secret and data key separately. A person completes paid credit top-ups on the provider’s payment page.

Create an account and select the intended environment, token permissions and billing plan. Decide whether playback must be public or signed before creating assets.