Connectors (MCP Servers)
Connectors integrate external tools and data sources into Grengin using the Model Context Protocol (MCP). Use this page to register connector servers, enable or disable them, and test and sync their connections.
For controlling which roles, departments, and users can access a server and its individual tools, see Connector Access & Permissions.
Permissions
| Action | Permission required |
|---|---|
| View the Connectors page | View MCP Servers |
| Add, edit, delete, test, sync, or connect a server | Admin MCP Servers |
Connectors appear in the sidebar under Control Hub → MCP Connectors. If the Connectors entry isn’t visible, your account lacks the View Connectors permission.
Connector configuration is organization-wide. Access rules (configured on the Access page) reference your roles, departments, and users, but the Connectors page itself is not scoped to a single department.
Server list
The page opens on the server list, with a table view (default) and card grid view available via the view toggle. The table displays:
| Column | Description |
|---|---|
| Name | Server name |
| Transport | HTTP or stdio |
| Auth | None, API key, or OAuth2 |
| Enabled | Whether the server is active |
| Status | Current connection status |
| Tools | Number of synced tools |
The list polls for status updates every 30 seconds and pauses while a server’s detail view is open, resuming on return to the list. If no servers exist, an empty-state card prompts you to add one.
Server detail view
Click a server’s access control (shield) icon to open its detail view. The detail view shows the server name and connection status, with the following tabs:
- Access — configure default access and access rules; see Connector Access & Permissions
- Tools — manage per-tool access; see Connector Access & Permissions
- Connection — OAuth2 servers only; connect, reconnect, or disconnect
Use the back button to return to the list. Detail views are not bookmarkable — there is no direct link to a single server’s detail page; it must be reached from the list.
Add a connector server
- On the server list, click Add Server.
- Complete the fields described below.
- Click Create.
New servers are created enabled by default.
| Field | Required | Notes |
|---|---|---|
| Name | Yes | — |
| Description | No | — |
| Transport | Yes | HTTP (default) or stdio |
| URL | No | Must be a valid web address if provided |
| Auth type | Yes | None, API key, or OAuth2 |
| Connection config | Yes | JSON; defaults to {} |
| Default access | No | A free-text field, distinct from the structured access controls on the Access tab — see Connector Access & Permissions |
OAuth2 configuration
Selecting OAuth2 as the auth type adds the following fields:
| Field | Required | Notes |
|---|---|---|
| OAuth provider | Yes | Atlassian, Google, GitHub, Slack, or Custom. Presets auto-fill the authorization and token URLs, and default scopes if none are entered. |
| Auth mode | Yes | Organization (one shared connection for the org) or Per user (default; each user connects individually) |
| Client ID | Yes | — |
| Client secret | Yes for new servers | Optional when editing if you want to keep the existing secret; reveal with the show/hide toggle |
| Scopes | No | Comma-separated list |
| Auth URL | Yes, Custom provider only | — |
| Token URL | Yes, Custom provider only | — |
Edit, enable/disable, and delete servers
| Task | How |
|---|---|
| Edit a server | Click the edit icon, update fields (same form as Add Server, plus an Enabled toggle), then click Save |
| Enable or disable a server | Flip the Enabled toggle in the list; the change applies immediately |
| Delete a server | Click the delete icon (list or detail view) and confirm in the dialog, which names the server being removed |
Test and sync
| Action | Purpose |
|---|---|
| Test Connection | Checks that the server is reachable. Returns a confirmation with response time on success, or an error on failure. |
| Sync Tools | Pulls the server’s current tool catalog so access can be governed on the Tools tab. |
Connect an OAuth server
- Click Connect (from the list, or from the Connection tab in the detail view).
- Complete authorization in the provider sign-in window that opens.
- Connection status refreshes automatically once the window closes.
If the browser blocks the pop-up, Grengin falls back to a full-page redirect to complete the same flow.
Behavior differs by auth mode:
- Organization mode — the Connection tab shows connection status, expiry, and granted scopes, with Connect, Reconnect, and Disconnect controls.
- Per user mode — the Connection tab is read-only, showing only the number of connected users and the provider name. There is no control to connect or disconnect individual users.
Note: The Connect button only appears for OAuth servers that are disconnected and have an OAuth connection block. A newly created OAuth server may not show Connect in the list immediately — use the Connection tab instead.
Note: The Connection tab exists only for OAuth2 servers. Servers using None or API key auth have no Connection tab.
Reference notes
Loading and empty states
- A loading spinner displays while the server list fetches.
- An empty-state card displays when no servers exist.
- Each tab shows its own empty state when a server has no synced tools.
Related
- Connector Access & Permissions — control who can use each connector and its tools.
- Roles & Permissions — define the roles your access rules reference.
- Organization & Departments — manage the departments you can target with access rules.
- Managing Users — find and manage the users you grant access to.
- AI Engines — configure the models that use these connectors.
- How Access & Permissions Work — understand the permission model behind this page.
- Control Hub Guide home