Connectors

Chief finishes more tasks when it can reach the tools around your code: pull requests, issues, errors, deploys, databases, designs, messages, documents and payments. Connectors shows, for each computer, which of these Chief can use, and helps you connect the rest.

Open it from the Chief tab (the Connectors row under Ask Chief) or from Settings › Chief › Connectors. Both need New Melta on (Settings › New Melta). Each computer's connectors come in four groups: Code and work, Talk, Business and Everything else.

What each connector needs

Code and work

• GitHub gives pull requests. It needs the GitHub CLI (gh) on the computer, logged in. Chief opens, checks and merges pull requests with that login. The detail screen shows the account, what its login may do, and the repos Chief can open pull requests in.
• Linear gives issues. It needs Linear's official MCP server (mcp.linear.app), signed in to in the browser.
• Jira gives issues and sprints. It needs Atlassian's remote MCP server (mcp.atlassian.com), signed in to with your Atlassian account. It reaches Confluence too.
• Sentry gives errors. It needs Sentry's official MCP server (mcp.sentry.dev), signed in to in the browser.
• Vercel gives deploys and logs. It needs Vercel's MCP server (mcp.vercel.com), signed in to in the browser.
• Supabase gives database and auth. It needs Supabase's MCP server (mcp.supabase.com), signed in to in the browser.
• Postgres gives your database. It needs your database's connection string (postgres://user:password@host:5432/db), pasted in Melta. Chief runs it with DBHub, which needs Node.js on the computer. Use a read-only database user if you can: Chief can run any query that user may.
• Figma gives designs. It needs Figma's remote MCP server (mcp.figma.com), signed in to in the browser.

Talk

• Slack gives messages. Its MCP server signs in through a Slack app your workspace admin approved. Connect opens Slack's guide to set it up on the computer.
• Discord gives messages. It needs a bot token: make an application at discord.com/developers, add a bot, invite it to your server and paste its token in Melta. Discord has no official MCP server, so Chief runs the community mcp-discord server, which needs Node.js on the computer.

Business

• Notion gives pages and databases. It needs Notion's official MCP server (mcp.notion.com), signed in to in the browser.
• Google Workspace gives Gmail, Calendar and Drive. Google's own MCP servers are in a Developer Preview that needs your own Google Cloud OAuth client, so Connect opens Google's guide instead of a one-tap sign-in. A Gmail, Calendar or Drive connector you already added to Claude Code counts too.
• Stripe gives payments and customers. It needs Stripe's official MCP server (mcp.stripe.com), signed in to in the browser.

Everything else

• Composio gives 500+ apps through one sign-in. It needs Composio Connect (connect.composio.dev), signed in to with your Composio account; then link the apps you want in Composio. Your requests to those apps go through Composio's service, not straight from your computer. To see which apps are linked, add a Composio API key (app.composio.dev › Settings › API keys) on Composio's detail screen. Melta sees app names and whether each is linked, nothing else.

Connecting

Tap Connect (or Reconnect when a sign-in ran out). What happens depends on the connector:

• GitHub: Melta opens a terminal on the computer and runs gh auth login --web, which shows a one-time code. Open github.com/login/device on your phone, sign in and type the code.
• Linear, Jira, Sentry, Vercel, Supabase, Figma, Notion, Stripe and Composio: Melta opens a terminal on the computer. Claude Code adds the server for all your projects and prints a sign-in link. Open it, sign in, then paste the address your browser ends on back into the terminal. Without Claude Code, Codex adds it instead.
• Postgres and Discord: a sheet asks for the connection string or the bot token. It goes to the computer over your SSH connection, and Chief adds the server to Claude Code and Codex there.
• Slack and Google Workspace: Melta opens the service's guide.

Come back to Connectors and it checks again. Test on a detail screen makes a real call (GitHub) or checks again (the others). Disconnect signs the computer's gh out (GitHub), or removes the connector from Claude Code and Codex on that computer, with its key, after you confirm. A connector that comes from your claude.ai account or a plugin, or a server you added yourself, stays: remove it there.

Where your tokens and keys are

Tokens and keys stay on your computer. Melta never stores them. Sign-ins stay with gh, Claude Code and Codex. A Postgres connection string, a Discord bot token or a Composio API key goes into the macOS keychain, Linux's keyring (secret-tool), or, without either, a file only you can read; Chief's own sessions are not allowed to read it. When Claude Code or Codex starts the Postgres or Discord server, melta-chief mcp-run hands it the key, so it is not written into Claude Code's or Codex's settings either.

The phone reads each computer over its own SSH connection with melta-chief connectors, which only reports whether a connector works and which account it uses. Nothing goes through Melta's servers.

Common questions

A row says "Update Chief on this computer"

Connectors need melta-chief 0.1.18 or later. Tap Update Chief, or run the install command again with --update.

I only see GitHub, Slack, Linear and Sentry

The others need melta-chief 0.1.25 or later. Tap Update Chief under the list.

A row says "Can't check: computer offline"

The phone can't reach that computer over SSH right now. Tap Reconnect, or see Troubleshooting.

Can I check from the computer itself?

Yes: melta-chief connectors lists them all, melta-chief connectors connect linear prints the command that connects one, and melta-chief connectors key postgres asks for a connection string without showing it.

Can I talk to Chief from Telegram?

Yes, that is a door rather than a connector: see Doors.