Your team's knowledge, always available

Built on Context Nest

Context Nest (by PromptOwl) is a structured knowledge vault for AI tools. Rather than dumping raw files at an AI, it organizes information as interconnected documents — nodes with graph relationships, pack bundles, semantic indexing, and full version history — purpose-built for AI consumption. Teams use it to share meeting notes, project decisions, architectural context, and reference documentation directly with Claude, Cursor, and other AI tools through the Model Context Protocol (MCP).

The limitation: it's tied to your machine

The original Context Nest runs as a local stdio MCP server with vault files on your filesystem. That means it only works when your machine is on and the server process is running. Sharing the vault via OneDrive or Dropbox can extend access to teammates, but requires every person to have the right drive mapped and synced — and there's no built-in multi-user story. Writes from different people can conflict silently, and nothing links a document change to the person who made it.

What Skynest adds: cloud deployment

Skynest adapts Context Nest for serverless cloud deployment on Vercel. It replaces the local filesystem with Vercel Blob — durable, globally accessible object storage — so vault documents are always available without any local process running. Authentication is handled by GitHub OAuth 2.1: every team member signs in with their own GitHub account, and every write is committed to a private GitHub repository under that user's identity. You get a complete, accurate audit trail of who wrote what and when, using real git commits — not a synthetic log.

All 18+ Context Nest MCP tools — read_document, search, create_document, update_document, read_version, integrity checks, and more — are exposed over HTTPS. Connect once from Claude Code, Cursor, or any MCP-compatible AI tool, and your team's entire knowledge vault is immediately accessible from any machine, any time.