Connectors are Model Context Protocol (MCP) server connections that integrate external tools into StationOne. They allow your AI to interact with services like GitHub, Google Drive, Salesforce, and many more directly from conversations.
Getting Started
- Launch StationOne and select a workspace.
- Click Connectors in the sidebar, or go to the bottom of the sidebar → + Add Connectors.
Adding a Pre-Built Connector
StationOne offers curated connectors with OAuth authentication:
- Browse connectors by category or search.
- Click Add on the desired connector.
- Follow the authentication flow:
- Most connectors use SSO or direct login.
- A webview opens showing the provider’s login/consent screen.
- Grant permissions when prompted.
- StationOne confirms successful connection.
- The connector appears in your server list as “Running”.
Available Curated Connectors
Kochava, GitHub, Google Drive, HubSpot, Salesforce, Asana, Jira, Zoom, Gong, Google Ads, Google BigQuery, TikTok Ads, StackAdapt, Amazon Ads, The Trade Desk, Revenue Cat, Sentry, LinkedIn, Zendesk, Airtable, ServiceNow, Survicate, Grafana, LINE Ads, LiveRamp, Samsung Ads, Shopify, Snap Ads, Unity Ads, Yahoo DSP, Liftoff, FreeWheel, Amplify, and more.
Adding a Custom MCP Server
Click + in the server list and choose a server type:
Smithery
Pre-packaged servers from smithery.ai.
- Enter the Server Package name.
- Enter your Smithery API Key.
- Click Save.
Stdio (Local Command)
For local scripts and tools.
- Enter the Command (e.g.,
python,node,uvx). - Enter Arguments (e.g., path to script).
- Optionally set Working Directory and Environment Variables.
- Click Save.
Streamable HTTP (Remote Endpoint)
For cloud APIs.
- Enter the URL.
- Optionally add HTTP Headers (e.g., Authorization).
- Optionally configure OAuth (Client ID, Client Secret, then click Setup OAuth).
- Click Save.
SSE (Server-Sent Events) — Deprecated
Legacy streaming protocol. Same configuration as HTTP but uses SSE transport.
OAuth Authentication
For HTTP/SSE servers requiring authentication:
- Expand the OAuth section in the server editor.
- Enter Client ID and Client Secret.
- Click Setup OAuth to open the authorization flow.
- Complete login/consent in the webview.
- Token is stored and auto-refreshed.
- Use Re-authenticate if the token expires.
Managing Connectors
Server List
Each server shows:
- Icon (from registry or favicon).
- Name and tool count.
- Status tag: Running, Failed, Disabled, etc.
Actions
- Start/Stop: Play/pause button toggles the server.
- View Tools: Search icon shows available tools.
- Context menu (right-click): Edit, Restart, Delete, View Logs, Test Tools.
- Reload All: Top button reloads all servers.
- Restart All: Top button restarts all servers.
Deprecation Notifications
When an MCP server is deprecated:
- An orange Deprecated badge appears on the server card/row.
- A message shows the sunset date and migration instructions.
- If a migration guide is available, a Migrate link appears.
- Example: Asana MCP v2 migration.
Using Connector Tools in Chat
- In the chat prompt area, click the + button.
- Go to the Tools section.
- Browse available tools from all connected servers.
- Select/deselect individual tools or toggle entire server tool groups.
- Selected tools appear as badges in the prompt area.
- The AI can use these tools when responding to your messages.