One-Click MCP Servers
A one-click MCP server is a preset for a popular hosted MCP server. It creates an MCP server connector that uses OAuth (Managed by Gateway), with the provider's endpoints and scopes already filled in. You supply at most a client ID and secret from your own app on the provider.
The Slack preset gives your agents Slack as tools, acting as the supervisor who signs in. To let people chat with one of your agents in Slack, add a Slack Agent connector instead. Its card is under Channels in the catalog.
The Presets
HYPR AgentPass™ offers these presets under MCP Servers in the catalog.
| Preset | What it reaches | What you provide |
|---|---|---|
| Atlassian | Jira, Confluence and other Atlassian products | Nothing. The gateway registers itself with Atlassian on first use |
| Cloudflare | The Cloudflare API, including Workers, DNS and zones | Nothing. The gateway registers itself with Cloudflare on first use |
| Salesforce | Salesforce objects | The Consumer Key of a Salesforce connected app. The Consumer Secret is optional |
| Slack | Slack, through a user-token app | The Client ID and Client Secret of a Slack app |
| Gmail | Gmail messages and drafts | The Client ID and Client Secret of a Google Cloud OAuth client |
| GitHub | Repositories, issues, pull requests and code search, through GitHub Copilot's hosted MCP | The Client ID and Client Secret of a GitHub OAuth app |
Add a One-Click MCP Server
- Open Add Connector.
- Expand MCP Servers.
- Click the preset's card. A dialog opens with the preset's Setup steps and its required scopes.
- Complete the Setup steps on the provider's side. See Provider Notes.
- Optional: Change the Connector name. It is part of the connector's gateway URL, and defaults to the preset's name.
- Enter the credentials the preset asks for, if any.
- Click the preset's connect button, such as Connect Atlassian. The new connector opens.
Creating a connector needs permission to edit connectors.
The dialog's scope list shows what your provider app must grant. Copy all copies the scopes, and the Configure on button for the provider opens the provider's settings. For Atlassian and Cloudflare, the scopes are managed for you. Show advanced (read-only) lists the values the preset fills in. To override one, edit the connector after you create it.
A preset that uses your own app shows a Callback URL. Register it in your app's allowed redirect list. The URL ends in the connector name, so it changes when you edit the name.
The Slack preset and the Slack Agent connector both suggest the name slack. If you add both, give one of them another name. A name that is already taken is refused with Connector already exists.
Provider Notes
Each preset's dialog lists its own setup steps. This section adds what each provider needs.
Atlassian and Cloudflare
No app is needed. On Cloudflare's consent screen, the supervisor chooses which Cloudflare permissions to grant.
Salesforce
- In Salesforce, open Setup → App Manager.
- Create a new connected app.
- Enable OAuth settings.
- Add the Callback URL from the dialog.
- Move the mcp_api and refresh_token, offline_access scopes to Selected.
- Confirm that Require PKCE is on and Enable for Device Flow is off.
- Save the connected app.
- Copy the Consumer Key into the dialog.
Slack
Click Download Slack app manifest in the dialog, and create the Slack app from it. The manifest carries the redirect URL and every user-token scope the preset needs. Then install the app to your workspace, and copy its Client ID and Client Secret from Basic Information → App Credentials.
To create the app by hand instead, add the dialog's Callback URL under OAuth & Permissions → Redirect URLs, and add every user-token scope the dialog lists.
Gmail
- In Google Cloud Console, open APIs & Services → Credentials.
- Create an OAuth client ID of type Web application.
- Add the dialog's Callback URL under Authorized redirect URIs.
- Enable the Gmail API for the project.
- Copy the Client ID and Client Secret into the dialog.
The preset asks for offline access, so the connection keeps working after its first access token expires. If you later edit the connector's OAuth scope / extra params, keep access_type=offline&prompt=consent in the value.
GitHub
- In GitHub, create a new OAuth app under your developer settings.
- Set its authorization callback URL to the dialog's Callback URL.
- Copy the Client ID.
- Generate a client secret.
- Enter both in the dialog.
The preset requests a default set of scopes. The dialog lists further recommended scopes. To request them, add them to the connector's OAuth scope / extra params after you create it.
After You Connect
The first time an agent uses the connector, its supervisor approves the provider's sign-in on mobile. From then on, the gateway stores and refreshes the token for that person. The connector's tabs work as for any MCP server connector. See MCP Servers.
To use the connector from an agent, see Connecting to a Gateway MCP Connector.
Related
- MCP Servers — build an MCP server connector from scratch
- Slack Agent — let people chat with an agent in Slack
- Controlling MCP Tool Access by Role — decide which tools each role's agents see