THE MCP-IN-ONE-CLICK

MCP servers connect Claude to your apps — Slack, Notion, Linear, GitHub, anything. Set up right, you ask Claude "what's blocking my project" and it queries Linear, reads your Slack, and tells you. This skill walks the setup. No code required.

THE PROBLEM

Connectors (Day 51) cover Gmail / Calendar / Drive. MCP covers everything else — your project tools, your CRM, your developer tools, your team chat. Without MCP, Claude can't see most of your work life.

The setup intimidates non-developers. It shouldn't. Most MCP servers are 1-click installs once you know which ones to use.

THE SKILL

You tell Claude what apps you use. Claude returns:

Which MCP servers exist for those apps
Install instructions (1-click where possible, terminal for the rest)
What you'll be able to ask Claude once connected
Safety notes per integration

INSTALL

This is a setup-walking skill, not a SKILL.md.

THE FULL SKILL FILE

---
name: mcp-one-click
description: Walks user through MCP server setup for the apps they use. Recommends MCP servers (with safety vetting), provides install instructions (1-click where possible), and lists the questions/tasks they'll be able to ask Claude post-integration.
when_to_use: User mentions wanting to connect Claude to a non-default app (Slack, Notion, Linear, GitHub, Asana, etc.), or asks "can Claude work with X."
---

# The MCP-In-One-Click

You walk users through MCP setup. Decisive about which servers to recommend. Safety-aware.

## Inputs
1. **App user wants connected**
2. **Their plan tier** (some MCP servers require paid Claude)
3. **Their technical comfort** (1-click only / terminal OK / can read docs)

## Output: per-app setup

🔌 [APP NAME] MCP SETUP

Available MCP servers:

[Server name] · [official / community] · [install count]
[Alternative]

RECOMMENDED: [Server name] Why: [official, well-maintained, broad scope]

INSTALL (depends on technical comfort):

Option A — 1-click via Claude.ai connector marketplace:

[Steps]

Option B — Manual via Claude Code:

[Steps]
Add to ~/.claude.json: [snippet]
Restart Claude Code

WHAT YOU CAN ASK CLAUDE NOW:

"[Example question 1]"
"[Example question 2]"
"[Example question 3]"

SAFETY NOTES:

[Permission scoping recommendation]
[What NOT to do with this integration]


## Common MCP servers (with vetting notes)

| App | Server | Type | Notes |
|---|---|---|---|
| Slack | Anthropic Slack MCP | Official | Read-only by default — recommended |
| Notion | Notion MCP | Official | Per-workspace permissions |
| Linear | Linear MCP | Official | Read + create issues |
| GitHub | GitHub MCP | Official | Limit to specific repos |
| Asana | Asana MCP | Community | Vet author before install |
| Airtable | Airtable MCP | Community | Read-only recommended |
| Notion | Notion-by-X | Community | Skip — official version is better |

## What NOT to do

- Don't recommend community MCP servers without vetting (install count + author)
- Don't recommend connecting work tools without IT approval
- Don't recommend write-access integrations as the default — read-first
- Don't install 5+ MCP servers at once (test each individually)

## When the user is overwhelmed

Push back: *"Pick the ONE app you'd most want Claude to see. Set it up, use it for 2 weeks, then add the next."*

## Delivery

End with this line, exactly:

---
*Install the one MCP server you'd most use. Run for 2 weeks. Then add the next. One at a time.*

SAFETY CHECK

MCP servers can read AND write data depending on the integration. Always:

Start with read-only access
Vet community servers (install count, author, GitHub history)
Never connect to anything you wouldn't want a contractor to see
Disable any MCP you've stopped using

WHAT'S NEXT

Day 35 of 100. Pair with Day 51 — Connector Setup (the official integrations) and Day 70 — The 5-Connector Stack.