Official MCP connectors from the products your customers already use — plus community servers hosted on the Command+K gateway. Per-user identity, managed tokens, zero glue code.
MCP servers from the products your users already work in, wired into the Command+K gateway. Click any connector for its use cases and connect flow.
Code search, file contents, and repository browsing for your assistant.
Issues, projects, and cycles — create and query tickets from in-product chat.
Pages, databases, and search across your Notion workspace.
Search, messages, canvases, and users from your Slack workspace.
Jira issues and Confluence pages from your Atlassian site.
CRM records, marketing content, and activities from your HubSpot account.
Query and update Salesforce records via the hosted MCP server.
Conversations, contacts, and help-center articles.
Tickets and knowledge base via Freshworks' MCP server (Early Access).
Release notes, feeds, feedback, and roadmap data — hosted on Command+K.
Customers, subscriptions, invoices, and payments.
Catalog, subscriptions, transactions, and reports.
Payments, orders, customers, and catalog.
Invoices, payments, disputes, and subscriptions.
Availability, scheduling links, and booked events.
Analytics, feature flags, experiments, and session insights.
Events, funnels, retention, and dashboards. MCP requires project setup we don't automate yet.
Design files, components, and comments.
Designs, folders, and brand assets.
Sites, CMS collections, and pages.
Tasks, projects, and goals.
Boards, items, and workflows.
Tasks, lists, folders, and docs.
Issues, errors, and performance data.
Projects, deployments, and logs.
Database, auth, and edge functions.
Files, folders, and metadata.
Search, read, and link Drive files.
Tickets and help center. Zendesk hasn't shipped an official MCP server yet.
Live MCP servers that teams built and published on Command+K. Each one has a public connect page with per-user OAuth — introduce your product's tools to every AI surface that speaks MCP.
Host your MCP server on Command+K, flip on the directory listing, and your tools get a public connect page — discoverable by every team browsing this marketplace.
Host your MCPBring an API or an existing MCP server — deploy it on the gateway in minutes.
Enable the public directory listing with your name, logo, and category.
Users authorize with their own account via your public connect page.
The Command+K Marketplace is a directory of Model Context Protocol (MCP) connectors — official servers from products like Notion, Stripe, Linear, Slack, and Atlassian, plus community MCP servers hosted on the Command+K gateway. Each connector plugs into the CMD+K in-product AI assistant in one click, with per-user OAuth identity, so a product's assistant can read data and take actions in the tools its users already work with.
Connectors come in two flavors. Official connectors are MCP servers operated by the vendors themselves — Notion, Stripe, Atlassian, Sentry and the rest — reviewed and preconfigured so connecting is one click, not an integration project. Community servers are built by teams on the Command+K gateway: they get the same per-user OAuth, token management, and a public connect page, and opt into this directory to reach new users.
The Command+K Marketplace is a directory of Model Context Protocol (MCP) connectors — official servers from products like Notion, Stripe, Linear, Slack, and Atlassian, plus community MCP servers hosted on the Command+K gateway. Each connector plugs into the CMD+K in-product AI assistant in one click, with per-user OAuth identity, so a product's assistant can read data and take actions in the tools its users already work with.
An MCP connector is a server that speaks the Model Context Protocol — an open standard for giving AI assistants tools. When you connect one from the marketplace, your CMD+K assistant gains that product's tools (search, read, create, update) and calls them with the signed-in user's own identity and permissions.
Open the Command+K dashboard, go to Marketplace, and click Connect on any tile. One-click OAuth connectors open a sign-in popup; bring-your-own-app connectors ask for your OAuth client credentials once; API-key connectors ask for a token. The connector's tools are available to your widget immediately after.
Yes. Any MCP server hosted on the Command+K gateway can opt into the public directory — your server gets a public connect page, a listing with your logo and description, and per-user OAuth handled by the platform. It's how MCP builders put their tools in front of every Command+K customer.
Yes — that's the point of the gateway. Each end user authorizes a connector with their own account, so the assistant only ever sees what that user can see. Tokens are stored and refreshed by the platform; your product never touches them.
Every workspace starts with a 14-day free trial — widget, knowledge base and MCP included. No credit card. Upgrade only when you need scale.
No credit card · 14-day free trial · Questions? Book 1:1 with the founder