Back to Browse

Archipelago MCP Server

Developer ToolsModerate7.4MCP RegistryRemote
Free

Server data from the Official MCP Registry

Agent memory for human brains: your agent's plans and decisions as a map you read, correct, share.

About

Agent memory for human brains: your agent's plans and decisions as a map you read, correct, share.

Remote endpoints: streamable-http: https://app.archipelago.tools/mcp

Security Report

7.4
Moderate7.4Low Risk

Archipelago is a self-hosted shared work-map MCP server (Node, embedded PGlite or Postgres) with per-request bearer-style person tokens that scope access to workspaces. The MCP endpoint, view resource and CSP policy appear deliberately constrained; the visible code shows no exfiltration, shell execution, or hardcoded secrets. The package.json is clean with recognized dependencies, and the truncated three.js vendor file is a standard MIT library, though the full tool/auth implementation (src/server.ts, tools.ts) was not provided so token validation and dependency integrity could not be fully verified. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity).

5 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on the server that hosts it, not on your machine.

File System Write

Writes files on the server that hosts it, not on your machine.

database

Applies to the server that hosts this plugin, not to your machine.

env_vars

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "tools-archipelago-archipelago": {
      "url": "https://app.archipelago.tools/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Archipelago

Tests

If you're going somewhere uncharted, you should make a map. Archipelago is a map that draws itself while you work, so you and your agents never get lost.

Agent memory for human brains: your agent's plans and decisions as a map you read, correct, share.

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

  • Make a plan: Your agents make plans you can see on the map.
  • Work through it: Watch agents work through the map, keeping it up to date so you don't have to.
  • Customize: Tell your agent any problem you want to solve, and watch it create custom types, rules, views, styles, and more to model it clearly.
  • Never forget: Every change is saved. You and your agents can look back and see every step you've made so far.
  • Share: Collaborate live with your team, or publish for all. Anyone with the link can add it to their own map in a click.
  • Automate: Turn your map into a machine that acts. Automations reach into your programs or the web. Run them on a schedule, or respond to something changing on the map.
  • Own your data: Open source, MIT, and a database you can download any time.

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.

Connect your agent

Archipelago runs for you at app.archipelago.tools: there is nothing to host. Ask your agent:

Install Archipelago from https://app.archipelago.tools/connect/install

Or paste one line in a terminal. On Windows (PowerShell):

irm https://app.archipelago.tools/connect/install.ps1 | iex

On macOS or Linux:

curl -fsSL https://app.archipelago.tools/connect/install.sh | sh

It connects Claude Code, Codex and Cursor where it finds them, and opens your browser once to sign in to your workspace on archipelago.tools; with no account yet, choose Start a workspace there. ChatGPT and Grok Bot are connected in their own apps; the install page says how. From then on each session starts on your map, handed the open work the sessions before it left there and why each piece needs attention. For a server of your own, the same page is at /connect/install on it.

Then 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 /mcp on the same server.

Host it yourself

Only if you want to run your own server.

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.

git clone https://github.com/AlexReiner98/archipelago.git
cd archipelago
npm install
npm 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.

To connect a project to your own server, with the hooks and working rules in the project's own files, run this in its folder with the server running:

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 what 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.

Read on

Copyright 2026 Aperture Design Tools Inc. MIT License.

Reviews

No reviews yet

Be the first to review this server!