Begonia.pro

pro.begoniaPublished by begonia.proOfficial publisherv0.1.0Updated Oct 24, 2026

Local SEO: MCP for local business audits with tools and guidance.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Begonia.pro is a remote MCP server for local SEO audits of local businesses, giving an assistant tools and guidance for that work.

What you can do
Audit local business listings and local search presence with the server's tools and guidance. The registry description names local SEO auditing as the purpose, but no individual tools are listed, so the exact actions are not documented here.
When to use it
Worth considering when you want an assistant to help review or audit the local search presence of a local business and you already have a Begonia.pro account token.
Requirements
Remote streamable HTTP endpoint at begonia.pro. A required bearer token sent in the Authorization header, in the form Bearer followed by the token. Network access to the endpoint.
Before you install
The server requires a bearer token in the Authorization header; treat it as a secret and check what the server does with audit data before sending business details. No tools are listed, so confirm what it can read or change before relying on it.

Installation

In SourceWeft

  1. Open Begonia.pro 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/pro.begonia%2Fbegonia-pro/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": {
    "begonia-pro": {
      "type": "http",
      "url": "https://www.begonia.pro/mcp",
      "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. v0.1.0LatestSep 16, 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.