Skip to content

MCP Servers

Connect Claude to external APIs instantly no config files needed.

# What are MCP Servers?

MCP (Model Context Protocol) lets Claude talk to external services databases, APIs, Google Sheets, Meta Ads, and more. Think of it as plugging a USB cable into Claude.

With MCP, Claude can:

  • Read and write your Google Sheets
  • Query your PostgreSQL database
  • Pull Meta Ads campaign data
  • Search the web, manage GitHub, and more
# Easiest Way to Add MCP

No config files needed

Just tell Claude what you want

Forget editing JSON files or hunting down config paths. Just tell Claude what you want to connect and give it the MCP link. Claude installs the MCP server automatically.

Paste something like this into Claude (replace the link with your MCP server URL):

text
Set up the Meta Ads MCP server in this Next.js project. Use the official HTTP MCP endpoint at https://mcp.facebook.com/ads. Configure it in .mcp.json, run /mcp to trigger the OAuth login flow, and verify the tools are available. I have a Facebook Business Manager account with ads_management and ads_read permissions. If any scopes are missing, tell me exactly what to request.

Claude handles everything configures the server, walks you through OAuth, and verifies the tools work.

After it's done

Quit Claude (Ctrl+C) and enter again. Then run /mcp to trigger the browser-based OAuth flow. The MCP server will be active and ready to use.

# Meta Ads MCP

Connect Claude to Meta Ads Manager for campaign analytics, audience insights, and ad performance monitoring.

Paste this into Claude to set up Meta Ads MCP:

text
Add the Meta Ads MCP server globally using the CLI — run this exact command:

claude mcp add --transport http meta-ads https://mcp.facebook.com/ads

Then edit ~/.claude.json to make sure the meta-ads server has "enableAllProjectMcpServers": true set in its project config so it connects without a trust prompt.

Also, this project is a Next.js app — drop a .mcp.json in the project root (create one if it doesn't exist):

{
  "mcpServers": {
    "meta-ads": {
      "type": "http",
      "url": "https://mcp.facebook.com/ads"
    }
  }
}

And in .claude/settings.local.json, add "enableAllProjectMcpServers": true and "enabledMcpjsonServers": ["meta-ads"].

I already have a Facebook Business Manager account with ads_read and ads_management permissions, so OAuth scopes should be fine. Once the config is in place, tell me to restart Claude and run /mcp — that'll trigger the browser-based OAuth login flow.

Claude configures the MCP server, walks you through OAuth, and verifies the tools work. Then you can ask things like:

  • “Show me my top 5 campaigns this month”
  • “Which ad sets have the best ROI?”
  • “Pull audience insights for the last 30 days”