MCP Server Connections
MCP (Model Context Protocol) connections enable agents to access tools from external services like GitHub, Linear, Notion, and more.
Recommended: Create and manage connections via the web UI at https://ui.cloud.firetiger.com/integrations/mcp
What is MCP?
The Model Context Protocol is an open standard that allows AI agents to securely connect to external tools and data sources. MCP servers expose tools that agents can invoke to perform actions like creating issues, querying databases, or sending notifications.
Installation
- Navigate to Settings > MCP Servers in the Firetiger UI
- Click Connect Server
- Either:
- Select a suggested server (GitHub, Linear, Notion, Sentry, Atlassian, PagerDuty)
- Or enter a custom Server URL for any MCP-compatible server
- Click Connect to initiate the OAuth flow
- Authorize Firetiger to access the service in the popup
The connection will be created automatically once authorization is complete.
Suggested Servers
Firetiger provides quick-connect options for popular MCP servers:
| Service | URL | Description |
|---|---|---|
| GitHub Copilot | https://api.githubcopilot.com/mcp/ |
Access issues, PRs, and repositories |
| Linear | https://mcp.linear.app/mcp |
Manage issues and project tracking |
| Notion | https://mcp.notion.com/mcp |
Access pages, databases, and docs |
| Sentry | https://mcp.sentry.dev/sse |
Monitor errors and performance |
| Atlassian | https://mcp.atlassian.com/v1/sse |
Connect Jira, Confluence, and more |
| PagerDuty | https://mcp.pagerduty.com/mcp |
Manage incidents and on-call |
What Gets Created
When you connect an MCP server, Firetiger creates a connection with:
| Field | Value |
|---|---|
connection_id |
Auto-generated unique identifier |
server_url |
The MCP server URL you connected to |
server_name |
Automatically fetched from the server metadata |
display_name |
Customizable name (defaults to server name) |
description |
Optional description for agent context |
Viewing Available Tools
After connecting, you can view the tools provided by the MCP server:
- Navigate to Settings > MCP Servers
- Click on the connection card
- View the Available Tools section
- Click Refresh Tools to update the tool list from the server
Each tool displays its name, description, and input schema.
Authentication
When connecting a server, pick the Authentication Method that matches how the MCP server authenticates clients:
| Method | When to use | What you need |
|---|---|---|
| OAuth (Dynamic) | The server supports OAuth discovery and dynamic client registration (RFC 7591). Most hosted MCP servers (GitHub, Linear, Notion, Sentry) work this way. | Nothing — you sign in through the provider’s consent page. |
| OAuth (Static) | The server requires OAuth but doesn’t support dynamic registration; you pre-registered an OAuth app in the provider’s admin console. | Client ID + client secret from the provider. You still sign in through the provider’s consent page. |
| OAuth (Client Credentials) | The provider issued machine-to-machine credentials for the client_credentials grant (RFC 6749 §4.4) — there is no user sign-in at all. Common for gateway products that front MCP servers with service accounts (e.g. Runlayer). |
Client ID + client secret, and optionally the token URL and scopes. |
| API Token | The server accepts a static bearer token (API key, PAT). | The token. |
| None | The server requires no authentication (internal or localhost servers, usually combined with a network transport). | Nothing. |
If your vendor’s instructions show a direct POST to a token endpoint with grant_type=client_credentials, use OAuth (Client Credentials) — the browser-based options will fail with errors like Invalid client_id, because the client isn’t registered for the authorization-code flow.
OAuth (Dynamic) and OAuth (Static)
Both run a browser authorization flow: Firetiger redirects you to the provider’s consent page and stores the resulting tokens. Access tokens are refreshed automatically, and you can revoke access at any time from the connected service’s settings.
OAuth (Client Credentials)
No browser step: Firetiger requests an access token directly from the token endpoint using your client ID and secret when you click Connect, verifies it against the MCP server, and automatically requests a fresh token whenever the current one expires.
- Token URL is optional — when left empty, Firetiger discovers the token endpoint from the MCP server’s OAuth metadata (RFC 8414). Set it explicitly if your provider gave you one.
- Scopes are optional, space-separated, and are re-requested on every token renewal.
- Bad credentials fail immediately at connection time, so you know right away whether the setup works.
Credential handling
For every method:
- Client secrets and tokens are write-only: they are stored encrypted and never returned by the API or UI.
- Access tokens are managed and renewed automatically (rotating refresh tokens for the browser OAuth flows; re-minting for client credentials).
Customization
Display Name
Set a descriptive display name to help identify the connection:
Production GitHub - Engineering Org
Description
The description field helps agents understand when and how to use this connection:
GitHub connection for the engineering organization.
Use for:
- Creating and managing issues in product repos
- Reviewing pull requests
- Accessing repository documentation
Managing Connections
Refresh Tools
If the MCP server adds new tools, click Refresh Tools to update the available tool list.
Delete Connection
To remove an MCP connection:
- Click on the connection card
- Click Delete Connection
- Confirm the deletion
This revokes Firetiger’s access and removes the connection. You can reconnect at any time.
Custom MCP Servers
You can connect any MCP-compatible server by entering its URL. The server must:
- Implement the MCP specification
- Support one of the authentication methods above (OAuth in any of its three flavors, a bearer token, or no auth)
- Be accessible from Firetiger’s infrastructure, or through a configured network transport for servers on private networks (available for the API Token, None, and OAuth Client Credentials methods)
Best Practices
- Use descriptive names - Help agents identify the right connection when multiple are available
- Document tool usage - Include guidance on which tools to use for different scenarios
- Limit connections - Only connect services that agents need access to
- Review permissions - Understand what access each MCP server requests before connecting