Docs
Connect
Connect an MCP client to your workspace, save a provider API key for Qora and classification, and authorize the business services you want Qora to use.
Open a workspace
Start a trial or sign in. Credentials appear on the Connect page in the app after provisioning finishes.
Connect an MCP client
MCP server URL: https://fabric.qorbit.com/mcp. Your workspace URL is shown on Connect in the app. Review each client’s permission prompt. Do not grant unrestricted access by default.
Grok Bot is an external agent with MCP support. It is not Grok web, Grok Build, or the Grok model selected for Qora conversations.
Cloud assistants · OAuth
Claude, ChatGPT, and Grok web authenticate with OAuth. They do not use the bearer token.
- Open Claude and go to Customize → Connectors.
- Choose +, then Add custom connector.
- Paste
https://fabric.qorbit.com/mcp(or the URL on your Connect page). - Add the connector, then authenticate with your Qorbit account when prompted.
- Enable the connector for a conversation from the chat + menu → Connectors.
Anthropic’s help: Get started with custom connectors using remote MCP.
Team and Enterprise owners add connectors under Organization settings → Connectors. Members then connect individually. Remote connectors are reached from Anthropic’s infrastructure, so the MCP URL must be publicly reachable.
ChatGPT authenticates to Neural Fabric with OAuth. No bearer token.
- Open ChatGPT connector or MCP integration settings.
- Add a custom MCP connector.
- Paste the MCP server URL from your Connect page.
- Sign in with your Qorbit account when prompted.
ChatGPT’s settings labels vary by plan. If you do not see connector settings on mobile, finish this step on desktop.
Grok web uses OAuth. Grok Build CLI is a separate bearer-token client.
- Go to grok.com/connectors.
- Choose New Connector, then Custom.
- Enter the MCP server URL from your Connect page.
- Complete Qorbit authentication when asked.
IDEs and local clients · bearer token
Copy the MCP URL and bearer token from Connect. The app labels the token for Cursor, VS Code, Kimi Code, OpenClaw, and Grok Build. Replace YOUR_TOKEN in the examples. After rotation, update every copied config — the previous token stops working.
Project config: .cursor/mcp.json. Global: ~/.cursor/mcp.json. Remote HTTP servers use url and headers.
{
"mcpServers": {
"qorbit-fabric": {
"url": "https://fabric.qorbit.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Restart or reload MCP after saving. Cursor asks before running tools unless you change Run Mode.
VS Code uses servers as the root key, not mcpServers. Workspace: .vscode/mcp.json. You can also run MCP: Add Server.
{
"servers": {
"qorbit-fabric": {
"type": "http",
"url": "https://fabric.qorbit.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Trust the server when VS Code prompts.
claude mcp add --transport http qorbit-fabric --scope project https://fabric.qorbit.com/mcp --header "Authorization: Bearer YOUR_TOKEN"
If the shell does not accept a single long line, keep it as one command. Restart Claude Code after adding the server.
OpenClaw requires mcp.servers with transport: "streamable-http". Do not use Claude Desktop’s mcpServers shape.
{
"mcp": {
"servers": {
"qorbit-fabric": {
"transport": "streamable-http",
"url": "https://fabric.qorbit.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
}
Hermes uses the same streamable HTTP bearer config as other local MCP clients in Qorbit onboarding.
{
"mcp": {
"servers": {
"qorbit-fabric": {
"transport": "streamable-http",
"url": "https://fabric.qorbit.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
}
The Connect page lists Kimi Code as a bearer-token client. If this CLI is not available in your install, paste the URL and token into that client’s MCP settings instead.
kimi mcp add --transport http qorbit-fabric https://fabric.qorbit.com/mcp --header "Authorization: Bearer YOUR_TOKEN"
Grok Build is a bearer-token client. Copy the MCP URL and token from Connect and add them in Grok Build’s MCP settings. Grok web remains OAuth and does not use this token.
Grok Bot
Grok Bot is an external agent experience that supports MCP. Neural Fabric provides Qorbit’s shared business database.
It is distinct from selecting xAI / Grok as the provider that powers Qora. Grok web uses OAuth. Grok Build uses a bearer token. Those clients are not Grok Bot.
- Ask Grok Bot to add a custom MCP server named Qorbit at
https://fabric.qorbit.com/mcpusing Streamable HTTP. - Confirm the connection and complete Qorbit authorization when prompted.
- Verify the connection by asking it to list one entity.
The app also lists Windsurf, Zed, Cline, LM Studio, and Ollama as local MCP-compatible tools. Use the same URL and bearer token in that tool’s MCP configuration.
Configure a language-model provider
This setup saves the API key for the model that powers Qora. It is separate from authorizing an external AI client. Claude, ChatGPT, and Grok web use OAuth to reach Neural Fabric. Cursor, VS Code, OpenClaw, and Grok Build use a bearer token. Grok Bot is a separate MCP client. Choosing xAI / Grok here selects the model. It does not connect Grok web, Grok Build, or Grok Bot.
- Open Settings → Models & voice.
- Select Provider and enter its API Key.
- Select Show available models, then choose from Available models, or enter an exact Model ID.
- Select Test key.
- After a successful check, select Save. During onboarding, this control is Save key.
The API key authorizes access to the provider. The model selection determines which model runs.
You can select newer compatible models available to your account. Qorbit is not limited to the example versions previously listed.
If the model list cannot load, you can still enter an exact model ID.
The selected provider and model power both Qora and classification. The model must support tool calls and images.
Model-provider usage is billed separately.
| Provider | Get an API key |
|---|---|
| Anthropic / Claude | https://console.anthropic.com/settings/keys |
| OpenAI | https://platform.openai.com/api-keys |
| xAI / Grok | https://console.x.ai |
| Moonshot AI / Kimi | https://platform.kimi.ai/console/api-keys |
| DeepSeek | https://platform.deepseek.com/api_keys |
OpenAI-compatible (classification only)
This choice is separate from the five providers above. It classifies incoming information and does not power Qora. Saving it replaces the shared provider setting. Enter a public base URL and an exact model ID. Test key checks classification for this choice.
An external MCP client accesses Neural Fabric and is not the model selected here. fabric_search supports match and answer. When mode is omitted, search defaults to match. Answer generation requires explicit mode: "answer" and uses a model to compose a response from stored information. Match retrieval, fabric_list, fabric_graph, fabric_read_source, and fabric_provenance retrieve stored data and do not use this key for classification. An external agent’s conversation follows its provider’s billing. Classification that agent triggers in Qorbit uses your configured key.
Connect a business service
On Connect, authorize a business service through MCP so Qora can retrieve information you allow and add it to Neural Fabric. Featured connectors in the app include services such as Google Drive, Slack, and QuickBooks, plus custom MCP servers. Status can show Connected or Connected — Qora attach pending. Qora attaches on a later chat turn.
This authorization is not your MCP client login and not your provider API key. Connected agents do not receive access beyond the workspace and the services you authorize.