Overview

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Instead of copy-pasting requirements into chat, your AI assistant can directly query, create, and manage requirements in your ATOMS projects.

How it works

The MCP server runs locally on your machine as a stdio process
Your AI assistant communicates with it using the MCP protocol
The server authenticates with your ATOMS account and queries Supabase directly
All data access is gated by Row Level Security (you only see what you have access to)

Capabilities

16 tools across 4 categories

Category	Tools	Description
Entry Points	`atoms_status`, `atoms_list_projects`	Health check and project discovery
Read	`atoms_list_items`, `atoms_get_item`, `atoms_search`, `atoms_get_coverage`, `atoms_get_history`, `atoms_export_mermaid`, `atoms_trace`, `atoms_project_summary`	Query and analyze requirements
Write	`atoms_create_item`, `atoms_update_item`, `atoms_delete_item`, `atoms_link_items`, `atoms_bulk_import`, `atoms_record_test_result`	Create and modify items
Apps	5 tools with interactive UIs	Visual dashboards in supported hosts

Interactive MCP Apps

Five tools include interactive visual applications that render in capable hosts like Claude:

Coverage Heatmap : Visualize test coverage gaps across domains
Mermaid Diagram : Pan/zoom requirement hierarchy diagrams
Trace Graph : Force-directed dependency graph
Project Dashboard : Compliance overview with charts
Import Wizard : Batch import results with color coding

In hosts that don't support MCP Apps, these tools gracefully fall back to JSON responses.

Requirements

Node.js 18+
An ATOMS.tech account with at least one project
A supported AI assistant: Claude Desktop, Claude Code, Cursor, or any MCP-compatible client