Connect Notion, Jira, GitHub and more to your AI coding agent

A coding agent that can only see your repository is missing most of the context behind the work. The bug report is in Sentry, the spec is in Notion, the ticket is in Jira or Linear, and the schema lives in Supabase or Neon. Andromity can now connect to 50 of those apps directly, through each app’s own official MCP server.

One click, then a browser sign-in

Open Andromity Hub → MCP Servers → Discover in VS Code, or /settings → MCP → + Connect an app in the terminal. Pick an app and select Connect. Your browser opens the app’s own sign-in page; once you approve, the app is saved to ~/.andromity/mcp.json and connected. It is then available in every project you trust.

If you cancel the sign-in, nothing is saved, so a half-finished attempt doesn’t leave a broken server behind.

Why official servers

Every connector in the catalog is a remote MCP server run by the app itself: Notion’s at mcp.notion.com, Linear’s at mcp.linear.app, Sentry’s at mcp.sentry.dev, and so on. There is nothing to install, no community wrapper to audit, and no Andromity server in the middle. The app decides which tools exist and what your account can reach, and requests go from your machine to the app.

Before adding an app to the catalog, we checked its server for the parts that make a one-click connection work: OAuth discovery, automatic client registration, and a token method Andromity supports. Apps whose servers only accept clients they have approved in advance are left out, because the Connect button would fail at sign-in.

Apps that use a token instead

GitHub, Airtable, Render and PagerDuty don’t let new clients register for browser sign-in, but they accept an access token. For those, Connect asks for a token and links to the page where you create one. Andromity sends a test request to the app before saving anything, and keeps the token in its encrypted token store rather than in a config file.

Gmail, Google Calendar and Google Drive use your own Google OAuth client, because Google’s MCP servers are part of the Google Workspace Developer Preview and don’t support automatic registration. The Gmail guide walks through the setup.

The agent still asks

Connecting an app doesn’t change Andromity’s safety model. MCP servers don’t start in an untrusted folder. In SAFE mode the agent asks before every tool call; in TRUST mode it asks for tools that create, update, delete or push. Tool schemas load on demand, so connecting several apps doesn’t fill the context window with tool definitions up front.

What it looks like in practice

• “Read Sentry issue WEB-3F2, write a regression test that reproduces it, then fix it.”
• “Implement Linear issue ENG-312 on this branch and comment on the issue with what changed.”
• “Check the Supabase advisors for this project and fix any missing row level security policies in our migrations.”
• “Read the API conventions page in Notion and check this new endpoint against it.”

Browse the catalog

The integrations page lists every app with how it connects, and the setup guides cover what each server can do, its access controls and its limits, based on the vendor’s own documentation. Any other MCP server still works through Add MCP Server or mcp.json.

Connectors are in the VS Code extension and the terminal app. Update Andromity, open Discover, and connect the app your next task depends on.