Test your LLM App as a Claude connector test-in-claude
After deployment, your LLM App exposes an MCP server URL. Add this URL to Claude as a custom connector, then test the generated actions and widgets.
In this guide: Learn how to add your deployed app as a Claude connector, choose its sign-in behavior, and test its actions and widgets in a conversation.
For an app with public and protected actions, Claude supports deferred sign-in until it calls a protected action. An app whose actions all require authentication needs sign-in before use. See Authenticate end users with your own identity provider.
Plan requirements
Custom connectors using remote MCP are available for Free, Pro, Max, Team, and Enterprise plans. Free accounts support one custom connector. On Team and Enterprise, an authorized owner adds the connector for the organization before members connect to it. Enterprise custom roles may also grant that permission.
See Claude’s current custom connector instructions for plan and organization controls. The remote MCP endpoint must be reachable from Claude’s infrastructure, not just from your local browser.
Copy the MCP server URL
In LLM Apps:
- Open the App Detail page.
- Find Test the app.
- Under Stage environment, select Copy URL.
Add the custom connector
-
Open Customize > Connectors. For an organization-wide connector, an authorized owner instead opens Organization settings > Connectors.
-
Select Add custom connector, or Add > Custom > Web for the organization flow.
-
Enter the connector name if requested and paste the full HTTPS MCP server URL.
-
If the dialog has multiple steps, select Continue and review the detected authentication settings:
- No sign-in for a public app with authentication disabled.
- Sign in when needed for an app with public and protected actions.
- Sign in now to request sign-in before connector use.
-
For OAuth, choose a client identity method supported by your identity provider. If you use a pre-registered client, enter its details only in the connector’s OAuth settings, not in the URL or action metadata.
-
Select Add. For an organization connector, each member then selects Connect from their own connector list.
Some accounts show a single-screen dialog with Advanced settings, while others show a multi-step flow. Use the current platform instructions if your layout differs.
Allow the generated tools
Claude lists each generated action under Tool permissions on the connector page. New tools default to Needs approval, prompting you to approve every call during testing.
Keep approval prompts enabled for actions that change data or perform sensitive operations. Use Always allow only for specific trusted, low-risk actions when appropriate for your test.
Test the connector
- Start a new chat.
- Select + in the message box (or type
/), hover Connectors, and turn on the connector you added for this conversation. - Ask a question that matches one of the generated actions. For example: Show me some coffee.
Verify that:
- Claude invokes the expected action.
- The widget displays the expected sample data.
- The text response matches the widget.
- Widget controls work as expected.
For mixed authentication, first call a public action without signing in. Then call a protected action, complete the sign-in prompt, and confirm that the same request succeeds afterward. Test missing permissions and invalid input as well.
After changing the app, redeploy and repeat the affected tests. If you need to change a connector’s saved authentication settings, Claude may require you to remove and add the connector again.