Appearance
Connections
Connections are external tools the assistant can use for you — GitHub, Linear, Notion, a company system — connected with your own login. Once a service is connected, you simply ask: "list my open GitHub issues", "add a page to the Q3 planning Notion space", and the assistant finds and uses the service. Connections work in Chat AI, in Super Agent workflow nodes and with your dedicated agent.
Technically a connection is an MCP server (Model Context Protocol) — the open standard that lets an assistant call a service's tools. Any service that exposes an MCP endpoint over https:// can be connected.
Before you connect
The assistant acts on a connected service as you, with your credentials, and may send it details from your conversation. Connect only services you trust, and only with the access they need.
Connecting a service
Press Connect a service. Pick one of the Popular services or enter a Server URL by hand (the service's MCP endpoint — public https:// addresses only), give it a Name, and choose how it authenticates:
| Authentication | When |
|---|---|
| Sign in with provider | The service supports OAuth sign-in — no token needed. Finblade detects this from the URL (Checking how this service signs in…). A permissions step lets you choose what the assistant may do; read-only access is selected by default |
| Bearer token | You paste a personal access token from the service |
| Custom header | The service expects its key in a named header |
| None | Public servers such as documentation search |
Popular services include GitHub, Notion, Linear, Atlassian (Jira & Confluence), Gmail, Google Calendar, Google Drive, Sentry, Stripe, Supabase, Hugging Face and several documentation servers (DeepWiki, Context7, Microsoft Learn, AWS Knowledge, Cloudflare Docs). Some providers do not let apps register themselves; an administrator then has to set the provider up once before anyone can sign in.
Test the connection before saving — a successful test reports Connected to name — n tools available. Tick the consent box (I understand the assistant will read and act on this service using my own login…) and Save. You can connect up to 10 services.
Managing connections
Each card shows the service's status — Connected, Not tested, Error or Needs sign-in — how many tools it provides and whether it is Enabled. From the card: Test connection, Edit (rename, change the URL or replace the token — leave blank to keep the stored token), Enable / Disable (keep the connection but stop the assistant using it), and Remove (the assistant will no longer be able to use it, and its stored token will be deleted).
Needs sign-in means the provider no longer accepts our access (the token expired or was revoked) — press Reconnect / Sign in again.
Connections are personal: each user connects their own accounts, and the assistant only ever uses your connections in your conversations.
Do it with the API
Connections: GET/POST /mcp-servers/servers/, test/, discover/ (does the server support sign-in?), and the OAuth oauth/start/ → oauth/callback/ pair.