Connect your tools
Connect a service when it helps with the work you want to do: read a specification, send a notification, keep customer records, or store your project’s code. You can build and publish a content-first site without an integration.
The Connectors catalog shows the services available to your workspace and the setup each one needs. Start with the intended result, then choose the connection that supports it.
Where to find connectors
Open Connectors from the dashboard. In a project, choose More → Connectors to see its connections, then All connectors to browse the catalog.
The dashboard and project views use the same catalog. Connecting from inside a project can also link the saved connection to that project. A connection created from the dashboard does not automatically give every project access.
GitHub code synchronization has its own setup in More → Settings → Git.
Choose the connection for your task
A connector’s page describes its supported operations. Not every service supports the same features, account types, or use from a published app.
Connect and use a service
Open the service
Choose the connector and read its setup requirements. Check which account or resource you intend to connect.
Authorize or enter a credential
Complete the provider’s sign-in flow, or enter the requested key in the protected connection form. Select only the account and resources needed for your task.
Link the project
For a shared project-service connection, choose Use in this project or manage Linked projects. Personal connections remain personal to their owner.
For example:
Build actions and your published app
A service can help Mythos while it is building without automatically becoming part of your website. Reading a document in Build, for example, does not let a visitor read that document.
To add a service to the app, describe the visitor’s action and expected result. Mythos needs to build the app behavior and, where required, set up server access through its managed backend. Keep secret credentials out of browser code.
For a contact form, test the complete path: submit the form, find the saved enquiry, and check the notification. For an analytics integration, publish the tracking behavior and check events in the selected property. Connecting Google Analytics by itself only saves the measurement ID; it does not install tracking.
The account connected to a project is the account used by that integration. It does not automatically give every visitor a separate provider account. Explain the app’s user and recipient rules when you ask Mythos to build the flow.
Review actions and approvals
Read operations can run without asking each time. Changes, sends, and deletions ask for approval unless you have chosen Always allow for that connection.
Review the destination, affected records, and complete content before approving an action. The Always allow choice applies to every action on that connection in your Builds, including changes and deletions. Choose Ask before changes in its approval settings to return to per-action confirmation.
A provider can accept an action before its final outcome is known. An accepted email is not proof that it reached an inbox. If Mythos reports an uncertain result, inspect the provider before requesting the same action again.
Add an MCP server
MCP servers expose tools that Mythos can use while working. Choose Add MCP server for a service that supplies a compatible server endpoint.
Enter the server’s HTTPS URL and use the authentication method the server supports:
- OAuth opens the provider’s authorization flow.
- Bearer token or API key accepts the server credential in the protected setup form.
- No authentication is for a server that does not require credentials.
Provider-specific setup can limit which methods are available. For OAuth, Advanced lets you request space-separated scope names when the provider requires them; otherwise, leave the field empty to use its defaults.
After connecting, choose Discover tools and review the tools you want to enable. Discovered tools stay disabled until selected and reviewed. Adding a server does not add its tools to the published app or change the provider’s permissions.
Manage a connection
Use Linked projects to review where a project-service connection is available. Remove a project’s link when it no longer needs that service. Review the linked projects before deleting a saved connection, because the change can affect every project using it.
When OAuth access expires or is revoked, use the connector’s Reconnect action. For an API-key connection without a credential-update control, disconnect it, connect with the new key, relink the intended projects, and set up any app integration again. Telegram provides its own Update bot token action; it is not a general control for every connector.
Disconnecting Mythos does not undo messages already sent, records already changed, or other completed provider actions. Follow the service’s guide when removing app access or webhooks.
Ownership and costs
Your provider’s plan, permissions, quotas, and charges still apply. Mythos Build usage and provider usage are separate. A read can incur provider charges even when it does not require an approval card.
A repository created through GitHub stays in the selected GitHub account. A managed Supabase backend stays in your Supabase organization. See those guides for their distinct disconnect and reconnect behavior.
Enter private keys only in the protected connection or secret-input form. Never paste them into a prompt, public document, or client-side code.