AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

MCP tools services for AI agents

Connect a service through a documented MCP interface.

Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.

163 available services15 capability categoriesOpen discovery · no login

Choosing mcp tools for your task

Inspect the tools exposed by the server and the account they operate on. Verify whether the integration performs actions or merely searches documentation.

Before you proceed: Review individual tool inputs and scope before allowing consequential actions.

AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.

FIND THE MISSING CAPABILITY

Services with MCP tools

97 services · Catalog updated 2026-11-10 · See each listing’s review date

Recall.ai ↗

Capture meeting media and investigate recording workflows through APIs.

Before you connect

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.

Our integration playbook
Track admission, capture and artifact readiness as separate states

Inspect setup, billing & access →

Svix ↗

Deliver webhook events and investigate failed deliveries with agent tools.

Before you connect

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.

Our integration playbook
Make the receiver safe to replay before recovering missed events

Inspect setup, billing & access →

WorkOS ↗

Manage identity resources and authorize access to your MCP services.

Before you connect

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.

Our integration playbook
Keep management authorization separate from end-user access

Inspect setup, billing & access →

Cartesia ↗

Generate and transcribe speech through hosted voice models and agent tools.

Before you connect

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.

Our integration playbook
Match the audio contract before connecting speech to a live workflow

Inspect setup, billing & access →

Novu Cloud ↗

Operate notification workflows and subscriber preferences through agent tools.

Before you connect

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.

Our integration playbook
Resolve the subscriber, environment and delivery provider before triggering

Inspect setup, billing & access →

Courier ↗

Manage notification templates, journeys and delivery through operational agent tools.

Before you connect

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.

Our integration playbook
Resolve environment and provider capacity before releasing a notification

Inspect setup, billing & access →

Scrapfly ↗

Fetch live web content through managed scraping, browser and extraction tools.

Before you connect

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.

Our integration playbook
Validate page identity and extraction completeness before scaling retrieval

Inspect setup, billing & access →

Notte ↗

Give agents hosted browser sessions with reusable authenticated state.

Before you connect

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.

Our integration playbook
Check authentication, task completion and browser shutdown separately

Inspect setup, billing & access →

OpenWeather for agents ↗

Fetch weather observations and forecasts through an agent-oriented API or MCP server.

Before you connect

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.

Our integration playbook
Check the weather timestamp and the correct credit balance

Inspect setup, billing & access →

Financial Datasets ↗

Retrieve market prices, filings and structured company financial data through API or MCP.

Before you connect

Create and fund an account for API access, or authorize a funded USDC wallet on Base for supported x402 requests. Check the intended use against the data licence before selecting a route.

Our integration playbook
Keep each financial value attached to its period and source

Inspect setup, billing & access →

Merge Agent Handler ↗

Connect agent tool calls to authorized third-party accounts with managed connectors.

Before you connect

Set up an organization, Registered User and scoped Tool Pack, then authorize required third-party connectors. A documented agent signup route can create initial credentials, but it does not grant private account access.

Our integration playbook
Bind each tool call to the intended user and permission scope

Inspect setup, billing & access →

Checkly ↗

Run hosted application checks and inspect results through MCP, API or CLI.

Before you connect

Create an account, select monitoring locations and a plan, and configure checks and alerts. Authorize an approved OAuth client or issue a key with the required account role.

Our integration playbook
Distinguish a monitor’s last result from current application health

Inspect setup, billing & access →

Airweave ↗

Search synchronized context from authorized apps and databases through API, CLI or MCP.

Before you connect

Create an account and collection, authorize the required source connections and wait for an initial sync. Choose a plan and decide which data the agent may retrieve.

Our integration playbook
Check source freshness before treating retrieved context as current

Inspect setup, billing & access →

Tinybird ↗

Query managed analytics data and published endpoints through MCP or APIs.

Before you connect

Create a Workspace in the intended region, ingest an authorized dataset and prepare query endpoints. Issue a resource-scoped token or appropriately restricted JWT and set a usage budget.

Our integration playbook
Give the agent a scoped analytical question and a known data window

Inspect setup, billing & access →

ScraperAPI ↗

Retrieve web content and supported structured datasets using hosted collection infrastructure.

Before you connect

Create an account, obtain its API key and select a credit allowance and concurrency level. Define the permitted sources, retrieval volume and required output format.

Our integration playbook
Budget the actual retrieval options and validate the extracted fields

Inspect setup, billing & access →

Tenderly ↗

Simulate transactions and inspect contract execution in managed blockchain environments.

Before you connect

Create a Tenderly account and project, arrange a paid plan and have MCP access enabled through sales. Select the intended project, network and Virtual Environment before running a workflow.

Our integration playbook
Keep simulated state separate from permission to move real assets

Inspect setup, billing & access →

Alchemy ↗

Query blockchain nodes and indexed data through MCP, API or CLI.

Before you connect

Create an account and app for API or MCP access, or authorize an EVM wallet and USDC budget for the separate x402 gateway. Select the intended network and scope any wallet permissions separately.

Our integration playbook
Bind blockchain observations to a chain, block and payment route

Inspect setup, billing & access →

Reducto ↗

Turn complex documents into structured fields and layout-aware content.

Before you connect

Create a Reducto account and authorize a key or local login. Select the processing region, retention terms and spending limits before uploading sensitive documents.

Our integration playbook
Validate document evidence before accepting structured fields

Inspect setup, billing & access →

Supadata ↗

Retrieve public video transcripts and metadata through API, SDK or MCP.

Before you connect

Create an account, connect hosted MCP with OAuth or configure an API key, and set a credit budget. Decide whether generated transcription and automatic credit recharge are allowed.

Our integration playbook
Set a transcription mode and cost ceiling before fetching video

Inspect setup, billing & access →

Dappier ↗

Query publisher content and current information with documented agent payment options.

Before you connect

Choose the required publisher model and access channel. Configure an API key for the regular API, or authorize the storefront’s identity and payment route with a bounded budget.

Our integration playbook
Select the content contract before authorizing paid retrieval

Inspect setup, billing & access →

Tavus CVI ↗

Create and operate conversational video agents through API, MCP and CLI.

Before you connect

Create a Tavus developer account, configure credentials and billing, and choose a face, voice and permitted application tools. Set session duration, concurrency and spending limits.

Our integration playbook
Bound the session lifecycle before connecting application actions

Inspect setup, billing & access →

OpenAlex ↗

Find scholarly works, resolve citations and inspect research connections through API or MCP.

Before you connect

Connect MCP and approve OpenAlex sign-in, or obtain a free API key. An agent can request a key for its owner, but the owner must click the emailed activation link before that key works.

Our integration playbook
Keep a reproducible search trail before summarizing research

Inspect setup, billing & access →

Enigma ↗

Look up U.S. businesses, legal entities and card-revenue signals through API or MCP.

Before you connect

Create an Enigma account, choose a plan covering the required interface and obtain an API key. Current pricing places API access in Pro and MCP access in Max; confirm account entitlements and credit limits.

Our integration playbook
Resolve the business entity before buying enrichment

Inspect setup, billing & access →

Docusign MCP ↗

Prepare, send and track agreement workflows through authenticated API and MCP tools.

Before you connect

Choose a Docusign account and eligible plan, enable MCP access with the administrator, and configure OAuth. Custom agents need an approved production Integration Key and their own approval step for agreement actions.

Our integration playbook
Validate recipients and document versions before sending an agreement

Inspect setup, billing & access →

Doppler ↗

Supply scoped credentials to agent workloads through managed secrets, CLI and MCP.

Before you connect

Create a project and a config containing only the required credentials. Have an authorized administrator issue a suitably scoped token, choose its expiry and configure the agent runtime. The MCP server requires Node.js 20 or later.

Our integration playbook
Match credential scope to the workload before launching it

Inspect setup, billing & access →

Supermemory ↗

Retain project context, retrieve source documents and share memory across authorized agent sessions.

Before you connect

Create an account, decide which data may be retained and choose a space or namespace. Approve MCP access to the intended spaces, or create an API key in the developer console for application integration.

Our integration playbook
Keep memory attributable and test corrections across sessions

Inspect setup, billing & access →

Weaviate Cloud ↗

Store searchable data in a managed vector database and query it through SDKs or MCP.

Before you connect

Create a cloud account and cluster, import an authorized collection and configure its vectorizer. Enable Agents for the organization if using Query Agent, and issue a key with access to the intended collections.

Our integration playbook
Validate retrieval and access boundaries before asking for summaries

Inspect setup, billing & access →

You.com APIs ↗

Search current web sources through API or MCP, with free and documented machine-payment routes.

Before you connect

For limited search, configure the free MCP profile without an account. For broader access, create an account and API key or authorize OAuth. For machine payments, use a compatible funded wallet and an approved spending budget.

Our integration playbook
Choose an access route and bound the retrieval cost before researching

Inspect setup, billing & access →

Hookdeck Event Gateway ↗

Queue, inspect and retry incoming webhooks that trigger agent workflows.

Before you connect

Create an account and project, connect a source to a destination, and configure incoming webhook signature checks and destination authentication. Select throughput and retention appropriate to the workflow.

Our integration playbook
Make event retries safe before connecting them to agent actions

Inspect setup, billing & access →

BrowserStack MCP ↗

Run agent-directed tests on hosted real mobile devices and desktop browsers.

Before you connect

Create a BrowserStack account and obtain the product licence for the workflow: App Automate for mobile device control or Automate for desktop browser control. Provide an authorized app build or test URL and connect the MCP client.

Our integration playbook
Pin the build and device before judging a test result

Inspect setup, billing & access →

Permit MCP Gateway ↗

Route MCP tool calls through managed identity, authorization and audit controls.

Before you connect

Create a gateway organization and host, connect the intended MCP servers, configure user and agent identities and assign tool access. Point clients at the host-specific gateway URL and complete the required sign-in.

Our integration playbook
Check the actual tool behavior behind each access tier

Inspect setup, billing & access →

Sauce MCP ↗

Inspect tests and operate dedicated mobile devices through hosted MCP tools.

Before you connect

Create a Sauce Labs account and choose the required product entitlements. Mobile control requires private dedicated devices and Real Device Access API concurrency; ordinary account access is sufficient only for tools without those dependencies.

Our integration playbook
Confirm the device entitlement before scheduling a reproduction

Inspect setup, billing & access →

BuiltWith ↗

Retrieve website technology profiles and historical detections through API or MCP.

Before you connect

Choose account credits with an API key or authorize a funded Base USDC wallet for x402. Saved-card top-ups require separate manual enablement, spending limits and an Agent Billing Key.

Our integration playbook
Check observation dates before treating a technology as currently installed

Inspect setup, billing & access →

Censys Platform ↗

Look up observed internet assets, certificates and exposed services using API or MCP.

Before you connect

Create a Platform account and select the appropriate plan. Organization access requires the API Access role. Choose the organization whose entitlements and credits should be used.

Our integration playbook
Attach observation time and identity confidence to each inventory finding

Inspect setup, billing & access →

Explore related capabilities

Browse all service tags →

NO BROWSER REQUIRED

Discover. Inspect.
Connect.

Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.

GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
GET /api/agent-services?payment=mpp-wallet
GET /api/agent-services?payment=no-payment
GET /api/agent-services?id=e2b

Full catalog: /data/agent-services.json

Manifest: /.well-known/agent-services.json

Choose your next service with the facts in hand.

Find the tools you need

You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.

Check what you need from your owner

Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.

Confirm your payment path

Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.