Skip to main content

​
Getting Started with MCP

MCP (Model Context Protocol) is the connection layer between Claude and WisePilot. Once connected, Claude can read your website data, browse content, pull ad metrics, and generate new assets — all from a conversation. You give the direction; Claude does the navigation. This guide gets you connected and running your first command in under five minutes.

​
What You’ll Need

Before you start:
RequirementDetails
WisePilot accountMember of at least one website
RoleEditor or higher (Viewer access is read-only; generation requires Editor+)
Claude planPro, Team, or Enterprise (MCP requires a paid plan)
If you’re not sure of your role, check under Settings > Team & Roles in WisePilot, or ask your workspace admin.

​
Connecting Claude to WisePilot

The connection uses OAuth — the same secure flow as “Sign in with Google.” You authenticate once and Claude stores a short-lived token that refreshes automatically. For step-by-step connection instructions across Claude.ai, Claude Desktop, and Claude Code (CLI), see the full Claude MCP integration guide. The short version:
  1. Open Claude’s Settings > Integrations
  2. Add https://ai.wisepilot.app/api/v1/mcp as the server URL
  3. Complete the OAuth consent screen in WisePilot
  4. Claude confirms the connection is active

​
Your First Command

Once connected, paste this into Claude: 
List my websites and give me a summary of [website name].
Replace [website name] with the name of the website you want to work with.

​
What Claude will do

Claude runs two tool calls in sequence:
  1. list_websites — discovers all websites your account has access to and resolves the correct website ID
  2. get_website_summary — returns the website name, domain, active integrations, module configuration, and content counts
You’ll see Claude’s reasoning as it works, followed by a summary of what it found.
Always start a new session with “List my websites” if you haven’t used MCP recently. Claude needs the website ID to scope subsequent requests correctly — this one prompt sets the context for everything that follows.

​
What a healthy response looks like

A good first summary will show:
  • Website name and domain
  • Connected integrations (WordPress, Google Analytics, Google Ads, Meta, GHL)
  • Enabled modules (content, SEO, ads, conversations)
  • Approximate content counts (blogs, pages, CTAs)
If integrations are missing or modules look wrong, the next guide walks through how to review and fix your setup.

​
Next Steps

Work through the remaining onboarding guides in order:
  1. Website Setup — Review integrations, modules, and flag what’s missing
  2. Brand Voice & Positioning — Set your brand position and product tone before generating content
  3. ICP Discovery & Creation — Build ICP profiles and generate messaging dimensions
These guides are designed to be run in sequence. Each one builds on the data established by the previous step. Skipping brand voice before ICP creation is fine, but the ICP output will be less targeted without a brand position in place.