GRTwo Docs

io.github.grtwo-jcanslerPublished by GitHub account grtwo-jcanslerv1.5.0Updated Oct 24, 2026

Publish and share Markdown/HTML docs from AI assistants. Requires grtwo.app Pro. OAuth or API key.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A remote MCP server that lets an AI assistant publish and share Markdown or HTML documents through grtwo.app.

What you can do
Publish Markdown or HTML documents from an assistant session to grtwo.app for sharing. The manifest lists no individual tools, so the exact operations are not documented; the stated purpose is publishing and sharing docs. Access is tied to a grtwo.app Pro account.
When to use it
Useful when you want an assistant to turn its output into a shareable document on grtwo.app rather than leaving it in the chat, and you already have or plan to get a grtwo.app Pro account.
Requirements
A remote endpoint at grtwo.app reached over streamable HTTP. OAuth authentication is required, and the description also mentions an API key as an alternative. A grtwo.app Pro subscription is required. No environment variables or headers are declared.
Before you install
Publishing sends your document content to grtwo.app, a third party, and shared docs may be visible to others. It requires a paid Pro subscription. OAuth grants access to your account, so review the scopes requested; treat any API key as a secret.

Installation

In SourceWeft

  1. Open GRTwo Docs in the dashboard and add it to a workspace.
  2. Connect the required 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.grtwo-jcansler%2Fdocs/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "grtwo-docs": {
      "type": "http",
      "url": "https://www.grtwo.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.5.0LatestSep 16, 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.