Publish MCP

​

Overview

After configuring and validating your tools, the final step is to publish the MCP so it can be used by agents, assistants, or external environments. To do this, click the Publish button located at the top right of the panel. It opens Manage Published Server, which is also where you come back to change or undo any of this later.

---

​

MCP Visibility

Choose who will have access to the MCP server:

• Private — Only accessible by you:
  The MCP will only be accessible from your environment or by your agents.
  Ideal for internal integrations or testing environments.
• Public — Accessible to everyone:
  Makes the MCP available to any environment that supports the MCP protocol, such as ChatGPT or other Devic instances.
  This option generates a public access URL for the server.

---

​

The address

Each published server gets its own subdomain, not a path on a shared one: https://<slug>.mcp.devic.ai The Server URL Slug field is yours to choose — it defaults to the server’s name and the dialog shows the resulting address as you type. Slugs are unique across Devic, so an already-taken one is refused rather than silently reassigned. That address becomes the endpoint from which agents or external systems can invoke the MCP tools.

---

​

Changing your mind

The same dialog carries Update Configuration, which applies a new visibility or slug, and Unpublish Server, which withdraws the public address while leaving the server itself and its tools untouched.

---

​

After publishing

Once active, the MCP:

• Is hosted on Devic’s infrastructure.
• Can be consumed by agents and assistants.
• Can be exposed to LLMs such as ChatGPT, Claude, Cursor, etc.
• Updates automatically if you modify its tools or configuration.

---