💬 Slack MCP
The Slack MCP connects the agent to your workspace's channels and DMs. Typical tools: read_channel (read recent messages), send_message (send message), search_messages (search the history). You need a OAuth Bot Token configured as an environment variable.
Real-world use case: you ask "summarize the last 50 messages in the #engineering channel," and the agent reads and processes them, then gives you a summary. Or "post in #standup: deploy of module X complete," and it posts for you.
"slack": {
"command": "npx",
"args": ["-y", "@anthropic/mcp-server-slack"],
"env": {
"SLACK_BOT_TOKEN": "xoxb-seu-token-aqui"
}
}In one sentence: Slack MCP = read, send, and search Slack messages through an agent.
📆 Google Calendar MCP
With the Calendar MCP, the agent can list events (list_events), create meetings (create_event), check availability (check_availability). You need a Google Service Account or OAuth2 configured.
Practical example: "what's on my schedule tomorrow?" and the agent fetches the events, summarizes them, and highlights conflicts. Or "schedule a call with Joao tomorrow at 2 p.m." and it creates the event directly.
In one sentence: Calendar MCP = view, create, and manage Google Calendar events through an agent.
📧 Gmail MCP
The Gmail MCP exposes tools for search_emails, read_email, send_email, create_draft. The agent can triage your inbox: read unread emails, summarize them, and even draft replies for you to review.
Be careful with permissions: send_email actually sends it. If you only want triage, use create_draft instead of send, and review it before sending.
Be careful with send_email
The agent can send real emails. If you don't want that, configure the MCP in read-only mode or remove the tool send_email of the permissions in settings.json.
In one sentence: Gmail MCP = email triage, search, and drafting directly in the agent.
📝 Notion/Linear MCP
MCPs for project management: o Notion MCP lets you create pages, search docs, and update databases. The Linear MCP lets you create issues, list sprints, and update status. Both need API keys in the env.
Scenario: the agent finishes a coding task, automatically creates a review issue in Linear, and documents the change in Notion. No manual project management work.
In one sentence: Notion/Linear MCPs = automatic documentation and issues without leaving the agent.
🔗 Combining Multiple MCPs
The true power of MCP emerges when you run 3-5 servers at the same time. The agent sees all the tools from all servers and can orchestrate across them. Example: "read the client's email, create an issue in Linear, and notify them in Slack" = three MCPs in a single instruction.
Be careful with the tool budget: each tool the agent sees consumes context tokens (the schema is in the system prompt). With 50+ tools, context costs go up. Keep only the MCPs you actually use every day.
In one sentence: multiple MCPs simultaneously = the agent orchestrates across tools without code.
⚡ Everyday Automations
Ready-to-use recipes you can copy and adapt:
Morning briefing
"Read my unread emails, show me today's calendar, and summarize the latest messages in #general on Slack."
Post-deploy notify
"Post in Slack #deploys: 'Deploy v2.3 completed' and create a page in Notion with the changelog."
Email triage
"Read the 20 most recent emails, sort them by urgency, and draft replies for the urgent ones."
Sprint review
"List the issues completed in Linear this week and generate a standup summary."
In one sentence: combine productivity MCPs into workflows that run with a single instruction.
🧾 Module Summary
Next module:
3.4 — Database and API MCPs: Postgres, Redis, REST, GraphQL.