MCP Connection
The MCP Connection type (external_tool internally) is NeuBird’s generic connector for any vendor that exposes a remote MCP server over HTTP. Use it for a tool that doesn’t have its own dedicated NeuBird connection type — point it at the vendor’s MCP endpoint and NeuBird calls that server’s tools directly during investigations.
NeuBird validates the connection by listing the target server’s tools. It tries <endpoint>/mcp first, then the bare endpoint, and keeps whichever one responds.
There are three ways to authenticate, shown as tabs on the connection form.
Direct Access
Section titled “Direct Access”Use this when the vendor issues a static bearer token.
| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive name for this connection |
| Description | No | An overview of what this connection is used for |
| Endpoint URL | Yes | The vendor’s MCP server URL |
| Access Token | No | A bearer token for the MCP server, if it requires one |
Use this when the vendor’s MCP server supports OAuth. Enter the Endpoint, then click through the authorization flow.
- NeuBird discovers the server’s OAuth metadata (authorization, token, and registration endpoints) from the endpoint you provide.
- If you don’t supply a Client ID, NeuBird attempts Dynamic Client Registration (DCR) against the discovered registration endpoint to obtain one automatically.
- You are redirected to the vendor to authorize access, then redirected back. NeuBird exchanges the authorization code for tokens and stores them, refreshing automatically as needed.
| Field | Required | Description |
|---|---|---|
| Endpoint | Yes | The vendor’s MCP server URL |
| Client ID | No | Only needed if the auth server does not support Dynamic Client Registration |
| Client Secret | No | Paired with Client ID, if the auth server requires a confidential client |
Note
If the auth server supports DCR, leave Client ID and Client Secret blank — NeuBird registers a client automatically during the flow.
Teleport Application
Section titled “Teleport Application”Use this when the MCP server is only reachable from inside your network. Same fields as Direct Access, plus the standard Teleport Application fields (Teleport Proxy URL, Bot Join Token, Teleport App Name).
Connection Fields
Section titled “Connection Fields”| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive name for this connection |
| Description | No | An overview of what this connection is used for |
| Endpoint URL | Yes | The vendor’s MCP server URL |
| Access Token | No | A bearer token for the MCP server (Direct Access / Teleport Application) |
| Teleport Proxy URL | Yes for Teleport Application | The Teleport proxy server URL, e.g. teleport.example.com:443 |
| Bot Join Token | Yes for Teleport Application | Machine ID bot token for tbot |
| Teleport App Name | Yes for Teleport Application | Must match the Teleport application name for this service |
For general instructions on creating and managing connections, see the Connections Overview.