Atlas Red mind maps

com.atlas-redPublished by atlas-red.comOfficial publisherv1.1.0Updated Oct 28, 2026

Build and edit real mind maps from a chat: brainstorm, plan, organise notes. Free, never metered.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Atlas Red server that lets an assistant build and edit real mind maps from a chat for brainstorming, planning and organising notes.

What you can do
  • Create mind maps from a conversation, turning a brainstorm or outline into a structured map.
  • Edit existing mind maps, adding and reorganising content as the discussion develops.
  • Use maps to plan work or organise notes, with the map itself as the shared artifact.
  • No tool list is published, so the exact set of operations is not documented.
When to use it
Useful when you want an assistant to turn a chat brainstorm, plan or set of notes into a visual mind map you can keep editing, rather than a plain text outline.
Requirements
A remote endpoint at app.atlas-red.com over streamable HTTP; OAuth sign-in is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access to your Atlas Red account, so review the scopes requested. The server creates and edits mind maps in that account, which changes stored data. The description says it is free and never metered, but no pricing or data-handling details are provided.

Installation

In SourceWeft

  1. Open Atlas Red mind maps 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/com.atlas-red%2Fmind-map/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": {
    "atlas-red-mind-maps": {
      "type": "http",
      "url": "https://app.atlas-red.com/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

2
  1. v1.1.0LatestOct 15, 2026
  2. v1.0.0Sep 16, 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.