Development Layer · MCP

Your agent doesn't guess what context it
needs. It queries the Neural Fabric.

Connect Claude, Cursor, Copilot, Kimi Code, or OpenClaw to the Neural Fabric via MCP. Before every task, your coding agent queries shared memory (decisions, constraints, prior discoveries) across every document in your project. One call. The right context. Immediately.

01  |  ARCHITECTURE

Your docs already reference each other. Your agent just can't see it.

The same Neural Fabric. Developer data instead of business data. Architecture decisions, build notes, specs, constraints, phase results. Every document your team has written, connected by the references they share.

QORBIT Neural Fabric Sign out
Search entities◀ Hide
authentication decisions
⊕ Add Document
Entities: 94
Entity Types (9)All None
ARCHITECTURE DECISION
Auth: Token refresh flow
Decided during Q2 security review
DOC 2026-03-15-auth-architecture.md Open
Mar 15, 2026 · 8.1 KB · text/markdown
SHA-256    4e8c2a17
AuthorAlex C.
Date2026-03-15
StatusApproved
CategoryAuthentication
Related specAPI Security Spec v2
CONSTRAINT
Token expiry must not exceed 24h
Direct match
BUILD NOTE
Auth flow verified in staging
Direct match
PHASE RESULT
Load test: 10K concurrent sessions pass
Direct match
SPEC
API Security Specification v2
Direct match
DESIGN DOC
Login screen redesign: mobile + desktop
Direct match
ARCHITECTURE DECISION
Session persistence across deployments
Direct match
PLAN DOCUMENT
Q3 Release Plan
Direct match
02 | Workflow

How it changes your workflow

Without Neural Fabric
Open Composer. No prior context. Starting from zero.
Scan filenames. Guess which .md to read.
Read 5 wrong files. Find the right one eventually.
Start work without knowing decisions made last week in Claude.ai.
With Neural Fabric
Open Composer. First action: query the Neural Fabric.
Call fabric_search: one query across 80+ docs. Ranked by relevance.
Right context returned immediately. Decisions, constraints, prior discoveries.
Start work from the same shared memory as Claude.ai and every other agent.
What any agent learns, everything inherits. When an agent calls fabric_add, that knowledge is instantly available to every other agent connected to the Neural Fabric, regardless of tool, model, or time.
03 | Connect

Connect your AI tool.

Replace YOUR_TOKEN with the bearer token from your Connect page.

1
Go to Settings → Connectors
Open Claude.ai settings and navigate to Connectors.
2
Add a custom connector
Click + and enter the URL: https://fabric.qorbit.com/mcp
3
Connect and sign in
Click Connect. Sign in with your Qorbit account. All six Fabric tools appear. Set permissions to "Always allow."

No bearer token needed. Claude.ai authenticates via OAuth.

claude mcp add --transport http qorbit-fabric \
  --scope project \
  https://fabric.qorbit.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
.cursor/mcp.json
{
  "mcpServers": {
    "qorbit-fabric": {
      "url": "https://fabric.qorbit.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Restart Cursor after saving.

.vscode/mcp.json
{
  "servers": {
    "qorbit-fabric": {
      "url": "https://fabric.qorbit.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

VS Code uses "servers" as the root key, not "mcpServers".

kimi mcp add --transport http qorbit-fabric \
  https://fabric.qorbit.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
openclaw.json
{
  "mcp": {
    "servers": {
      "qorbit-fabric": {
        "url": "https://fabric.qorbit.com/mcp",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer YOUR_TOKEN" }
      }
    }
  }
}

Open Composer and try: fabric_search("what decisions have we made"). You should see ranked results from your Neural Fabric immediately.

Get your Neural Fabric URL and bearer token