Claude · Setup

The 4 MCP servers to install in Claude Code, and the prompt that wires them in one go

Context7, Playwright, Firecrawl and Composio installed from a single message, with the exact verified commands, the two API keys to grab, and what to know about security before you connect.

QQuentin Megevand
September 19, 2026 · 7 min read

Claude Code knows how to write code. It has no idea how to read a web page, drive a browser, or touch your apps. Those abilities get added, and they get added in one evening. An MCP server is a skill you wire once and Claude keeps for good.

Four of them cover almost everything you will ask for: reading current documentation, driving a browser, extracting the content of a site, and acting inside your apps. The prompt below installs all four, one at a time, asking for your keys at the right moment.

Claude AI Lab

The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.

Join the Lab →
✅What you need
1
Claude Code installed, on a paid plan. Every command in this article is verified on version 2.1.278.
2
Node.js 20 or higher. Check with node --version. Two of the four run through npx.
3
A Firecrawl account on firecrawl.dev. Free, no credit card.
4
A Composio account on composio.dev, only if you want the fourth one. Read the security section before you decide.
1

The install prompt

📋 paste into Claude Code

Open Claude Code in your terminal, in any folder. Paste this message and send it. Claude installs Context7 and Playwright on its own, then stops to ask for your Firecrawl and Composio keys.

I want you to configure 4 MCP servers in Claude Code.
Do them one at a time and tell me if any of them fails.

1) Context7: current documentation for libraries and frameworks.
   No API key needed:
   claude mcp add --scope user context7 -- npx -y @upstash/context7-mcp@latest

2) Playwright: drive a real browser (open pages, click, fill forms).
   No API key needed:
   claude mcp add --scope user playwright -- npx -y @playwright/mcp@latest

3) Firecrawl: extract the content of web pages so you can process it.
   Ask me for the FIRECRAWL_API_KEY before you run this.
   Once I have given it to you:
   claude mcp add --scope user firecrawl -e FIRECRAWL_API_KEY=<MY_KEY> -- npx -y firecrawl-mcp

4) Composio: connect Claude to my apps and run actions inside them.
   Ask me for the Composio MCP URL and the X-API-Key.
   Once I have given them to you:
   claude mcp add --scope user --transport http composio "<MY_URL>" --header "X-API-Key: <MY_KEY>"

When you are done:
- Run `claude mcp list` and show me the status of all 4.
- Remind me to quit and reopen Claude Code so they load.
- If one stays disconnected, tell me the exact error and how to fix it.

Do nothing else: leave the 4 configured and verified.
The detail that matters
--scope user installs the servers for your account, not for the current folder. Without it, you reinstall them in every project. Folder scope is the command default, and it is rarely what you want.
2

The 4 servers

🔌 what each one unlocks
📚
Context7
Injects up to date library documentation while Claude codes. Without it, Claude answers from what it memorised during training, so sometimes from a version that shipped two years ago. Free, no key.
🎭
Playwright
Claude drives a real browser. It opens pages, clicks, fills forms, runs a full journey. This is what you use to test a funnel or pull data from behind a login. Free, no key.
🔥
Firecrawl
Turns any page into clean, usable text. Playwright navigates, Firecrawl extracts. They complement each other instead of competing. Free key required.
🔗
Composio
A gateway to more than a thousand applications, Gmail, Slack, Notion, Calendar and the rest, with the ability to act inside them. Account and key required, and a whole section below.

The line between the first two and the last two is not power, it is perimeter. Context7 and Playwright stay on your machine. Firecrawl and Composio route through a third party, with a key that identifies you and gets billed.

3

The two API keys

🔑 firecrawl.dev and composio.dev
🔥Firecrawl
5
Create an account on firecrawl.dev. The free plan gives you 1,000 credits a month, no credit card.
6
Credits reset at the start of each cycle and do not roll over. One extracted page costs one credit.
7
Copy the key from your dashboard and hand it to Claude when it asks.
🔗Composio
8
Create an account on composio.dev, then connect the applications you actually want to drive.
9
Grab two things from your panel: the MCP server URL, and the key that travels in the X-API-Key header.
10
Connect only the applications you need this week. Every connected app is one more door behind the same key.
General rule
An API key gets pasted into the terminal, never into a file you commit. --scope user stores it in your Claude configuration, outside your repository.
4

Composio and security

🛡️ read before wiring

Composio is the most capable of the four, and the only one that deserves a decision rather than a reflex install. On 21 May 2026, the company disclosed a security incident itself: an attacker exfiltrated roughly 5,241 API keys and 5,001 GitHub OAuth tokens.

The entry point is worth knowing, because it says something about the model. The attacker came in through the Gmail OAuth token of an employee, intercepted magic link sign-in emails, then climbed to the production systems holding customer secrets, over a window of about eight hours. Composio revoked every user's GitHub tokens as a precaution, not only the ones with evidence of compromise, and paused releases while it investigated.

🎯
What it changes in practice
You are not handing a key to a tool, you are parking your application access with a third party. The day that third party falls, your access falls with it.
✂️
Connect the strict minimum
Three useful applications beat fifteen wired up "just in case". Your connection list is your attack surface.
🔄
Plan the revocation
Know where to revoke each connected app before you need to. Incident day is the wrong time to hunt for the button.
🧪
Separate your accounts
For client work, use the client's Composio account, not yours. Their access stays with them.
Verdict
The first three install with no trade-off to weigh. Composio is a decision: real capability against parking your access with a third party. If you do not have five applications to drive, start with three servers.
5

Check and troubleshoot

🩺 claude mcp list
🔎The three checks
11
Quit and reopen Claude Code. Servers load at startup only. This is the number one cause of "it does not work".
12
Run claude mcp list. You should see all four names with their connection status.
13
Ask for a real task. A server does nothing on its own, it waits for a request: open this page and summarise it, find the docs for this library, send me that recap.
2
servers with no API key at all
1,000
free Firecrawl credits per month
2.1.278
Claude Code version the commands are verified on

A server that stays disconnected almost always comes down to one of three things: Claude Code was not restarted, Node is below version 20, or the key was pasted with an extra space. For the Composio header, the flag is --header, singular, with -H as the short alias.

Important
The prompt installs the servers, it does not do the work. Once the four are in place, everything depends on what you ask next.

Where to start

Install Context7 and Playwright tonight, they cost nothing and ask nothing of you. Add Firecrawl when you have a real page to extract. Keep Composio for the day you have five applications to drive, and wire it knowing exactly what you are doing.

Four servers, one message to paste, and a Claude that goes from talkative to operational.

Want to go further?

And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing