netweft

io.github.souravsspacePublished by GitHub account souravsspacev0.1.1Updated Oct 25, 2026

Read an SEO workspace: projects, keywords, rank tracking, site audits, context. Read-only.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Netweft exposes a read-only SEO workspace — projects, keywords, rank tracking, site audits and context — to an AI assistant over a remote or local MCP endpoint.

What you can do
Read SEO workspace data: projects, keywords, rank tracking, site audits and context, all read-only.
When to use it
Useful when you want an assistant to answer questions about your existing Netweft SEO projects, keyword sets, ranking positions or audit results without switching tools.
Requirements
A Netweft account and API key, supplied as the NETWEFT_API_KEY environment variable or as an Authorization bearer header. Connects to the hosted endpoint at api.netweft.com by default, or to a self-hosted API URL via NETWEFT_API_URL; the npm package netweft-mcp runs locally over stdio. Network access required.
Before you install
The API key is a secret; keep it out of shared configs and logs. Access is described as read-only, so no writes are expected, but the server does read your SEO workspace data and sends it to the assistant.

Installation

In SourceWeft

  1. Open netweft 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/io.github.souravsspace%2Fnetweft/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": {
    "netweft": {
      "type": "http",
      "url": "https://api.netweft.com/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.1LatestOct 25, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.