tinyfish

io.github.doc2mcpPublished by GitHub account doc2mcpv1.0.1792469327Updated Oct 27, 2026

MCP server for tinyfish documentation, generated by doc2mcp.

The publisher's own server: TinyFish AI Web Agent

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Hosted MCP server that serves a tinyfish documentation project converted by doc2mcp, letting an assistant query that documentation.

What you can do
  • No tools are listed in the manifest. Based on the description and README, this is a hosted endpoint generated by doc2mcp from a documentation source, so an assistant can reach that converted documentation through the MCP connection.
  • The doc2mcp platform turns a documentation URL into a hosted MCP URL plus a bearer token that is pasted into an editor's MCP configuration.
  • Each converted project is published under the doc2mcp namespace in the MCP Registry.
When to use it
Use it when you want an assistant to work against this specific tinyfish documentation set without building your own retrieval setup, and you already have a doc2mcp project token for it.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A bearer token is required in the Authorization header, taken from the project's Connect tab. A doc2mcp account is needed to create and manage the project.
Before you install
The Authorization header carries a project MCP token that the README says to treat like a password; keep it out of shared configs and repositories. The service is hosted by a third party, so documentation queries go to that provider. The product source is private and the README does not describe what data is stored or logged.

Installation

In SourceWeft

  1. Open tinyfish 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%2Ftinyfish/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": {
    "tinyfish": {
      "type": "http",
      "url": "https://www.doc2mcp.site/api/mcp/1048e4a1-f431-4694-8297-c573624c4ed4/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.1792469327LatestOct 20, 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.

Other Tinyfish integrations