docs
This commit is contained in:
Ishaan Jaffer
parent
1b24a0fdd7
commit
36be0044dc
@ -50,73 +50,71 @@ Navigate to the MCP Servers page and click **"+ Add New MCP Server"**.
|
||||
|
||||
|
||||
|
||||
Enter the server details — name it "DeepWiki" and set the URL to `https://mcp.deepwiki.com/mcp`.
|
||||
The create dialog opens. Enter **"DeepWiki"** as the server name.
|
||||
|
||||
|
||||
|
||||
Select **HTTP** as the transport type.
|
||||
For the transport type dropdown, select **HTTP** since DeepWiki uses the Streamable HTTP transport.
|
||||
|
||||
|
||||
|
||||
Now scroll down to the MCP Server URL field.
|
||||
|
||||
|
||||
|
||||
Fill in the MCP Server URL.
|
||||
Enter the DeepWiki MCP URL: `https://mcp.deepwiki.com/mcp`.
|
||||
|
||||
|
||||
|
||||
With the name, transport, and URL filled in, the basic server configuration is complete.
|
||||
|
||||
|
||||
|
||||
#### Step 2: Enable "Available on Public Internet"
|
||||
|
||||
Expand **Permission Management / Access Control** and toggle **"Available on Public Internet"** on. This ensures external callers (like ChatGPT) can discover this server.
|
||||
Before creating, scroll down and expand the **Permission Management / Access Control** section. This is where you control who can see this server.
|
||||
|
||||
|
||||
|
||||
Toggle **"Available on Public Internet"** on. This is the key setting — it tells LiteLLM that external callers (like ChatGPT connecting from the public internet) should be able to discover and use this server.
|
||||
|
||||
|
||||
|
||||
Click **"Create"** to save the server.
|
||||
With the toggle enabled, click **"Create"** to save the server.
|
||||
|
||||
|
||||
|
||||
The server is now created and visible in the table with a **"Public"** badge under Network Access.
|
||||
|
||||
|
||||
|
||||
#### Step 3: Connect from ChatGPT
|
||||
|
||||
Open ChatGPT and add a new MCP server. The endpoint to use is:
|
||||
|
||||
```
|
||||
<your-litellm-url>/mcp
|
||||
```
|
||||
|
||||
Click the MCP server icon in ChatGPT to add a new connection.
|
||||
Now let's verify it works. Open ChatGPT and look for the MCP server icon to add a new connection. The endpoint to use is `<your-litellm-url>/mcp`.
|
||||
|
||||
|
||||
|
||||
Select **"Add an MCP server"**.
|
||||
In the dropdown, select **"Add an MCP server"** to configure a new connection.
|
||||
|
||||
|
||||
|
||||
Enter a label for the server.
|
||||
ChatGPT asks for a server label. Give it a recognizable name like "LiteLLM".
|
||||
|
||||
|
||||
|
||||
Paste your LiteLLM MCP URL (`<your-litellm-url>/mcp`).
|
||||
Next, enter the Server URL. This should be your LiteLLM proxy's MCP endpoint — `<your-litellm-url>/mcp`.
|
||||
|
||||
|
||||
|
||||
Paste your LiteLLM URL and confirm it looks correct.
|
||||
|
||||
|
||||
|
||||
Enter your LiteLLM API key in the authentication field.
|
||||
ChatGPT also needs authentication. Enter your LiteLLM API key in the authentication field so it can connect to the proxy.
|
||||
|
||||
|
||||
|
||||
Click **"Connect"**.
|
||||
Click **"Connect"** to establish the connection.
|
||||
|
||||
|
||||
|
||||
ChatGPT now shows the available tools from your public MCP servers. Since DeepWiki is marked as public, its tools appear here.
|
||||
ChatGPT connects and shows the available tools. Since both DeepWiki and Exa are currently marked as public, ChatGPT can see tools from both servers.
|
||||
|
||||
|
||||
|
||||
@ -124,51 +122,63 @@ ChatGPT now shows the available tools from your public MCP servers. Since DeepWi
|
||||
|
||||
### Flow 2: Make an Existing Server Private (Exa)
|
||||
|
||||
Now let's restrict an existing MCP server so it's no longer visible to external callers like ChatGPT.
|
||||
Now let's do the reverse — take an existing MCP server (Exa) that's currently public and restrict it to internal access only. After this change, ChatGPT should no longer see Exa's tools.
|
||||
|
||||
#### Step 1: Edit the Server
|
||||
|
||||
Navigate to the Exa server and click to view its details.
|
||||
Go to the MCP Servers table and click on the Exa server to open its detail view.
|
||||
|
||||
|
||||
|
||||
Click **"Settings"** to edit.
|
||||
Switch to the **"Settings"** tab to access the edit form.
|
||||
|
||||
|
||||
|
||||
The edit form loads with Exa's current configuration.
|
||||
|
||||
|
||||
|
||||
#### Step 2: Toggle Off "Available on Public Internet"
|
||||
|
||||
Expand **Permission Management / Access Control**.
|
||||
Scroll down and expand the **Permission Management / Access Control** section to find the public internet toggle.
|
||||
|
||||
|
||||
|
||||
Toggle **"Available on Public Internet"** off.
|
||||
Toggle **"Available on Public Internet"** off. This will hide Exa from any caller outside your private network.
|
||||
|
||||
|
||||
|
||||
Click **"Save Changes"**.
|
||||
Click **"Save Changes"** to apply. The change takes effect immediately — no proxy restart needed.
|
||||
|
||||
|
||||
|
||||
#### Step 3: Verify in ChatGPT
|
||||
|
||||
Go back to ChatGPT and reconnect to the LiteLLM MCP server.
|
||||
Go back to ChatGPT to confirm Exa is no longer visible. You'll need to reconnect for ChatGPT to re-fetch the tool list.
|
||||
|
||||
|
||||
|
||||
Open the MCP server settings and select to add or reconnect a server.
|
||||
|
||||
|
||||
|
||||
Enter the same LiteLLM MCP URL as before.
|
||||
|
||||
|
||||
|
||||
Set the server label.
|
||||
|
||||
|
||||
|
||||
Enter your API key for authentication.
|
||||
|
||||
|
||||
|
||||
Click **"Connect"** to re-establish the connection.
|
||||
|
||||
|
||||
|
||||
Only DeepWiki tools are visible now — Exa has been successfully restricted to internal access only.
|
||||
This time, only DeepWiki's tools appear — Exa is gone. LiteLLM detected that ChatGPT is calling from a public IP and filtered out Exa since it's no longer marked as public. Internal users on your private network would still see both servers.
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user