Mythos Docs

Custom MCP lets you connect an external service to Mythos using its remote MCP server. MCP is a standard that lets a service offer tools an AI assistant can use, such as finding a document, reading a meeting note, or running an available workflow.

Use the connection to bring your own context into a project while building. For example, you can ask Mythos to use the requirements in a company knowledge base, or turn an approved workflow’s result into an app design.

MCP connections are personal. They are available to your chats across your projects; other workspace members connect their own accounts. Publishing your project does not give the app or its visitors access to your MCP connection.

Add a custom MCP server

You need a remote MCP server URL from the service you want to connect. Use its public HTTPS address. A local command, configuration file, or address such as localhost is not a remote server URL.

Open Connectors on the Mythos Dashboard and select Add MCP.
Enter a Server name that will help you recognize the connection.
Paste the complete Server URL supplied by the provider. Keep any path at the end of the URL.
Choose the authentication method required by that server.
Complete the connection and review the tools Mythos discovers.

Choose authentication

Option	When to use it
OAuth (default)	The service lets you sign in and approve access in your browser. Select Add & authorize, then complete the provider’s authorization.
Bearer token or API key	The service gives you a token for its MCP server. Enter it in the credential field and select Add server.
No authentication	The server explicitly offers public tools without a credential. Select Add server.

The provider determines the required method. An API key for a service’s ordinary API is not necessarily a credential for its MCP server. Keep credentials in the connection form rather than pasting them into chat.

When the connection is ready, ask for a small, specific read:

Find the onboarding brief for our customer portal and summarize the requirements before we start building.

If the service offers actions that change data, describe the change you want and review Mythos’s approval request. You can review Agent approval for this connection in its settings. Always allow applies to your use of that connection; leave Ask before changes selected when you want to review changes individually.

n8n

Connect n8n to use the workflows available to you through your n8n instance. Access depends on your n8n role, the workflows made available through MCP, and the instance’s settings.

An n8n owner or administrator enables access under Settings → Instance-level MCP.
Open Connect a client in the connection details and copy the Server URL. It normally ends in /mcp-server/http.
In Mythos, select the n8n setup guidance in Add MCP and paste that full URL.
Use OAuth to sign in, or choose MCP access token and paste the value from the API key tab in n8n’s connection dialog.

For example:

Find the customer research workflow available through my n8n connection. Explain its inputs before running it for Acme.

Only workflows available to your MCP connection can be used. Connecting n8n does not start every workflow, expose all workflows in the instance, or add an n8n connection to your published app. See n8n’s MCP guide for workflow availability and account permissions.

Wispr Flow

Use Wispr Flow meeting notes as context for a build. The connection can read accessible meeting notes and related information; it cannot edit meetings or retrieve dictation history.

Wispr Flow supports MCP setup on Mac and Windows. You need Notetaker and MCP access on the account that contains your notes. Follow any Cloud Sync prompt and check organization restrictions if access is unavailable.

In Wispr Flow, open Settings → MCP → All other apps and copy Server URL.
Choose the Wispr Flow guidance in Mythos’s Add MCP form and paste the URL exactly.
Keep OAuth selected, choose Add & authorize, and sign in with Google, Apple, Microsoft, or your organization’s SSO. Wispr Flow does not support email-and-password sign-in for this authorization.

Try a prompt with a meeting name and date:

Read the notes from Tuesday’s customer portal meeting. Use the agreed requirements to outline the pages we should build.

See Wispr Flow’s connection guide if a meeting or calendar is missing.

Manage connected tools

Open the saved connection in Connectors to inspect its Tools. If the provider changes the tools it offers, use Refresh tools and review what is available before continuing.

Disconnect the server in Mythos when you no longer want to use it. Remove or revoke the provider’s authorization separately where that provider supports it.

Common questions

Does this connect a service to my published app?

No. Custom MCP gives your Mythos chats access while you work. If visitors need a live connection to the service, describe that app requirement separately.

Can the same URL work for everyone on my team?

The server URL may be shared, but each person connects with their own authorization. Their tools and data follow the provider’s access rules.

Why does a connection have no usable tools?

Check that you copied the MCP endpoint rather than the service’s homepage, selected its required authentication method, and have access to the resources it exposes. A successful sign-in alone does not mean the server offers tools to your account.