network

io.github.doc2mcpPublished by GitHub account doc2mcpv1.0.1785624232Updated Oct 25, 2026

MCP server for network documentation, generated by doc2mcp.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A hosted doc2mcp server that exposes converted network documentation to an assistant over a remote MCP endpoint.

What you can do
Serves documentation that was converted into an MCP project by doc2mcp, so the assistant can draw on that documentation while answering questions or writing code. Access is per project, using the project's own MCP token. The manifest lists no individual tools, so the exact operations depend on the converted documentation.
When to use it
Use it when you have already created a doc2mcp project from a documentation source and want an assistant such as Cursor, Claude or VS Code to consult that documentation directly.
Requirements
A remote MCP endpoint at doc2mcp.site, a doc2mcp account and a project, and a bearer token from the project's Connect tab sent in the Authorization header.
Before you install
The Authorization bearer token is a credential and should be treated like a password; anyone holding it can reach the project's MCP server. Documentation content is hosted by a third-party service, so consider what material you convert and share.

Installation

In SourceWeft

  1. Open network 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.doc2mcp%2Fnetwork/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": {
    "network": {
      "type": "http",
      "url": "https://www.doc2mcp.site/api/mcp/627464b0-c66d-44f0-a60d-76664a9bdbb1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

doc2mcp

Paste docs → get a hosted MCP server for Cursor, Claude & VS Code

Turn any documentation URL into a live Model Context Protocol server in under 60 seconds.

[Live] [MCP Registry] [npm] [GitHub stars] [License: MIT]

[doc2mcp on Product Hunt]

Try it free · Docs · Marketplace · Pricing

⭐ Star this repo — it helps developers discover doc2mcp on GitHub and the MCP Registry.

What is this repo?

This is the public face of doc2mcp on GitHub:

RepoVisibilityPurpose
doc2mcp/doc2mcp-registry (this repo)PublicMCP Registry manifest, badges, discovery
doc2mcp/doc2mcpPrivateProduct code (not open source)

The live product runs at doc2mcp.site. Source code stays private so the platform cannot be copied.

How it works

  1. Sign in at doc2mcp.site/login
  2. Paste a docs URL (Stripe, LangChain, your own Mintlify site, OpenAPI, GitHub repo…)
  3. Get a hosted MCP URL + Bearer token
  4. Paste into Cursor / Claude / VS Code mcp.json
  5. Every MCP you create is auto-listed on the official MCP Registry as io.github.doc2mcp/<slug>
json
{  "mcpServers": {    "my-docs": {      "url": "https://doc2mcp.site/api/mcp/{project_id}/mcp",      "headers": { "Authorization": "Bearer <your-token>" }    }  }}

CLI

bash
npm install -g doc2mcpdoc2mcp logindoc2mcp https://docs.example.com

MCP Registry

EntryNamespace
Platform gatewayio.github.doc2mcp/doc2mcp
Your converted docsio.github.doc2mcp/<slug> (auto-published on each conversion)

Gateway manifest (server.json)

This repo publishes the canonical platform record via GitHub OIDC when you push a v* tag:

bash
git tag v1.0.2git push origin v1.0.2

Workflow: .github/workflows/publish-mcp.yml

Why a separate public repo?

The MCP Registry grants namespace io.github.doc2mcp/* only to workflows running inside the doc2mcp GitHub org. This small public repo holds the OIDC publish manifest — not the product source.

Links

License

The server.json manifest in this repo is MIT. The doc2mcp product code is proprietary and not distributed in this repository.

Source: README.md at commit 5a80226

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1785624232LatestSep 16, 2026

Score

75% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.