Bring your own tools into Mythos with MCP

A project brief often exists somewhere other than the chat where you are building. Your team may have a tool that exposes approved requirements, research notes or a reusable workflow. Re-entering that material by hand can leave out the detail that explains an important decision.

A custom MCP connection gives Mythos a way to use tools exposed by a compatible remote server. MCP stands for Model Context Protocol. The server describes the tools it offers; Mythos can request an available action through the connection.

The value depends on the server. Start with a source that already has a clear job and access policy, such as retrieving the approved brief for one project.

In Connectors, choose Add MCP and enter the server name, its full HTTPS endpoint, and the authentication method required by the provider. A remote MCP endpoint is different from a provider's ordinary website or API homepage. A local command or localhost address cannot serve as that remote endpoint.

After connecting, review the discovered tools and enable the ones needed for the task. A tool that reads a brief may be useful immediately; another that publishes or changes records needs a separate reason to be available.

If the server changes its tool list, use Refresh tools and review the new selection. The custom MCP documentation covers authentication and supported connection setup.

Suppose an MCP server exposes your approved workshop brief. Ask Mythos to retrieve that brief and identify the audience, schedule and booking rules before changing the site. You can then check that it found the intended material.

The next request can use those facts to build the workshop page. Keep the source's approved details separate from decisions you still need to make, such as whether visitors can reserve immediately or only request a place.

Where the provider offers actions that change external information, review those actions according to the connection's approval settings. Reading a brief and updating its approval status have different consequences, even if the same server offers both tools.

Custom MCP connections are personal. They can provide context in your Mythos chats across projects, while other members connect their own accounts. Publishing a project does not expose your personal connection to visitors.

That distinction helps when a team reviews the result. The website can use facts you approved for publication, but it should not assume every visitor can call the tools you used while building it. If the finished app needs an external integration, describe and implement that visitor flow explicitly.

Keep lasting project decisions in Knowledge, and use MCP when the task needs information or an action from the connected source. A focused first request makes it easier to see whether the connection is doing the job you added it for.