Apify MCP Server
by Apify
Apify MCP server: lets AI agents run Apify Actors to scrape and extract web data, with docs and storage tools.
- Does
- 5 things
- Install
- 5 steps
- Works with
- 3 hosts
Guide
MCP stands for Model Context Protocol. An MCP server is a small program that exposes a service to an AI app. The AI app is the client, also called the host; examples in our profiles are Claude Code, Cursor, Windsurf and Codex. The client connects to the server and the server tells it what it can do, so one server such as the GitHub MCP Server can work in many clients.
A server offers tools (actions the model can call, such as creating an issue or running a query), and the reference everything server also exercises prompts and resources (data the client can read). Servers connect in two ways. Local servers run on your machine as a command, for example npx for the filesystem server or uvx for git and fetch. Remote servers sit behind a URL, such as Context7, Sentry and Vercel.
Security matters because a server acts with the access you give it. Profiles cite concrete advice: grant minimum token scopes (GitHub), use a Restricted API Key (Stripe), create read-only database users (Redis) and review what the model asks to do (Neon). The fetch server's README warns it can reach local and internal IP addresses, and the filesystem server's write_file overwrites existing files. We profiled 49 MCP servers; 47 are official.
| Term | What it is | Example |
|---|---|---|
| MCP | The protocol: JSON-RPC 2.0 messages plus two transports | The specification at modelcontextprotocol.io |
| MCP host | The AI app you work in | Claude Code, Claude Desktop, VS Code, Cursor |
| MCP client | One connection the host opens per server | VS Code opens a separate client for Sentry and for the filesystem server |
| MCP server | The program that provides tools, data and prompts | GitHub, Sentry, filesystem |
Not always a networked one. A local server is a process the AI app launches on your machine and talks to over standard input/output (stdio); it usually serves one client and runs with your user permissions. A remote server runs on the vendor's platform behind a URL over Streamable HTTP, serves many clients and authenticates with bearer tokens or API keys; the protocol recommends OAuth.
An API is one service's own interface, and every AI app has to integrate it separately. An MCP server wraps that capability in a standard format the model can discover at runtime (tools/list) and call (tools/call), so one server works in every MCP host. Many MCP servers call the vendor's API underneath.
by Apify
Apify MCP server: lets AI agents run Apify Actors to scrape and extract web data, with docs and storage tools.
by Atlassian
Atlassian's official remote MCP server connecting Jira, Confluence and more to AI assistants with OAuth.
by AWS Labs (Amazon Web Services)
MCP server that lets AI assistants run AWS CLI commands across all AWS services with validation and security controls.
by AWS Labs (Amazon Web Services)
MCP server that fetches, searches and recommends current AWS documentation pages as markdown for AI assistants.
by AWS Labs (Amazon Web Services)
Open-source suite of MCP servers from AWS Labs for AWS docs, APIs, IaC, pricing, data and more, run locally over stdio.
by Microsoft
Microsoft's MCP server that brings Azure context and operations into AI agents, installable via npm, .NET, PyPI or Docker.
by Brave
Brave's official MCP server for web, local, image, video and news search plus AI summarization.
by Chrome DevTools (Google)
Lets your coding agent control and inspect a live Chrome browser: performance traces, network, console, screenshots, automation.
MCP means Model Context Protocol, the standard that lets AI apps connect to external tools and data through servers.
A stdio server runs locally as a command like npx or uvx. A remote server runs elsewhere and you connect to its URL, usually with OAuth or a token.
Not usually. You add a config entry or run an add command and authenticate. To build your own, Anthropic's mcp-builder-skill and mcp-server-dev plugin guide you.
They are as safe as the access you grant. Use minimum permissions, read-only credentials where possible, and read each server's README security notes.
An API is one service's own interface that each AI app must integrate separately. An MCP server wraps that capability in a standard format the model discovers at runtime and calls, so one server works in every MCP client; many MCP servers call the vendor API underneath.
Not always a networked one. A local MCP server is a process the AI app launches on your machine over stdio; a remote server runs on the vendor's platform behind a URL, often with OAuth.
Yes. The Model Context Protocol site lists Claude, ChatGPT, VS Code and Cursor among the clients that support MCP servers.
compare>