Archipelago

io.github.AlexReiner98Published by GitHub account AlexReiner98v1.0.0Updated Nov 3, 2026

A living map of all your work that keeps you, your team, and your agents on the same page

VerifiedStreamable HTTPWeb executable

Overview

Archipelago's hosted MCP server (app.archipelago.tools); OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
app.archipelago.tools
Last checked

Installation

In SourceWeft

  1. Open Archipelago 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.AlexReiner98%2Farchipelago/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": {
    "archipelago": {
      "type": "http",
      "url": "https://app.archipelago.tools/mcp"
    }
  }
}

README

Archipelago

[Tests]

[A living map of all your work: islands drawn in stacked rows, parting round the title and its line, from a chat to a structured model that keeps you, your team, and your agents on the same page.]

A living map of all your work. From a chat to a structured model that keeps you, your team, and your agents on the same page.

Early: built and used daily by its author; expect rough edges.

AI is speeding up lots of tasks, but more speed is only helpful if you're moving in the right direction. Making a map before you execute helps identify risks and dependencies, and makes it easy to keep track as people and agents work.

One shared map means anyone can pick up the work at any time, from anywhere. Detailed history makes it possible to analyze how projects actually developed, what was missed, and how to improve.

The site is archipelago.tools.

How it works

Archipelago is a small unopinionated core, the rest is yours to shape.

People stay in control. Agents do much of the work, and you decide what needs your approval. Every change records the source of authority, and what is applied can be undone. You stay in charge

The log is the truth. Every change is added to one log and never rewritten. Undo, history, live updates and backups all read the same record. docs/log.md

Everything is an item, every item has a type. Every type extends one of seven kinds. Because Archipelago is built around those kinds, what works on the types we ship works just as well on a type you add.

Plugin architecture. Packs are where opinion enters the system. Create a pack with the item types, link types, view styles, and features you need. A type, view or rule of yours works like the ones that ship. Write a pack

One surface for people and agents. You and your agents use the map through the same tools. What an agent is told is kept on the map, where you can read and change it. The agent tools

One way to read. A query is a filter, a walk and a limit, and a view is a query with its layout. You and your agents read the same query.

Host it yourself

Archipelago is one Node 24 server and a persistent disk, MIT licensed, with everything included. The database is embedded; for a team, keep the maps on a Postgres server instead. If you'd rather not run a server, the Quickstart has it running for you in about five minutes.

bash
git clone https://github.com/AlexReiner98/archipelago.gitcd archipelagonpm installnpm start

Open http://127.0.0.1:3100, go to Workspace and type your name under Owner. To look around first, npm run demo opens a map of Archipelago itself on port 3200, its data kept apart.

Connect Claude Code

In the folder of a project you work on, with the server running:

bash
node -e "fetch('http://127.0.0.1:3100/connect/setup.mjs').then(r=>r.text()).then(t=>import('data:text/javascript,'+encodeURIComponent(t)))"

It lists the files it will write (.mcp.json, a few hooks, working rules in CLAUDE.md) and asks first. Add -- --dry-run to only see the list, or -- --remove to take it out. Then reopen Claude Code in that folder and say:

Put this project in Archipelago, with the three things I am working on as tasks, and tell me what you would do first.

Your tasks appear on the map right away. To take anything back, open Changes and choose Undo. Any other MCP client works the map at http://127.0.0.1:3100/mcp.

Read on

Copyright 2026 Aperture Design Tools Inc. MIT License.

Source: README.md at commit 7d8304f

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.0.0LatestNov 3, 2026

Score

85% 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
  • License10 pts