You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For authenticated access, issue an API token from the admin panel (see link:/docs/cloud/sophia/administrator-guide#_api_token_management[API Token Management]). The admin panel can generate ready-to-paste MCP configuration snippets for each token.
25
-
26
-
The token can be passed either as a standard `Authorization: Bearer <token>` header or as a `?token=<jwt>` query parameter — useful for clients that do not support custom headers:
Sophia supports multiple *Contexts*, each representing a distinct knowledge base with its own prompt template, tag filters, and RAG options. The context is selected via the URL path.
| `cloud` | `https://sophia-api.restheart.com/mcp/cloud/` | RESTHeart Cloud managed service docs
41
22
|===
42
23
43
-
NOTE: Available contexts depend on your Sophia instance. Use the admin panel to create and manage contexts.
44
-
45
-
==== Filtering by Tag
46
-
47
-
Within a context, documents are organized by *tags*. Pass the optional `tags` parameter to the `sophia_search` tool to narrow retrieval to documents that carry the specified tags. Use `sophia_list_tags` to discover which tags are available in your context.
48
-
49
-
=== Configuration Examples
50
-
51
-
==== Claude Desktop (public context)
24
+
To connect immediately with Claude Desktop, add this to `claude_desktop_config.json`:
52
25
53
26
[source,json]
54
27
----
@@ -62,9 +35,19 @@ Within a context, documents are organized by *tags*. Pass the optional `tags` pa
62
35
}
63
36
----
64
37
65
-
==== Claude Desktop (authenticated)
38
+
=== Authenticated Access
39
+
40
+
Private knowledge bases require an API token. Issue one from the admin panel (see link:/docs/cloud/sophia/administrator-guide#_api_token_management[API Token Management]). The admin panel generates ready-to-paste MCP configuration snippets for each token.
The token can be passed as an `Authorization: Bearer <token>` header or, for clients that do not support custom headers, as a `?token=<jwt>` query parameter:
When configuring via `claude_desktop_config.json`, pass the token as a header:
48
+
=== Configuration Examples
49
+
50
+
==== Claude Desktop (authenticated via config file)
68
51
69
52
[source,json]
70
53
----
@@ -82,25 +65,11 @@ When configuring via `claude_desktop_config.json`, pass the token as a header:
82
65
}
83
66
----
84
67
85
-
When configuring via the Claude Desktop UI, custom headers are not available — use OAuth client credentials instead, which Sophia supports natively.
86
-
87
68
Add the snippet under `mcpServers` in `claude_desktop_config.json` (`~/Library/Application Support/Claude/` on macOS, `%APPDATA%\Claude\` on Windows), then restart.
When configuring via the Claude Desktop UI, custom headers are not available — use OAuth client credentials instead, which Sophia supports natively.
102
71
103
-
With authentication:
72
+
==== Cursor / VS Code (SSE transport)
104
73
105
74
[source,json]
106
75
----
@@ -121,6 +90,14 @@ Add to your project's `.mcp.json` or global MCP config.
121
90
122
91
The snippets above use link:https://www.npmjs.com/package/mcp-remote[`mcp-remote`], a small Node.js bridge that exposes the HTTP endpoint as a local `stdio` process — the format most clients expect. It requires link:https://nodejs.org[Node.js >= 18] and is downloaded automatically by `npx` on first run.
123
92
93
+
=== Selecting a Context
94
+
95
+
Each context has its own URL path. Contexts define the knowledge base scope, prompt template, and RAG options. Use the admin panel to create and manage additional contexts.
96
+
97
+
==== Filtering by Tag
98
+
99
+
Within a context, documents are organized by *tags*. Pass the optional `tags` parameter to the `sophia_search` tool to narrow retrieval to documents that carry the specified tags. Use `sophia_list_tags` to discover which tags are available.
0 commit comments