Claude Web / Mobile Connection

Official docs confirmed

Claude officially supports custom connectors using remote MCP. A connector added on the web can generally be used in Claude Mobile, but adding a brand-new server is still safest on the web.

Last verified: 2026-04-17

Screenshots are replaced automatically when you update the matching files under frontend/public/docs/apps/claude.

Before you start

Your Codebase remote MCP endpoint must be reachable from the public internet.
Your Claude account and plan must expose custom connector support.
Only connect remote MCP servers that you trust.

Connection steps

Open the Connectors settings in Claude

Start in claude.ai at Settings > Connectors, following Anthropic’s support guide. If you already have connectors configured, look for the custom integration entry point beneath the current list.

Screenshot Slot

Replace this file with your screenshot

Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.

frontend/public/docs/apps/claude/01-entry.png

Replace this slot with a screenshot showing where Connectors appears in Claude web.

Start the custom integration or remote MCP flow

This is the step where you enter the Codebase remote MCP server details. The exact label may vary, such as Add custom integration, custom connector, or remote MCP.

Screenshot Slot

Replace this file with your screenshot

Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.

frontend/public/docs/apps/claude/02-open-connect.png

Replace this slot with the remote MCP or custom integration entry screen.

Complete OAuth and approve access

Anthropic’s support docs note that custom connectors often use OAuth. Review the requested access carefully and only approve the scopes that are actually required.

Screenshot Slot

Replace this file with your screenshot

Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.

frontend/public/docs/apps/claude/03-auth.png

Replace this slot with the Codebase authorization screen shown during Claude setup.

Test it on the web and confirm mobile availability

After connecting, verify that the connector can be invoked in Claude conversations on the web. Anthropic notes that an already-added remote server may be available on mobile as well, but initial setup is best handled on the web.

Screenshot Slot

Replace this file with your screenshot

Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.

frontend/public/docs/apps/claude/04-complete.png

Replace this slot with a screenshot showing the connector available in Claude web or mobile.

Test checklist

Confirm that Codebase appears as connected in Settings > Connectors.
Confirm that the connector appears during tool approval or in the search or tools UI while chatting.
Confirm that a connector added on the web is also available on mobile.

Troubleshooting

The remote MCP server must be publicly reachable. A VPN-only or intranet-only endpoint may fail to connect.
Review any write-capable tool permissions carefully before approving them.
If you need to change connection details, you may need to remove the existing connector and add it again.

If you need to review connection state or permissions again, also check the Connected apps page.

Official sources

Get started with custom connectors using remote MCP

Anthropic’s user-facing guide to custom connector setup, security, and approval UX.

https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Build custom connectors via remote MCP servers

Reference article for the current remote MCP connector support model and product context.

https://support.claude.com/en/articles/11503834-build-custom-connectors-via-remote-mcp-servers