Replit Integrations
Replit applications work with the systems and models you already use.
From Outlook and GitHub to Microsoft Fabric and your ERP, applications read and write through connectors, MCP servers and APIs of their own. Which connection sees which data we decide per project.
For teams whose application has to work with the ERP, Microsoft 365, data platforms or models the company already uses.
- Connectors
- MCP
- Microsoft Fabric
- Replit AI Integrations
- Secrets
- REST
Data where it already sits
The purchasing application reads open orders from the ERP, shows the supplier rating from Microsoft Fabric and sends queries by Outlook. A model summarises long quotes. The agent set up the connections while building; credentials sit in the secrets, and your IT has approved which accounts the agent and the application use.
What we connect
We connect what the application really needs and document every connection. Examples:
- Tools through connectorsOutlook, Slack, GitHub, Linear and other services with a single sign-in, limited to selected workspaces on the Enterprise plan.Result: the application works with your team's tools.
- Data platformsDatabricks, Snowflake and Microsoft Fabric through the data warehouse connectors, Fabric as a private preview on the Enterprise plan.Result: reports and applications read the same figures as your reporting.
- Business systems through their APIsERP, CRM or Microsoft Graph with an app registration of its own, credentials in the secrets.Result: the application writes to where the case is handled next.
- MCP both waysThe agent uses MCP servers from Atlassian, Notion or Linear, for example, and your team drives Replit from ChatGPT, Claude or Slack.Result: context from your tools flows into the agent's work.
- Models in the applicationReplit AI Integrations without keys of your own, or your account with Microsoft Foundry and OpenAI.Result: AI features run through the provider your data protection team has approved.
What a connection needs
A list of the systems the application should read or write, with one responsible person per system. Technical accounts with the least privileges needed. A decision on which model providers are allowed; on the Enterprise plan Replit AI Integrations start switched off. And a test environment of the business systems, where one exists.
What you have at the end
An overview of all connections: which system, which account, which rights, who is responsible. Credentials in the secrets and nowhere in the code. Tests that check every connection with test data. And a rule for how new connections are requested and approved.
Sound familiar? Tell us where you stand today.
ContactWhat's new.
As of: 24 October 2026
- As of 24 October 2026
Connectors with a single sign-in.
After one sign-in the agent reads and writes in services such as Outlook, Slack, GitHub or Linear. Custom connectors come as a beta with Pro and Enterprise, your own OAuth apps with the Enterprise plan.
Source: Replit Docs: Connectors - Since 14 August 2026
MCP both ways.
The agent connects to MCP servers, and Replit itself can be used from ChatGPT, Claude, Slack or other MCP clients to build, find, update and publish applications.
Source: Replit Docs: Connect via MCP - As of 2 October 2026
Replit AI Integrations start switched off on Enterprise.
Models from OpenAI, Anthropic, Google and other providers run without keys of your own and are billed to credits. In Pro and Enterprise organisations an administrator switches them on; on the Enterprise plan requests through OpenRouter go only to zero-data-retention endpoints.
Source: Replit Docs: Replit AI Integrations
Interfaces we have built.
For Kwaxx we are building a two-way interface to Abacus, at OLAO Health a REST API connects website, portal and app, and at BZ Pflege an entry in ESCADA triggers the Microsoft 365 account and enrolment in Moodle.
What IT and data protection ask about connections.
Can SharePoint or Teams be connected?
Yes, through Microsoft Graph with an app registration in your Entra ID that receives only the rights it needs. Credentials sit in the secrets, and your IT approves the registration.
Does the agent see our credentials?
No. Secrets are injected at runtime through a proxy and are not visible to the agent. Roles govern who in the workspace may see their values.
Which models may the application use?
The ones your data protection team approves. On the Enterprise plan Replit AI Integrations start switched off; alternatively the application uses your own account with Microsoft Foundry or OpenAI, under your contract.
Who owns a connection after go-live?
One person per system, recorded in the overview. They approve changes to rights and are told when a connection fails.
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.


