Monton

dev.montonPublished by monton.devOfficial publisherv1.0.2Updated Nov 7, 2026

Write and revise cloud docs with Claude, ChatGPT and your team. Review and comment from your phone.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Monton is a remote cloud document workspace that lets an assistant help write and revise docs together with Claude, ChatGPT and your team.

What you can do
  • Draft and revise cloud documents with the assistant's help
  • Collaborate on the same docs with teammates and other AI assistants
  • Review and comment on documents, including from a phone
  • No tool list is published, so exact capabilities are not documented
When to use it
Useful when you keep working documents in a shared cloud workspace and want an assistant to help draft, revise and review them alongside teammates, including on mobile.
Requirements
A remote MCP endpoint at monton.dev reached over streamable HTTP; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your Monton account and its documents; review the scopes requested at sign-in. Documents are shared with teammates and other AI assistants, so check who can see and edit them before adding sensitive content.

Installation

In SourceWeft

  1. Open Monton 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/dev.monton%2Fmonton/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": {
    "monton": {
      "type": "http",
      "url": "https://monton.dev/mcp"
    }
  }
}

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

3
  1. v1.0.2LatestNov 7, 2026
  2. v1.0.1Oct 30, 2026
  3. v1.0.0Oct 21, 2026

Score

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.