Marketplace
Over 20 preconfigured MCP connectors — knowledge from real systems straight into the chat.
The marketplace in SovrGPT bundles knowledge and action connectors. Technically they are based on the Model Context Protocol (MCP) — an open standard that lets models operate external tools.
Reachable via Sidebar → Marketplace — enabled individually per org.
What can a connector do?
- Read: GitHub issues, Notion pages, Linear tickets, Stripe customers, Atlassian issues, …
- Write: create issues, create Notion pages, update Cloudflare records, …
- Trigger: Vercel deployments, GitHub Actions, …
Exactly which actions are available is defined by the respective MCP server.
Available connectors (excerpt)
| Provider | Use cases |
|---|---|
| GitHub | Issues, PRs, code search, releases |
| Notion | Pages, databases, blocks |
| Linear | Issues, projects, teams |
| Atlassian (Jira/Confluence) | Issues, sprints, wiki pages |
| Stripe | Customers, payments, subscriptions |
| Vercel | Projects, deployments, environment variables |
| Cloudflare | DNS, Workers, R2 |
| Slack | Post messages, list channels |
| Sentry | Issues, releases, performance |
| Resend | Mail templates, sending logs |
| Supabase | Tables, RLS policies, SQL |
| PostHog | Events, funnels, feature flags |
| HubSpot | Contacts, deals, companies |
| Brevo | Mailing lists, campaigns |
| Pipedrive | Pipelines, activities |
| Plausible | Site stats, goals |
| Trello | Boards, cards |
| Microsoft Graph | Outlook mail, OneDrive, Teams |
| Discord | Channel messages, server info |
| YouTube | Video metadata, comments |
The exact list lives in lib/mcp-catalog.ts and grows with every release.
Enabling a connector
- Open
Sidebar → Marketplace. - Click the card of the connector you want.
- "Connect" → the OAuth flow or a token input dialog opens.
- The token is stored encrypted in our EU database (encrypted columns).
- The connector is immediately available in chat — as a tool in the composer.
Security
- All tokens are org-scoped. Switching orgs shows different tokens.
- Tokens are never visible client-side — only the server can decrypt them.
- If an org membership is lost, access ends immediately.
- When a connector is deactivated, the token is removed from the database (not merely soft-deleted).
Your own MCP servers
Self-hosted MCP servers (internal tools) can be added via a custom endpoint:
- Enter the URL and bearer token under
Marketplace → Custom MCP. - The server must implement the MCP spec (see modelcontextprotocol.io).
- Once activated, the tool becomes visible in all of the org's chats.
Planned for Q3/2026: SDK templates (Node, Python) for quickly building your own MCP servers.