Skip to main content
Most remote MCP servers authorize automatically — you add the server and approve access in your browser (see Connect a remote MCP server). Some services, though, require you to register your own OAuth app and give the Hub its Client ID and Client Secret. This page explains when that happens and how to set it up.
Your Client Secret is stored in your OS credential store — Keychain on macOS, Credential Manager on Windows — and is never sent to Viorant’s servers. The token exchange runs on your machine, so Viorant never holds an access token either. The one part that does route through Viorant is the redirect back from the service; see where Viorant sits.

​
When you need your own app

When you add a connector, the Hub detects how the service handles authorization:
  • Automatic — the service registers the Hub for you. You approve access in your browser and you’re done.
  • Bring your own app — the service requires a pre-registered OAuth app. The Hub asks for a Client ID and Client Secret that you create in that service’s developer settings.
Services that currently need your own app include Slack, HubSpot, GitHub, Asana, and Google Workspace. You can add any remote MCP server by its URL — browse the directory at mcpservers.org. The examples below cover common services that need their own app. If yours isn’t listed, search that service’s developer docs for how to create an OAuth app to get a Client ID and Secret, then add them here.

​
Why your own app?

These services don’t let an application register itself on the fly — they require an OAuth app that you own. Bringing your own app means the connection runs under your account and your permissions, not a shared Viorant identity. You control the scopes, and you can revoke access at any time from the service.

​
Add your credentials

1

Create an OAuth app in the service

Follow the guide for your service below. Each one gives you a Client ID and a Client Secret.
2

Register the callback URL

In the Space’s connector settings, use Copy callback URL and paste it into your OAuth app’s list of allowed redirect (callback) URLs. Copy it exactly.It’s a fixed https:// address and it’s the same for every connector and every Space, so you only ever register one — and because it’s a normal HTTPS URL, services that reject custom schemes or localhost accept it without complaint.
3

Paste the Client ID and Secret, then authorize

Enter them in the connector’s settings in the Space you want to use it in, then choose Authenticate. Your browser opens the service’s consent screen — approve it, and the connector’s tools load.
Client ID and Secret are held per Space, alongside that Space’s tokens. If you use the same service in two Spaces, enter them in each — or register two apps, if you want the two Spaces to appear as separate applications to the service.
If you click Connect for a service that needs its own app before adding credentials, the Hub tells you what’s missing and links back to the guide.

​
Examples

Worked guides for services that need their own OAuth app. We keep adding more — if yours isn’t here, the steps are similar: create an OAuth app in the service, copy its Client ID and Secret, and add them to the connector.

GitHub

Repositories, issues, and pull requests.

Slack

Channels, search, and workspace tools.

HubSpot

CRM records — contacts, companies, deals.

Asana

Tasks, projects, and portfolios.

Google Workspace

Gmail, Drive, and Calendar.