ATLAS: Task Management System

Created By
cyanheadsa year ago
A Model Context Protocol (MCP) server for ATLAS, a Neo4j-powered task management system for LLM Agents - implementing a three-tier architecture (Projects, Tasks, Knowledge) to manage complex workflows. Now with Deep Research.
Overview

What is ATLAS MCP Server?

ATLAS MCP Server is a Model Context Protocol server designed to facilitate task management and organization specifically for Large Language Models (LLMs). It structures task management, enabling LLMs to handle complex tasks and maintain dependencies effectively.

How to use ATLAS MCP Server?

To use the ATLAS MCP Server, install it via npm with the command npm install atlas-mcp-server, and configure your MCP client settings to connect to the server.

Key features of ATLAS MCP Server?

  • Hierarchical task structures with parent-child relationships.
  • Robust dependency management and status tracking.
  • Supports rich content formats, including markdown and code.
  • Persistent session management for state recovery.

Use cases of ATLAS MCP Server?

  1. Managing complex workflows in AI applications.
  2. Supporting LLMs in project management and organization tasks.
  3. Facilitating collaboration among multiple LLMs through a structured protocol.

FAQ from ATLAS MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized communication protocol that allows LLMs to interact with external systems safely and efficiently.

  • How can I contribute to the project?

Contributions are welcomed! Please fork the repository on GitHub and follow the contributing guidelines provided.

  • Is there documentation available?

Yes, full documentation is available on the GitHub repository, detailing installation, features, and usage examples.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cyanheads
Star
198
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago