Skip to content

Commit 0ac0ad4

Browse files
committed
docs: fix readme
1 parent d58b18d commit 0ac0ad4

1 file changed

Lines changed: 1 addition & 9 deletions

File tree

README.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -331,21 +331,13 @@ You may find that customizing the prompt for your specific needs yields best res
331331

332332
The `deepset-mcp` package can be configured to run as a remote MCP server, allowing you to provide deepset platform access to multiple users through a centralized service. This is particularly useful for organizations that want to deploy the MCP server as a shared service or integrate it into existing infrastructure.
333333

334-
**Prerequisites**
335-
336-
- Python 3.9 or higher
337-
- `uv` package manager installed
338-
- Knowledge of FastAPI or similar web framework
339-
- OAuth authentication system (recommended)
340-
- SSL/TLS certificate for production deployment
341-
342334
**Key Requirements**
343335

344336
When running as a remote MCP server, you must configure the following:
345337

346338
1. **Transport Protocol**: Use `streamable-http` instead of the default `stdio` transport
347339
2. **Authentication**: Implement OAuth or similar authentication flow to securely handle user credentials
348-
3. **Authorization Headers**: Ensure client requests include proper `Authorization` headers with Bearer tokens
340+
3. **Authorization Headers**: Ensure client requests include proper `Authorization` headers with Bearer token for deepset access
349341
4. **Dynamic Workspace Mode**: Use `workspace_mode='dynamic'` to support multiple users with different workspaces
350342
5. **API Key Management**: Enable `get_api_key_from_auth_header` to extract deepset API keys from request headers
351343

0 commit comments

Comments
 (0)