For AI agents
Give your AI agent the whole Thridy library. Claude Code, Cursor, Claude Desktop and any other client that speaks the Model Context Protocol can search 13,000+ 3D icons, pick one, and fetch a transparent PNG or a hotlinkable WebP, without leaving the conversation. Included on every paid plan.
Be on a paid plan
MCP is included on every paid plan. See the plans.
Using Claude in the browser, Desktop or mobile?
Add https://mcp.thridy.com as a custom connector and sign in to Thridy when it asks. No token, nothing to copy. Details in section 4.
Using Claude Code, Cursor or another client?
Create a token at thridy.com/account/mcp and add the server with one command or one JSON block. Section 5 has the exact text for each client.
Ask for an icon
“Find me a rocket icon and add it to the slide.” Your agent searches, picks, and fetches.
https://mcp.thridy.comStreamable HTTP, POST only, stateless. Protocol revisions 2025-06-18, 2025-03-26 and 2024-11-05 are accepted. There is no SSE stream and no session id; each request is answered in full.
Send your token as a Bearer token in the Authorization header on every request. Tokens start with thmcp_, are stored hashed on our side, and can be revoked at any time from the same page that made them.
There are two ways to get one. Claude in the browser, Desktop and mobile use OAuth: the server answers every request without a token with HTTP 401 and a WWW-Authenticate header, Claude reads it, and sends you to thridy.com to sign in and approve. Nothing to copy. Every other client takes the token from your account page in the Authorization header.
Every request needs a token, initialize included. That is deliberate: a client probing the server has to learn on its first call that sign-in is required, or it concludes the server is open and never offers to sign you in. Without a token you get HTTP 401 and this, verbatim:
MCP access needs a Thridy token from a Pro account. Create one at https://thridy.com/account/mcp, or connect through Claude and sign in when it asks.For OAuth clients the discovery documents are at https://mcp.thridy.com/.well-known/oauth-protected-resource and https://thridy.com/.well-known/oauth-authorization-server. PKCE (S256) is required, public clients only, and both Client ID Metadata Documents and dynamic registration are supported.
No token and nothing to paste. Claude signs you in to Thridy and keeps the connection itself.
Add the connector
In Claude, open Customize, then Connectors, then Add custom connector. Name it Thridy and enter https://mcp.thridy.com.
Leave the detected settings
Authentication shows Always required and the OAuth client is detected. Both are right. Add no headers.
Sign in and approve
Claude sends you to thridy.com. Sign in if you are not already, read what the connection can do, and press Connect. You are sent straight back.
Ask for an icon
“Find me a rocket icon.” Claude searches the library and fetches the PNG for you.
To disconnect, remove the connector in Claude, or revoke it at thridy.com/account/mcp, where it appears as a token named Claude connector. Revoking stops it immediately.
Replace thmcp_YOUR_TOKEN with yours. If you create the token first, the token page shows each of these with the real value in place.
One command in a terminal. Verified against claude mcp add --help.
claude mcp add --transport http thridy https://mcp.thridy.com --header "Authorization: Bearer thmcp_YOUR_TOKEN"Save as .cursor/mcp.json in a project, or ~/.cursor/mcp.json to have it everywhere.
{
"mcpServers": {
"thridy": {
"url": "https://mcp.thridy.com",
"headers": { "Authorization": "Bearer thmcp_YOUR_TOKEN" }
}
}
}Add to claude_desktop_config.json. Desktop connects to remote servers through Connectors, which have no field for a fixed header, so the token goes through the mcp-remote bridge.
{
"mcpServers": {
"thridy": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.thridy.com", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer thmcp_YOUR_TOKEN" }
}
}
}Note the header is written Authorization:${AUTH_HEADER} with no space after the colon. Cursor, Codex CLI and Claude Desktop on Windows do not escape spaces inside args, so the space lives in the environment value instead.
Any client that supports Streamable HTTP and a custom header. Here it is as plain HTTP.
curl -X POST https://mcp.thridy.com \
-H "Content-Type: application/json" \
-H "Authorization: Bearer thmcp_YOUR_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_icons","arguments":{"query":"rocket","limit":3}}}'search_iconsquery, category?, limit?Search by subject: “email”, “rocket”, “shopping cart”. Returns matching icons with their page URL, a transparent PNG download link and a WebP preview. Searching never spends anything.
get_iconid or slugEverything about one icon: a 15-minute download link, embed sizes with ready-to-hotlink WebP URLs, description, categories and page URL. Takes the short id shown on every icon page (t09002), a slug from search, or a pasted thridy.com icon URL.
list_categoriesnoneThe 29 categories with live icon counts and category page URLs. Useful for browsing before a specific search.
Results are lean JSON carrying URLs, never image bytes. Every result includes the icon’s thridy.com page and the license line, so an agent always knows where an icon came from and what it may do with it.
| Plan | MCP | Calls a minute | In flight | Downloads |
|---|---|---|---|---|
| Free | no | 0 | 1 | 5 a day on the site |
| Pro | yes | 60 | 3 | 50 a day |
| Studio | yes | 120 | 6 | 100 a day |
The three limits are separate on purpose. Calls a minute and requests in flight are retryable, and the error says when to try again, so a well-behaved agent waits rather than giving up. The download allowance is shared with the website, and a separate guard of 60 downloads a minute per account sits on top of it, which is an abuse guard rather than part of any plan.
Not in Claude. Add https://mcp.thridy.com as a custom connector and Claude signs you in to Thridy through OAuth; there is nothing to copy. For Claude Code, Cursor and other clients you create a token at thridy.com/account/mcp on any paid plan and send it as a Bearer token in the Authorization header. There is no separate API key.
Searching the library through MCP is included on every paid plan and is not available on the free plan. Searching itself never spends anything; only fetching an icon counts against your plan's daily download allowance, the same allowance the website uses.
Every request needs a token, including the first one, so a client that connects and then fails on tools is sending a token the server does not accept. If you see "MCP access needs a Thridy token from a Pro account", the token is missing, mistyped, revoked, or the account it belongs to is on the free plan. In Claude, remove the connector and add it again to sign in afresh.
Claude Desktop connects to remote servers through Custom Connectors, which handle sign-in with OAuth and have no field for a fixed Authorization header. The Thridy server authenticates with a bearer token, so on Desktop the token goes through the mcp-remote bridge, which adds the header for you. Claude Code and Cursor send headers natively and need no bridge.
Open the icon on thridy.com and copy its id, a short code like t09002 shown on the page for paid accounts. Tell your agent that id and it will call get_icon with it. An id is exact and never changes, even if the icon is renamed, so it always lands on the one you meant. Pasting the icon page URL works the same way.
Fifteen minutes, and they are personal to your token. Fetch the PNG when you get the link rather than storing it. The WebP preview URLs and the icon page URLs never expire and are safe to embed or cite.
Three, kept separate because they fail for different reasons. Downloads a day, shared with the website: 50 on Pro, 100 on Studio, and fetching an icon you already fetched today does not count again. Tool calls a minute, which is 60 on Pro and 120 on Studio, and is retryable: the error tells your agent when to try again. And requests in flight at once, 3 on Pro and 6 on Studio.
No. That address still answers and will keep answering. mcp.thridy.com is the same server on its own host, and it is what new setups should use.
Yes. Every icon is free for personal and commercial use. On a paid plan no attribution is required. When you use an icon, linking its thridy.com page is welcome so readers can find the source.
Not yet. The three tools today are read-only: search, get one icon, list categories. Generating and editing icons over MCP is planned and will draw on the same render allowance your plan carries on the website.