Quick answer: In Claude, open Customize → Connectors, add https://iconly.ai/mcp as a custom connector, and select Connect. Sign in to Iconly, review the permission, and choose Allow access. You do not need an API key, client ID, or client secret.
Claude custom connectors let a conversation use tools hosted by a remote Model Context Protocol server. Once Iconly is connected, Claude can inspect the tools available to your account, collect the right parameters, and run a design workflow from a natural-language request.
The connection is account-aware. Iconly applies your plan, token balance, brands, media, presets, and library permissions to every tool call. This makes the connector useful for real production work rather than isolated image generation.
What Claude Can Do with Iconly
The Iconly MCP server gives Claude tools for discovery, creation, refinement, and saving:
| Stage | Example Claude request | Iconly tools |
|---|---|---|
| Discover | “Check my balance and show ecommerce presets.” | check_tokens, list_presets |
| Create | “Make a centered delivery-box icon in this style.” | generate_icon, generate_vector |
| Refine | “Recenter it and slightly increase the stroke.” | crop_recenter, adjust_thickness |
| Build campaigns | “Turn this launch brief into a social post and email.” | generate_social_creative, generate_email |
| Keep approved work | “Save the final icon as ecommerce-delivery.” | save_to_library |
Generated raster icons and SVG vectors are temporary at first. That separation lets you inspect and refine a result before Claude adds it to your permanent library.
What You Need Before Connecting
- An Iconly account.
- Access to custom connectors in your Claude plan or organization.
- Enough Iconly tokens for the assets you intend to generate.
- Pop-ups enabled for the OAuth login and consent window.
The only server address you enter is:
https://iconly.ai/mcp
Do not paste an Iconly API key into Claude. The hosted Claude connector uses OAuth. Leave manual client credentials and other advanced fields empty unless your organization has a specific policy requiring them.
How to Connect Iconly MCP to Claude
Claude Pro or Max
- Open Claude and go to Customize → Connectors.
- Select +, then choose Add custom connector.
- Enter
https://iconly.ai/mcpas the remote MCP server URL. - Leave Advanced settings empty and select Add.
- Select Connect next to Iconly.
- Sign in to Iconly in the browser window.
- Review the requested permission and select Allow access.
- In a Claude conversation, open the + menu, choose Connectors, and enable Iconly.
Claude Team or Enterprise
An Owner or Primary Owner first adds Iconly under Organization settings → Connectors → Add → Custom → Web. After the organization makes the connector available, each member connects their own Iconly account under Customize → Connectors.
Per-user authorization matters: each person uses their own Iconly balance, plan, brands, and library. The organization does not need to distribute a shared Iconly password or API key.
How the Claude OAuth Flow Works
Claude discovers Iconly's authorization endpoints and registers a client dynamically. When you select Connect, Claude opens Iconly's login and consent screen. After approval, Iconly returns short-lived access credentials and a rotating refresh token through an authorization-code flow with PKCE.
In practical terms:
- Claude never receives your Iconly password.
- You can review access before granting it.
- The connection is tied to the Iconly user who approved it.
- You can revoke the connection and reconnect if a session becomes stale.
For a concise reference covering the server and its tools, see the Iconly MCP documentation.
Test the Iconly Connector in Claude
Start with read-only calls so you can verify authentication without spending tokens:
Use the Iconly connector to check my current token balance.
Then list five presets suitable for ecommerce interface icons.
Next, generate one temporary result and ask Claude not to save it:
Use Iconly to create a centered black line icon of a delivery box.
Keep generous, even padding on all sides. Show me the result,
but do not save it to my library yet.
After reviewing the result, give Claude a separate instruction to refine or save it. This produces a clear boundary between a token-consuming generation, free deterministic adjustments, and a permanent library write.
Useful Claude and Iconly Workflows
Create a consistent icon set
- Ask Claude to list presets and choose one style.
- Generate one anchor icon and review its weight, padding, color, and perspective.
- Use the approved result as a reference for the remaining subjects.
- Ask Claude to check centering and spacing before saving.
- Save only approved variants with a predictable naming system.
Build a brand-led campaign
Ask Claude to list your Iconly brands, inspect the selected profile, and identify relevant media. It can then generate a supporting icon or vector, create social formats, and produce an email from one campaign brief. Review the rendered outputs in Iconly before publishing or sending them.
Turn a successful style into a reusable template
After several results converge on the desired visual language, ask Claude to summarize the style rules for your review. It can create a reusable prompt template covering stroke weight, detail, padding, palette, background, and perspective.
Troubleshooting Claude MCP Connections
The Iconly authorization window is blank
Refresh the authorization page once. If it remains blank, close it, remove the connector, and add the Iconly MCP URL again to start a fresh request.
The login or consent window never opens
Allow pop-ups for Claude, leave the connector's Advanced settings empty, and select Connect again. A manual client ID or secret can prevent the dynamic OAuth flow from starting correctly.
Claude says the connector is unavailable
Confirm the URL is exactly https://iconly.ai/mcp and that Iconly is enabled for the current conversation. On Team or Enterprise, confirm that an Owner made the connector available to the organization.
Claude answers without calling Iconly
Use an explicit instruction such as “Use the Iconly connector to check my tokens.” Also check the conversation's connector menu to confirm Iconly is enabled.
An asset was generated but is missing from the library
Icon and vector generations remain temporary until Claude calls save_to_library. Review the result, then ask Claude to save it with a clear name.
Frequently Asked Questions
What is the Iconly MCP server URL for Claude?
Use https://iconly.ai/mcp as the remote custom connector URL.
Does connecting Claude consume Iconly tokens?
Connecting and using read-only discovery tools does not generate assets. Icon, vector, social, email, and AI editing calls follow the connected account's normal token costs.
Can I disconnect Claude from Iconly?
Yes. Remove or disconnect Iconly in Claude and revoke stale authorization when needed. A later connection starts a fresh OAuth consent flow.
Is this the same setup used by the OpenAI API?
No. Claude provides a hosted connector UI and completes OAuth for you. An OpenAI-powered backend configures the remote MCP tool in code. Follow the separate Iconly MCP with OpenAI Responses API guide.
Next step: Add https://iconly.ai/mcp in Claude, run the read-only token test, and create one temporary icon before enabling a larger workflow.
Continue reading: How to Use Iconly MCP with the OpenAI Responses API · Iconly API: Complete Guide to Icons, Social Graphics, Emails, and Vectors · Iconly Agent Skills: How AI Assistants Can Use the Design API · Iconly API for Icon Generation: Developer Guide With Code Examples · HTML to Image API: Render Social Creatives and Email Previews