Model Context Protocol

Marketing your AI can actually operate

NexoFlow ships a remote MCP server. Claude, Cursor, and any MCP client can read your real marketing data and create work inside NexoFlow- without a browser, a scraper, or a custom integration.

Connect MCP See how it works

https://nexoflow.net/mcp

NexoFlow stops being an app you log into and becomes a tool your AI assistant can operate on your behalf. “What should I write about this month?” reaches real Search Console data, real calendar state, and real past performance- and can come back with drafts already waiting for approval.

How it works

Three steps from assistant to pipeline

01

Connect your assistant

Point Claude Desktop, Claude Code, Cursor, or any MCP client at the hosted endpoint. Use a personal token or OAuth- nothing to install locally.

02

Grant only what you mean

Tick scopes and projects deliberately. Read-only tokens never see write tools. Write tokens refuse a one-click grant across every client project.

03

Ask- then approve in the app

Your assistant reads Search Console, calendars, and performance- then drafts and schedules into NexoFlow. Nothing goes live instantly.

Connect

Remote. Hosted. Ready for your client.

Streamable HTTP with JSON responses- deliberately not long-lived SSE- so it stays compatible with NexoFlow's deployment model. Stateless per request. Nothing to install.

Personal tokens from Account Settings → MCP
OAuth 2.1 with mandatory PKCE for discovery-capable clients
Active subscription checked on every request
Rotate in one click with a 60-minute grace window

Personal tokens

Name a credential, tick scopes and projects, set expiry (default 90 days). You get a nxf_mcp_… token shown once. Only a SHA-256 digest is stored.

Delegated OAuth

Full OAuth 2.1 authorization server with discovery, refresh-token rotation, and consent that says “read and change” when write scopes are in play- never soft-pedaled as read-only.

mcp.json

{
  "mcpServers": {
    "nexoflow": {
      "url": "https://nexoflow.net/mcp",
      "headers": {
        "Authorization": "Bearer nxf_mcp_…"
      }
    }
  }
}

Use cases

Ask in plain language. Get real work done.

Concrete prompts that map to shipped tools- not a chatbot bolted onto a dashboard.

What should I write about?

Striking-distance keywords from your own Search Console- the same demand data NexoFlow's content engine uses.

What's working on Instagram?

Winning patterns from your top posts, plus the day and hour this brand actually earns engagement.

Draft next month's plan

Proposed blog plans land unscheduled in NexoFlow- ready for review, never silently queued.

Queue that post

Schedule with a real cancel window. Publish is never silent, never immediate.

Built for trust

An AI with write access- bounded on purpose

Handing an assistant your marketing sounds alarming. Here's what stops it: no instant publishing, a cancel window, notifications, and permissions you tick individually.

No instant publishing

There is no publish-now path. "Publish" schedules at least 30 minutes ahead, with a buffer so the window stays honest after the write.

Every write is reversible

Idempotent calls, snapshots before overwrites, and a revert tool. Repeat keys replay the stored result instead of writing twice.

You're notified on every change

Each write lands in an audit trail and notifies the token owner in the app- so the cancel window is a real control, not theory.

Hidden tools stay hidden

If a token lacks a scope, those tools are never registered. A read-only assistant cannot even see that write tools exist.

Project-bound credentials

Every token is tied to an explicit project list. Checks run against the resolved project id- not a caller hint that could cross brands.

Forced safety defaults

Write arguments are allow-listed. Safety flags are stamped after the model speaks- drafts stay drafts, plans stay unscheduled.

Cancel-after, not approve-before

A human who is asleep doesn't get a veto. That's adequate for content on your own site that you review. Instant publish-now or anything landing in someone else's inbox would require a pending approval flow we haven't shipped- and we won't pretend otherwise.

Tool catalog

29 tools. Same data your dashboard uses.

18 read tools and 11 write tools. Search Console reads the same six-hour cache as NexoFlow's own content engine- so suggestions and generation share identical demand data.

Read · sample of 18

nexoflow_get_search_keywords

Top queries and striking-distance opportunities

nexoflow_get_content_calendar

Website, social, and GBP items with gap detection

nexoflow_get_winning_patterns

Caption, CTA, format, and hashtag patterns that worked

nexoflow_get_best_posting_times

Day and hour this brand earns engagement

nexoflow_get_search_performance

Clicks, impressions, CTR, position with deltas

nexoflow_get_ai_usage

Generation counts, tokens, estimated spend

Write · sample of 11

nexoflow_draft_website_post

Draft a website article

nexoflow_propose_blog_plans

Propose plans- always unscheduled

nexoflow_propose_social_drafts

Generate social drafts

nexoflow_schedule_website_post

Schedule with a cancel window

nexoflow_revert_write_operation

Restore a previous write

nexoflow_pause_autopilot

Pause automated generation

Permissions

Nine scopes. Nothing inherited by accident.

New credentials default to project discovery only. Everything else must be ticked deliberately- including full article text, which is a separate scope because generated posts can quote uploaded knowledge documents.

Write tokens disable "select all" across projects
Connections can be paused, never re-enabled via MCP
Deletes, org invites, and API key retrieval stay off-limits
Third-party text is marked untrusted for consuming agents

Scope catalog

projects:readreadProjects and connection health

content:readreadPlans, calendar, SEO fields

content:read_fullreadFull article text (separate on purpose)

analytics:readreadAnalytics and Search Console

reviews:readreadGoogle Business reviews

content:draftwriteCreate drafts and ideas

content:writewriteEdit posts and plans

content:schedulewriteSchedule posts

connections:writewritePause connections or autopilot

FAQ

Common questions

Put NexoFlow in your assistant's toolkit

Create an MCP credential in Account Settings, paste it into Claude or Cursor, and start asking questions against your real marketing stack.

Get started Developer API