English Français العربية

NASC — Networked AI Session Continuity

Official registry AI and agents

Shared memory across AI dev tools: each session hands its context to the next, not starting cold.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http nasc-networked-ai-session-continuity 'https://nasc.archerionlabs.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "nasc-networked-ai-session-continuity": {
            "type": "http",
            "url": "https://nasc.archerionlabs.com/mcp"
        }
    }
}

Frequently asked questions

What is NASC — Networked AI Session Continuity?

Shared memory across AI dev tools: each session hands its context to the next, not starting cold.

How do I install NASC — Networked AI Session Continuity?

It runs as a remote server. In Claude Code: claude mcp add --transport http nasc-networked-ai-session-continuity 'https://nasc.archerionlabs.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does NASC — Networked AI Session Continuity need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains NASC — Networked AI Session Continuity?

It is published by com.archerionlabs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.