OpenAPI vs MCP
| OpenAPI | MCP | |
|---|---|---|
| Protocol | REST API (HTTP) | Model Context Protocol (JSON-RPC) |
| Spec file | openapi.json / openapi.yaml | Auto-discovery |
| Auth | Bearer Token / Session | Bearer Token / API Key / None |
| Best for | Integrating existing REST APIs | AI-dedicated tool servers |
| Path examples | openapi.json, spec/tools.yaml | /sse (SSE), / (Streamable HTTP) |
Adding a Tool Server
Enter connection info
| Setting | Default | Description |
|---|---|---|
| URL | — | Tool server address (e.g., https://my-tool-server.com) |
| Path | openapi.json | OpenAPI spec file path or MCP endpoint. Final request URL = {URL}/{Path} |
| Auth Type | Bearer | Bearer: fixed API Key, Session: auto-forward current user’s session token |
| API Key | — | Bearer Token value (when using Bearer auth) |
| Access control | Public | Restrict tool server exposure to specific groups/users |
Admin Global vs Personal User
| Scope | Configuration | Applies To | Protocol |
|---|---|---|---|
| Global (admin) | Admin > Settings > Tools | System-wide (can be restricted by access control) | OpenAPI + MCP |
| Personal (user) | Personal Settings > Tools | That user only | OpenAPI only |
Personal tool servers can be disabled by admin. To use personal tool servers, the API server must have correctly configured CORS.
Using Tools in Agents
Globally registered tool servers can be selected in the “Tool Connections” section of the Workspace > Agents edit screen. When tools are connected to an agent, the AI auto-picks and calls the appropriate tool based on the question.Related Pages
Agent Tool Connections
Create OpenAPI/MCP tools in the workspace and connect to agents
Pipelines
Plugin system for injecting custom logic into LLM requests/responses