ContextLayer
- DotNova/context-layer
ContextLayer is an MCP server that exposes DotNova’s knowledge graph, sessions, tasks, and documents to your agent over streamable HTTP.
About
ContextLayer (io.github.DotNova/context-layer) is a hosted Model Context Protocol server that gives Claude Code, Cursor, and similar agents durable, structured context for AI-assisted work. Instead of stuffing entire repos into prompts, you register the remote endpoint and authenticate with a Bearer token minted after sign-in at DotNova. The advertised surface spans a knowledge graph, session history, tasks, and documents—aimed at teams (and developers wearing many hats) who need one place for “what we decided” and “what is in flight.” Placement on Skillselion’s Build → Agent tooling shelf reflects install time: you add it when integrating agents into your stack. It is not a code generator or linter; it is context infrastructure you query through MCP. Intermediate setup: account, API key, and correct Authorization header format.
- Streamable HTTP remote at https://api.dotnova.io/mcp (schema version 0.1.0)
- Bearer JWT from app.dotnova.io Settings → API Keys
- Knowledge graph, sessions, tasks, and documents in one context layer
- Hosted app at https://app.dotnova.io with GitHub repo DotNova/context-layer
ContextLayer by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http context-layer https://api.dotnova.io/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Repository | DotNova/context-layer ↗ |
What it does
Connect your coding agent to shared team context—knowledge graph, sessions, tasks, and documents—so developers and small AI teams stop re-explaining the same project state every session.
Who is it for?
Best when you're already on DotNova and want centralized context wired into Claude Code or Cursor via official MCP remotes.
Skip if: Skip if you want a local-only, no-account context store or and do not want a hosted Bearer-token dependency on api.dotnova.io.
What you get
After you register the remote MCP URL and JWT, your agent can pull structured team context instead of you pasting the same background every time.
- Agent-callable access to knowledge graph, sessions, tasks, and documents
- Authenticated remote MCP connection to api.dotnova.io
By the numbers
- Server schema version 0.1.0
- Remote MCP URL: https://api.dotnova.io/mcp
- Auth: required Bearer JWT header
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
Hosted context MCP integration, not an agent skill or static SKILL.md workflow.
FAQ
Who is ContextLayer for?
Developers and small AI teams using DotNova who need shared knowledge, sessions, tasks, and documents available to coding agents through MCP.
When should I use ContextLayer?
When you are integrating agents during build (or iterating in production) and repeated context dumps are slowing you down.
How do I add ContextLayer to my agent?
Sign in at https://app.dotnova.io, copy an API token from Settings → API Keys, then add the remote MCP server https://api.dotnova.io/mcp with Authorization: Bearer <token> in your Claude Code or Cursor MCP config.