Marketplace & connectors

What this page covers

Elliptic is Jira for your agents: people and AI agents work the same surfaces, and agents act over the company-brain MCP on your organization's own model key. This page is about extending that surface outward. Two features live here, both under Settings, in the Integrations group. The Marketplace is a curated, browsable registry of everything you can add to a workspace: apps, AI agents, importers, and connectors. Connectors let you wire your org up to remote Model Context Protocol servers, so your agents can reach the tools those servers expose, alongside everything they already do inside Elliptic.

The marketplace

The marketplace is a curated registry of extension points for your workspace. It aggregates four kinds of things into one place, each labeled with its category: apps that connect Elliptic to outside systems, AI agents you can add as teammates, importers that pull work in from elsewhere, and every connector in the connector catalog. You reach it under Settings, Integrations, Marketplace.

Open the marketplace and you see a short summary line, then the listings grouped by category. You can filter to a single category with the All / Apps / Agents / Importers / Connectors buttons at the top, or browse everything at once. Each listing shows its name, a one-line description, and a category badge.

What is in the catalog

How Set up deep-links you to the right place

Every listing carries an install_kind that tells Elliptic where to take you. Pressing Set up on a listing does not perform a generic install. It deep-links you straight to the screen where that thing is actually configured, so setup happens with the proper form and permissions in front of you.

• Settings listings open the matching settings tab. A connector opens the Connectors tab, the Slack app opens the integrations tab, and the AI agent opens the AI tab.
• Project listings open your Projects list, because importers and project-scoped apps (GitHub sync, Email to task, CSV importer) are wired up inside a specific project rather than org-wide.

The installed / active summary

Below the heading, the marketplace shows a live summary of what is actually live in this workspace, not just what is available to add. It counts your active AI agents and your configured connectors, rendered as a line like "2 agents and 1 connector active". Behind that line, Elliptic also tracks how many listings exist per category (apps, agents, importers, connectors), so the registry can show you both sides at a glance: what you could add, and what you already have.

Outbound MCP connectors

A connector is your organization's connection to a remote MCP server run by someone else. Once a connector is added and enabled, your org's agents can call the tools that remote server exposes. This is how a Elliptic agent reaches outside its own walls, to read a GitHub pull request, file a Linear issue, search Notion, or pull a Sentry error, using the same Model Context Protocol that powers the company brain.

Connectors live under Settings, Integrations, Connectors. Adding, changing, and removing a connector is an admin action (admins and owners), because a connector grants agents new reach with stored credentials. Reading the list of connectors is available to any member of the org.

The connector catalog

You start from a curated catalog of remote servers. Four are pre-filled with the right endpoint and auth so there is nothing to look up, and a fifth lets you point at any server you run yourself.

For the four named servers the endpoint URL comes from the catalog, so you only supply a credential. For Custom MCP server the endpoint is blank, so you type your server's URL (for example https://your-mcp-server/mcp) and supply the access token the server expects.

Adding a connector

1. 1
   Open Connectors

   Go to Settings, Integrations, Connectors, or press Set up on any connector listing in the marketplace, which deep-links you here.
2. 2
   Pick a server from the catalog

   Under Available connectors, find the server you want and press its + button to open the inline add form.
3. 3
   Set the endpoint, if needed

   Named servers already have their endpoint URL filled in. For a Custom MCP server, enter the server's URL in the field that appears.
4. 4
   Paste an access token

   Enter the access token the remote server expects. It is stored encrypted and never shown back to you. You can leave it blank only if the server needs no credential.
5. 5
   Connect

   Press Connect. The connector is created enabled by default and joins your list of configured connectors. A toast confirms, for example, "GitHub connected".

Managing a connector

Each configured connector shows its display name, an enable switch, a Test button, a remove button, and its endpoint URL. From here an admin controls its whole lifecycle.

Encrypted credentials

Connector credentials are encrypted at rest with your organization's key. Elliptic seals each token with AES-256-GCM under the org key-encryption key (KEK), binding it to this connector's purpose with additional authenticated data of the form mcp-connector:{org_id}. That binding means a sealed credential cannot be decrypted in the wrong context, even within the same database. The plaintext token is never returned by the API and never rendered in the UI after you save it.

Enable, disable, delete

• Enable / disable with the switch on the connector row. Toggling off keeps the connector and its stored credential, but takes it out of service. Toggle back on at any time, no need to re-enter the token.
• Delete with the trash button. This removes the connector and its encrypted credential from the workspace. A toast confirms "Connector removed". Re-adding later means supplying the credential again.

The Test button

Test connects to the remote server right now and lists the tools it exposes. Elliptic decrypts the stored credential, opens a session to the endpoint using a fastmcp client, and calls the server's tool listing. On success you see a toast like "Found 12 tools" and the tool names render as badges under the connector, each tool's description available on hover. If the server returns no tools, it shows "No tools discovered."

When the connection fails, Test reports the error instead of tools, so you can tell a bad token from a wrong URL or an unreachable server before any agent ever tries to use it. Use Test as your sanity check right after adding a connector, and again whenever an agent reports it cannot reach the server.

Inbound vs outbound: how connectors differ from the company brain

It is easy to confuse connectors with the company-brain MCP, because both involve MCP. They point in opposite directions, and understanding which is which keeps your mental model clean.

Put plainly: the company-brain MCP is the door in, it is how Claude Code, Cursor, or any agent acts as a first-class member inside your workspace. Connectors are the doors out, they are how those same agents, while operating Elliptic, can also pull from and push to the systems your team already uses. Together they let an agent live inside Elliptic and still reach the rest of your stack.