Frase MCP Server
OfficialFetch Google Search Console analytics data such as overview metrics, top queries, and top pages.
Publish content directly to Sanity CMS from Frase.
Publish content directly to Webflow from Frase.
Publish content directly to Wix from Frase.
Publish content directly to WordPress sites from Frase.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frase MCP ServerResearch 'ai visibility tools' and build a brief."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frase MCP Server
The content loop, run from your AI agent. This MCP (Model Context Protocol) server connects Claude, Cursor, Windsurf, VS Code, or any MCP client to Frase, the content operating system for AI search. Frase runs the loop content teams use to win Google rankings and AI citations, and this server puts that loop in your agent's hands:
Research what ranks and why: live SERP analysis, competitor breakdowns, topic clusters
Create briefs and drafts grounded in that research, in your brand voice
Publish straight to WordPress, Sanity, Webflow, Wix, or FraseCMS
Optimize every page for Google rankings and AI citations (ChatGPT, Perplexity, Gemini, Google AI) together
Track & fix: audit sites for decay and cannibalization, watch where AI engines cite you (and where they cite competitors instead), and surface the pages that need attention next
Why run it from an agent? Stacks that research in one tool, draft in another, and publish in a third lose context at every hop. Frase keeps research, drafts, scores, and publishing in one system — so your agent works with full context instead of copy-paste.
New to Frase? The server connects to your Frase account. Start a free 7-day trial (no credit card), then grab your API key from Settings → API.
What is MCP?
Model Context Protocol (MCP) is an open standard that allows AI assistants like Claude to securely connect to external tools and data sources. This server implements MCP to give Claude access to your Frase account.
Related MCP server: WordPress MCP Server
Quick Start
Option A: One-Click Install (Desktop Extension)
Desktop extension bundles are published on the Releases page. If no release is listed yet, use Option B or C below — same server, two commands.
Download the latest
frase-x.x.x.mcpbfile from ReleasesOpen Claude Desktop and go to Settings
Drag the
.mcpbfile into the Settings window (or use Install Extension)Enter your Frase API key when prompted (get it from Frase Settings)
Done — Claude can now access your Frase account
Option B: Claude Code (CLI)
Add the Frase MCP server to Claude Code with a single command:
claude mcp add frase -- npx -y @frase/mcp-server --api-key sk_live_your_api_key_hereClaude Code will automatically start the server when needed.
Option C: Manual Setup (npx)
1. Get your API key
Get your API key from Frase Settings.
2. Configure Claude Desktop
Add this to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"frase": {
"command": "npx",
"args": ["-y", "@frase/mcp-server"],
"env": {
"FRASE_API_KEY": "sk_live_your_api_key_here"
}
}
}
}3. Restart Claude Desktop
After saving the config, restart Claude Desktop. You should see "frase" in the MCP servers list.
Option D: Cursor
Add to your project's .cursor/mcp.json:
{
"mcpServers": {
"frase": {
"command": "npx",
"args": ["-y", "@frase/mcp-server"],
"env": {
"FRASE_API_KEY": "sk_live_your_api_key_here"
}
}
}
}Option E: Windsurf
Add to your Windsurf MCP config (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"frase": {
"command": "npx",
"args": ["-y", "@frase/mcp-server"],
"env": {
"FRASE_API_KEY": "sk_live_your_api_key_here"
}
}
}
}Option F: VS Code with GitHub Copilot
Add to your VS Code settings (.vscode/settings.json):
{
"github.copilot.chat.mcpServers": {
"frase": {
"command": "npx",
"args": ["-y", "@frase/mcp-server"],
"env": {
"FRASE_API_KEY": "sk_live_your_api_key_here"
}
}
}
}Prompts you can try
Once connected, ask your agent:
Run the whole loop on one topic
"Research 'ai visibility tools' in Frase, build a brief from the top competitors, draft the article in our brand voice, and publish it as a draft to our FraseCMS site."
See where AI cites you (and where it doesn't)
"Check our AI visibility for our main product queries. Which prompts cite us, which cite competitors, and what changed this week?"
Find what's decaying before it costs traffic
"Audit frase.io for content decay and cannibalization, and rank the fixes by likely traffic impact."
Turn a research session into a publishable draft
"Take my latest research session, generate an outline, and score the draft for both Google rankings and AI citations before I review it."
Your agent stays in control of nothing it shouldn't: every write goes to your account, drafts stay drafts until you publish, and the API key never leaves your local config.
Why run Frase from an agent?
Most content stacks research in one tool, write in another, optimize in a third, and publish in a fourth. Every hop loses context: the SERP data behind a brief, the reasoning behind an optimization, the research behind a page. Frase keeps the loop in one system, so an agent working through this server has the full picture at every step:
Research → Create: briefs are grounded in live SERP and competitor analysis your agent just ran, not pasted-in fragments.
Create → Publish: drafts go straight to WordPress, Sanity, Webflow, Wix, or FraseCMS — and FraseCMS keeps the research attached to the page it produced.
Publish → Optimize → Fix: published pages get scored for Google and AI citations, audited for decay, and tracked in AI answers, all through the same tools — so the next piece of work starts from what the last one learned.
You review and approve; the agent does the legwork. That is the working model across Frase — agent-native by design, human-in-the-loop by default.
Available Tools
Sites
list_sites- List all sites in your accountcreate_site- Create a new site to track
Briefs
list_briefs- List content briefs with optional status filtercreate_brief- Create a new brief (with optional auto-outline generation)get_brief- Get brief details including outline and SERP dataget_brief_status- Check brief generation progressexport_brief- Export a brief in JSON or Markdown format
Content
list_content- List content items with optional status filterget_content- Get content details including full body textgenerate_content- Generate content from a briefupdate_content- Update content title, body, status, or meta tagsdelete_content- Delete a content item (soft delete)get_content_status- Check content generation progressexport_content- Export content in JSON, HTML, or Markdown formatregenerate_content- Regenerate or improve content with optional instructionsrescore_content- Recalculate SEO, GEO, and EEAT scores for content
Research
list_research- List research sessionsstart_research- Start new AI-powered research on a topic (types: topic, competitor, gap, serp)get_research- Get research details with findings and sourcesdelete_research- Delete a research sessionexport_research- Export research findings in JSON or Markdown format
Jobs
get_job_status- Check status of async jobs (briefs, research, audits, content, etc.)
Audits
list_audits- List site auditsstart_audit- Start a new site audit (full, technical, content, or quick)get_audit- Get audit details with pages and issuesexport_audit- Export audit data as JSON or CSVaudit_page- Audit a single page URL for E-E-A-T, GEO, and SEO scores
SERP Analysis
analyze_serp- Analyze search engine results for a queryanalyze_competitors- Analyze competitor content for a queryget_search_intent- Get search intent classification for a query
AI Visibility
get_ai_visibility- Get AI visibility overview metricslist_prompts- List monitored AI promptscreate_prompt- Create a new monitored promptget_prompt- Get prompt details with citations and resultsupdate_prompt- Update a monitored promptget_competitors- Get AI visibility competitorsget_alerts- Get AI visibility alertsget_insights- Get AI visibility insights and recommendationsget_crawler_logs- View AI bot crawl activity on your sites
Analytics
get_gsc_overview- Get Google Search Console overview metricsget_gsc_queries- Get top search queries from GSCget_gsc_pages- Get top performing pages from GSCget_content_gaps- Get content gap opportunitieslist_performance_alerts- List performance alerts (traffic drops, ranking changes)resolve_alert- Mark a performance alert as resolved
Optimizations
list_optimizations- List optimization sessionsstart_optimization- Start optimization analysis for contentget_optimization- Get optimization details with suggestionsapply_optimization- Apply optimization suggestionsget_optimization_insights- Get optimization insights across contentdismiss_optimization- Dismiss an optimization
Webhooks
list_webhooks- List configured webhookscreate_webhook- Create a new webhookget_webhook- Get webhook detailsupdate_webhook- Update a webhookdelete_webhook- Delete a webhook
CMS Publishing
publish_content- Publish content to Frase CMS or connected platformslist_cms_connections- List CMS connection status for a site
Example Conversations
List your sites
You: What sites do I have connected?
Claude: [Uses list_sites tool]
Here are your connected sites:
| ID | Name | Domain | GSC | Created |
|----|------|--------|-----|---------|
| site_abc | Main Blog | example.com | Yes | Jan 15, 2024 |
| site_def | Product Site | product.example.com | No | Feb 20, 2024 |Create a brief with auto-outline
You: Create a brief about React performance optimization
Claude: [Uses create_brief with generate_outline=true]
## Brief Created
- **ID:** brief_abc123
- **Topic:** React performance optimization
- **Status:** pending
**Outline generation started.** Let me check the status...
[Uses get_job_status]
The outline is ready! Let me get the details...
[Uses get_brief]
## Brief: React performance optimization
### Outline
- Introduction to React Performance
- Common Performance Bottlenecks
- Optimization Techniques
- Measuring Performance
- ...Research a topic
You: Research best practices for Next.js SEO
Claude: [Uses start_research]
## Research Started
- **ID:** res_xyz789
- **Query:** best practices for Next.js SEO
- **Type:** topic
- **Status:** pending
I'll check on the progress...MCP Resources
Browse your Frase data directly in Claude:
frase://sites- List all your sitesfrase://sites/{id}- View individual site detailsfrase://content- List all content itemsfrase://content/{id}- View content with full bodyfrase://briefs- List all briefsfrase://briefs/{id}- View brief with outline
MCP Prompts
Pre-built workflows for common SEO tasks:
Prompt | Description |
| Full workflow: research, brief, outline, content generation |
| Analyze content and apply optimization suggestions |
| Research keywords, SERP analysis, and content opportunities |
| Analyze competitor content and find gaps |
| Run site audit and prioritize improvements |
| Full autonomous content lifecycle: research, brief, write, optimize, publish |
| Monitor performance, fix ranking drops, re-optimize underperforming content |
Test mode
Frase issues test API keys (sk_test_...) alongside live keys. A test key lets you — or your agent — dry-run the full integration without consuming credits or touching live content: run research, create briefs, score drafts, and exercise every tool call end-to-end, then swap to your sk_live_ key when the workflow is proven. Get both key types from Settings → API Keys.
If you are building an agent workflow, start with the test key. An agent that can rehearse a request before spending money completes integrations faster and makes fewer expensive mistakes.
Configuration
Variable | Required | Description |
| Yes | Your Frase API key |
| No | Override API URL (default: |
Troubleshooting
Server not appearing in Claude Desktop
Verify your config file location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Check JSON syntax - use a validator if needed
Restart Claude Desktop completely (quit and reopen)
Server not working in Claude Code
Verify the server is registered:
claude mcp listCheck server status:
claude mcp status fraseRemove and re-add if needed:
claude mcp remove frase
Authentication errors
Verify your API key is correct
Ensure the key has not expired
Check that the key has the required permissions
Rate limiting
The server automatically retries on rate limits with exponential backoff. If you're hitting limits frequently, consider spacing out your requests.
Support
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/frase-io/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server