Connections

Connections are what the assistant can reach on your behalf, beyond Finblade itself. The page has two tabs:

• Services (MCP) — 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 it.
• SSH machines — servers the assistant can run commands on, by name: "check disk space on web-1", "restart the worker on staging-2". See SSH machines below.

Both work in Chat AI, in workflows and with your dedicated agent.

Technically a service 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.

SSH machines

Machines your agent can run commands on. Save a server once, then ask the assistant to run commands on it by name. The login is encrypted, and only the terminal service ever uses it — the assistant never sees it.

Commands run straight away

Commands run straight away with this login, without asking you first. Save an account that has only the access the agent needs — never a root or administrator login you would not hand to a colleague.

Adding a machine

On the SSH machines tab press Add a machine:

Field	What to enter
Name	What the agent calls it, e.g. web-1 — letters, digits, dots, dashes and underscores
Description (optional)	Shown to the agent to help it pick the right machine, e.g. Production API server, Ubuntu 22.04
SSH login	As you'd type it after ssh, e.g. ubuntu@10.0.0.5
Port	Usually 22
Sign in with	Password, or Private key — paste the whole key including the BEGIN and END lines, or Load .pem file. Add the Key passphrase if the key has one

PuTTY .ppk keys aren't supported: convert the key in PuTTYgen (Conversions → Export OpenSSH key) first.

Save and test saves the machine and connects to it straight away. A machine the agent can use shows Connected; one that failed shows Error with the reason — fix the details and save again. When editing, leave the password or key blank to keep the saved one. You can save up to 20 machines.

Host keys

The first successful test remembers the server's host key — its identity. If the server later presents a different one, the machine shows Host key changed and the agent stops using it: someone may be intercepting the connection, or the server was rebuilt. If you know it was rebuilt or its SSH keys were changed, press Trust new key; otherwise leave it and find out why.

Using a machine

• In Chat AI or with your dedicated agent, just ask: the assistant sees your machines' names and descriptions, picks one and runs the command. While it does, the chat shows Running on your machine….
• In a workflow, a node that runs shell commands (the terminal tool) has a machine field: choose one of your saved machines (Manage machines opens this tab). Super Agent nodes can use your machines too, the way the chat assistant does.

A machine becomes usable once a test has succeeded, and stays usable until its host key changes; a later test that merely fails to connect doesn't lock it out. The workflow picker warns about machines that haven't passed a test yet.

Recent commands

Recent commands on a machine lists the last 50 commands run on it — the command, where it came from (Chat, Teams, Workflow, Dedicated agent or Connection test), its exit code and how long it took. Delete removes a machine; its command history is kept.

Machines are private to you: nobody else's assistant can use them. One rule to know when you share workflows: a workflow always runs with its owner's machines — including when a collaborator presses Run. Someone who has their own copy of your workflow runs it with theirs.

Do it with the API

Services: Connections — GET/POST /mcp-servers/servers/, test/, discover/ (does the server support sign-in?), and the OAuth oauth/start/ → oauth/callback/ pair.

SSH machines: SSH machines — GET/POST /ssh-machines/, {id}/test/ (with trust_new_host_key) and {id}/activity/.