Introducing External URL Support
Today, we're excited to announce support for connecting MCP servers hosted by Dedalus Labs via external URL. This broadens access to our MCP marketplace.
Until now, using servers on the Dedalus MCP marketplace meant building on our Agent SDK. But through conversations with many devs across hackathons and online communities, we've heard that devs want to bring our marketplace servers into whatever stack they were already using.
Let Dedalus handle the hosting. Build with whatever you want.
MCP servers deployed on the Dedalus marketplace now come with an external URL by default. This lets you connect the server to any LLM or agent client that supports remote MCP servers, without using the Dedalus SDK.
How does this work?
External URLs are enabled by default on deployment. If you'd prefer your server not have one, you can disable this before deploying.
Once an MCP server is deployed to our marketplace, you can access it in one of two ways:
- If you have a client configured (Claude Code, Cursor, or any agents), copy the connect URL from the server's marketplace page. This link allows the server to function as any other remote MCP server.
- If you are using the Dedalus Agent SDK, you can now use either MCP server's slug or the external URL in the
mcp_serversparameter, as defined in our docs.
That's it! We're making the Dedalus marketplace a more open, interoperable way to ship MCP servers. Let Dedalus handle the server hosting, then connect from whatever agent framework or client you're building with.