Flocon AI

com.flocon-aiPublished by flocon-ai.comOfficial publisherv1.0.0Updated Nov 2, 2026

Publish SEO pages from Claude or Cursor to your website. Next.js now, more frameworks soon.

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Flocon AI lets an assistant publish SEO pages from Claude or Cursor directly to your own website, currently for Next.js sites.

What you can do
  • Publish SEO pages to a connected website from the assistant.
  • Work with Next.js sites, with other frameworks described as coming later.
  • Connect to a hosted remote endpoint rather than a local package.
When to use it
Useful when you draft SEO-oriented pages in Claude or Cursor and want them pushed to your live website without a separate publishing step. Aimed at site owners running Next.js who already have a Flocon AI account.
Requirements
A remote MCP endpoint at mcp.flocon-ai.com over streamable HTTP. A Flocon AI account and a website MCP token from the Flocon AI dashboard, sent as a bearer token in the Authorization header. A Next.js website to publish to.
Before you install
The server writes pages to your public website, so review what gets published. The required Authorization header carries a per-website MCP token; treat it as a secret and keep it out of shared logs or transcripts.

Installation

In SourceWeft

  1. Open Flocon AI in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.flocon-ai%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "flocon-ai": {
      "type": "http",
      "url": "https://mcp.flocon-ai.com/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.