Available
AI tools & editorsClaude
A connector the customer adds to Claude, pointing at the MCP endpoint Meetext hosts for this deployment.
Explore integrationIntegrations
Every customer workspace. One deployment contract.
Bring your product into the places your customers already work. Meetext handles the different identity models, permissions and deployment lifecycles behind each one. You keep building the product.
Built once
Your AI, MCP server or API
Meet customers where they work.
14 available · Microsoft in Preview
Their workspace. Your product.
The destination directory
The workspace is theirs.
The rollout is yours.
14 available destinations. One place to find the setup, permissions and lifecycle details. Microsoft remains in Preview; each integration keeps its own prerequisites visible.
15 of 15 destinations
Available
AI tools & editorsChatGPT
A connector the customer adds in ChatGPT, pointing at the MCP endpoint Meetext hosts for this deployment.
Explore integrationAvailable
Business systemsAsana
An OAuth app whose refresh token is replaced on every use, deployed against one recorded workspace.
Explore integrationAvailable
Business systemsAtlassian
Jira and Confluence, cloud and data center, which are different products.
Explore integrationAvailable
AI tools & editorsCursor
A connector the customer's engineering team adds to Cursor, pointing at the MCP endpoint Meetext hosts for this deployment.
Explore integrationAvailable
Chat workspacesGoogle Chat
A Google Chat™ app in the customer's own space, installed from Google Workspace™ Marketplace.
Explore integrationAvailable
Business systemsHubSpot
A public app installed per portal, with scope changes that force reinstalls.
Explore integrationAvailable
Business systemsLinear
An OAuth application authorized per workspace, acting as the application rather than as the person who approved it.
Explore integrationAvailable
Business systemsNotion
A public integration authorized per workspace, over the pages the customer chooses to share and nothing else.
Explore integrationAvailable
Business systemsSalesforce
Where enterprise implementation actually lives, and the hardest destination to do honestly.
Explore integrationAvailable
Business systemsServiceNow
Instances, update sets and scoped applications, where configuration drift is the default.
Explore integrationAvailable
Chat workspacesSlack
A bot in the customer's own workspace, installed by someone who works there.
Explore integrationAvailable
AI tools & editorsVS Code
A connector added to VS Code, pointing at the MCP endpoint Meetext hosts for this deployment.
Explore integrationAvailable
Business systemsZendesk
An OAuth client authorized against the customer's own Zendesk subdomain.
Explore integrationPreview
Chat workspacesMicrosoft 365
The same shape against Microsoft Entra, where admin consent is a distinct step.
Setup & test notes
Microsoft 365 and Teams onboarding is temporarily unavailable while Meetext completes tenant provisioning.
What these words mean
- Available
- Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
- Preview
- Temporarily unavailable for new customer deployments while onboarding is completed.
- Planned
- Meetext models the destination and no adapter exists yet. Nothing to install, and nothing to sign up for.
- Bring your own
- Not a destination. Something you bring yourself, reached through a source rather than shipped to through an adapter.
Sources
Where your capabilities come from. Many, because you should not have to build anything new to start. Whichever you connect normalises into the same internal format, so every destination behaves identically.
The asymmetry is the product. Sources are open ended. Destinations are few and deep.
MCP server
AvailableStreamable HTTP, protocol versions negotiated per client.
OpenAPI document
AvailableOpenAPI 3, JSON or YAML, by URL or upload.
Repository
AvailableFastAPI, Flask, Django, Next.js and Express route discovery.
Your customer's database
AvailablePostgreSQL and SQLite. The schema is introspected into named, parameterized statements the customer approves; no query tool is ever exposed.
Bring your own
Bring your own- Internal APIs Reached as an OpenAPI document or a repository scan.
- Databases Customer-scoped PostgreSQL sources with approved read statements and credentials in Secret Manager, or through your own MCP server or API.
- Snowflake Through an MCP server or API you already run in front of it.
- Custom enterprise systems Anything you can describe as capabilities becomes deployable.
If your customers live somewhere that is not listed, tell us which and how many. That is how the next destination gets picked.
Your next customer is waiting.You build the product.
You build the product.
We take it from here.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.