Let people open your MCP App without asking Claude

• Organizations: a limited set of organizations has access, so check whether your organization has access
• Connectors: Verified directory connectors and custom connectors can have entry points. Connectors installed from a Community listing can’t.
• Users: a user needs the unified Claude experience, which combines chat and Cowork

​

Mark a tool as a global entry point

1. Add the openai/ui key
2. Set the key to an object whose entrypoints list contains a global entry
3. Keep ui.resourceUri in _meta as well

{
  "name": "open_studio",
  "title": "Example Studio",
  "description": "Open Example Studio.",
  "inputSchema": { "type": "object" },
  "_meta": {
    "ui": { "resourceUri": "ui://example/home" },
    "openai/ui": { "entrypoints": [{ "type": "global" }] }
  }
}

​

Confirm that Claude lists your app

1. Refresh the tools list for your connector
2. Open the Artifacts page in Claude on the web

​

Adapt a tool that declares entry points for another host

​

Design the view that people open from an entry point

• Arguments: make every input optional and show a useful starting state when the arguments are {}.
  • Claude can choose a value for an optional input, so don’t treat a value as proof of the user’s choice.
• Conversation: on the web, the app opens in a new conversation each time a user opens it
• Display mode: on the web, Claude shows the view full screen when the view supports fullscreen, so include fullscreen if you declare availableDisplayModes.
  • Without fullscreen, the view appears in the conversation.
• Approval: if the tool’s permission is Needs approval, Claude asks the user for approval before the view opens. If the conversation’s permission setting is Auto, Claude can open the view without asking.

​

Set the title, name, and description of the marked tool

• title: set a title, because Claude displays it with the connector’s name. Use 60 characters or fewer, and leave out Claude’s name and Anthropic’s name.
• name: don’t put two underscores in a row, two dots in a row, or a dot next to an underscore in the name. With any of these, Claude lists the app but people can’t open it from the entry point.
• description: write it for conversations too, because Claude can also call the same tool in a conversation where the connector is turned on

​

Refresh the tools list after you change an entry point

1. Go to Customize > Connectors and select your connector
2. Open the three-dot menu and click Refresh tools list

​

Conditions for showing an app on the Artifacts page

• Entry point: _meta["openai/ui"].entrypoints contains { "type": "global" }
• View: _meta.ui.resourceUri points to a ui:// resource
• Visible to Claude: _meta.ui.visibility is omitted or contains model, so that Claude can call the tool

• Remote: the connector is remote, not a local server
• Verified or custom: the connector has the Verified label in the directory, or it’s a custom connector.
  • If a user installs the connector from a Community listing, Claude doesn’t show its apps on the Artifacts page or in the sidebar, including pinned apps.
  • For what each label means, see Connector verification.

• Unified Claude experience: the user has this experience, which combines chat and Cowork.
  • If the message box offers a choice of Chat or Cowork, the account doesn’t have it.
  • On Team and Enterprise plans, an Owner or Primary Owner controls it with the Chat and Cowork unified setting in Organization settings > Capabilities.
• Connected: the user has connected the connector
• Turned on: the user hasn’t turned off the connector or set the tool to Blocked
• Allowed by the organization: on Team and Enterprise plans, the organization hasn’t set the tool or the connector to Blocked
• Organization access: the user’s organization has access to entry points

​

Check whether your organization has access to entry points

1. Refresh the tools list, then reload Claude on the web
2. If your app isn’t listed and meets all the other conditions, your organization may not have access
3. Keep your app working without an entry point, and test again later

​

Entry points that appear while you test and stay hidden for other people

• You: you keep the entry point on the connector that you added by URL
• People who install the Community listing: they have no entry point

​

Next steps

• Show your MCP App in the side panel or full screen: lay out the view for full screen and for the side panel
• Test your connector: add your server as a custom connector and open the app yourself
• Submit a connector: list your connector and its MCP App in the directory