Topicforge

net.topicforgePublished by topicforge.netv1.0.0Updated Oct 24, 2026

Generate programmatic SEO articles, topic clusters, FAQ schema, and batch jobs via TopicForge.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant generate programmatic SEO articles, topic clusters, FAQ schema, and batch jobs through TopicForge.

What you can do
TopicForge exposes its content generation service to an assistant over stdio. According to the registry description, it can produce programmatic SEO articles, build topic clusters, generate FAQ schema, and run batch jobs. The manifest does not list individual tool names, so the exact operations are not documented here.
When to use it
Use it when you want an assistant to draft SEO-oriented content at scale, organize related topics into clusters, add FAQ structured data, or queue bulk generation jobs through a TopicForge account. It is aimed at content and marketing workflows rather than general web search or browsing.
Requirements
Runs as a local process over stdio, installed from the npm package @topicforge/mcp, so Node.js and npm are needed. Desktop only; no web executable. Requires a TopicForge API key in TOPICFORGE_API_KEY, and optionally a custom API base URL in CONTENT_API_BASE_URI (default Network access to the TopicForge API is required.
Before you install
Requires a TopicForge API key (TOPICFORGE_API_KEY, tf_live_...) that grants access to the account; treat it as a secret and avoid exposing it in logs or shared configuration. The server generates and submits content and batch jobs to TopicForge, so generated material and job data are sent to that third party. No payment or wallet handling is described.

Installation

In SourceWeft

  1. Open Topicforge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.