Skip to main content
use-apify.com

Model Context Protocol: guides & tutorials

Model Context Protocol links hosts to scrapers, DBs, and internal APIs safely. Architecture and Apify-backed MCP servers developers ship to production.

3 articles

View all tags

The Model Context Protocol links AI hosts to scrapers, databases, and internal APIs through one safe, standard interface. These guides cover MCP architecture and building servers that expose Apify actors as callable tools.

MCP matters because it standardizes how assistants reach external systems, with permissions and clear contracts. Below you will find design patterns and Apify-backed MCP server examples developers ship to production.

Related topics

MCP16 min read

The Complete MCP Server Handbook for Developers (April 2026 Edition)

· 16 min read
Yassine El Haddad
Software Developer & Automation Specialist

The Model Context Protocol (MCP) is the USB-C for AI: a single open standard that connects AI applications to tools, data sources, and workflows. Originated by Anthropic in late 2024 and now an open, community-maintained standard, MCP is supported across a wide range of clients (Claude Desktop and Claude Code, ChatGPT, VS Code, Cursor, and others). The specification covers two transports (local stdio and remote Streamable HTTP, which supersedes the older HTTP+SSE transport), server-side tools, resources, and prompts, and an OAuth 2.1-based authorization flow for remote servers. The public server ecosystem is large and growing fast, spanning official Anthropic servers, vendor servers, and community projects.

If you do not already use Claude, you can try Claude free for a week and follow along with every example in this handbook. The guide covers MCP server development end-to-end, from your first server to production deployment with authentication.

TL;DR:

What you'll learnSection
MCP architecture and how it differs from REST/GraphQL§1–2
Build your first server in TypeScript§3
Build your first server in Python§4
Connect to Claude Desktop and Claude Code§5–6
OAuth 2.1 security and production auth§7
Top 20 production MCP servers§8
MCP for web scraping§9
Enterprise deployment patterns§10

Prerequisites:

  • Node.js 18+ or Python 3.10+
  • Claude Desktop or Claude Code installed
  • Basic understanding of APIs and JSON
AI agents5 min read

Top AI Agents & MCP Integrations on Apify (2026)

· 5 min read
Yassine El Haddad
Software Developer & Automation Specialist

Large Language Models require synchronous access to the live web to prevent hallucination. The AI Agents collection on Apify provides the critical orchestration layer—fully managed Model Context Protocol (MCP) servers and autonomous headless browser frameworks—with the picks below biased toward agents that already see real execution volume.

Apify5 min read

Model Context Protocol (MCP): Architectural Implementation (2026)

· 5 min read
Yassine El Haddad
Software Developer & Automation Specialist

Large language models have no native access to the outside world. On their own they cannot read a URL, query a database, or run a tool. Historically, bridging a model to live internet data meant writing brittle per-framework glue (LangChain tool definitions mapping to REST endpoints, and a different wrapper for the next framework).

The Model Context Protocol (MCP) standardizes that boundary. Anthropic introduced it in November 2024, and it is now an open standard that hosts like Claude, Cursor, and VS Code all speak. Think of it as a USB-C port for AI applications: one connector, many tools.

This guide walks through the mechanics of MCP and a worked setup that connects the Apify MCP server so an AI client can reach the live web by running Apify Actors.

Guides on this site

Frequently asked questions

Frequently Asked Questions

MCP is an open standard from Anthropic that defines how AI models interact with external tools and data sources. It standardizes tool definitions, authentication, and response formats so AI assistants can call APIs, run code, and access databases consistently across different LLM providers and host applications.

The Apify MCP server exposes actor runs, dataset reads, and key-value store access as MCP tools. AI assistants like Claude can call start_actor_run with an actor ID and input, then poll and read the resulting dataset—all from a natural language conversation. This turns Apify into an AI-native data collection layer.

MCP removes the need to write glue code between AI systems and scraping infrastructure. Agents can request scraping tasks in natural language, get structured results back, and chain scraping with analysis—all within one session. It also standardizes auth and tool discovery, making it easier to swap between MCP-compatible tools.

Use scoped API tokens with minimal permissions. Restrict which actors the MCP server can invoke. Log all tool calls with request and response metadata for auditability. Rate-limit the MCP server to prevent runaway agent loops. Treat MCP calls like any API integration—include them in your threat model and incident response plan.