People search for “Claude add custom connector” and “Claude MCP” for the same reason: Claude gets more powerful when it can call outside tools. Connectors are the product name. MCP is often the technology underneath. Here is a practical explanation without the jargon fog.
What Claude Connectors are
Connectors are integrations Claude can use during a conversation. First-party connectors appear in Anthropic’s directory. Custom connectors let you paste a URL for a remote server you (or a product you use) operate.
Once connected and authorized, Claude can list and call tools: search, tickets, calendars, or (in AiWings’ case) generate and edit images. You stay in Claude; the connector does the specialized work.
Where MCP fits
MCP (Model Context Protocol) standardizes how AI apps discover tools, pass arguments, and handle auth with remote servers. Claude can talk to an MCP endpoint with Streamable HTTP. Your connector URL is typically something like `https://your-domain/api/mcp`.
You do not need to implement MCP yourself to use AiWings. We host the remote server. Builders use the same ideas when publishing their own servers.
Custom vs marketplace connectors
- Directory / featured connectors: brand packaging, sometimes richer UI badges.
- Custom connectors: you supply name + URL; OAuth and tools come from that server’s metadata.
- Both styles still require you to approve access before tools run for your account.
How to add a custom connector in Claude
- Open Claude.ai and go to Settings (or the customize / connectors area).
- Choose Add custom connector (or equivalent “remote MCP” entry in your client).
- Give it a clear name, e.g. AiWings.
- Paste the full HTTPS MCP URL (for AiWings, copy it from the dashboard. Prefer the primary host with no redirect).
- Click Connect and complete sign-in / authorize in the browser popup.
- Confirm the connector shows tools available. If it says “no tools,” the URL, auth, or a host redirect is usually wrong.
What “tools available” means
After a healthy connect, Claude lists tools from the server (for AiWings: things like create_reference_upload and generate_image). If Claude shows “This connector has no tools available,” the client could not successfully initialize or list tools. Often that is a bad URL, expired auth, or an HTTP redirect between www and the apex domain.
Disconnecting and privacy
You can disconnect from Claude’s Connectors UI. You should also review linked apps or OAuth grants in the product dashboard (AiWings dashboard under connected access) so tokens do not linger after you stop using a service.
When you should use a custom connector
- You want a capability Claude lacks natively (images, internal APIs, niche data).
- You prefer one chat thread for research + production work.
- You are fine authorizing a third-party service with clear credit/billing controls.
FAQ
What is a Claude Connector?
A connector is a link between Claude and an external service that exposes tools Claude may call during a chat, usually over remote MCP after you authorize access.
Is a custom connector the same as MCP?
Custom remote connectors on Claude.ai are how many people attach MCP servers. MCP is the protocol; the connector entry is the app UI to register the server URL and OAuth.
Are connectors safe?
Only connect services you trust. Review the permissions screen carefully. You can disconnect anytime in Claude’s connector settings and revoke access from the service dashboard.