Toolfolio in your AI assistant

Search the published software catalog, explore categories, and browse curated collections from your coding assistant. Sign in with your Toolfolio account and approve read access.

Server URL

https://toolfolio.com/api/mcp

Transport: Streamable HTTP · Authentication: OAuth · Permission: toolfolio:read

Codex

Run these commands, sign in in your browser, then restart your MCP connection.

codex mcp add toolfolio --url https://toolfolio.com/api/mcp
codex mcp login toolfolio --scopes toolfolio:read --oauth-client-registration cimd

Codex setup reference

Cursor

Merge this entry into your MCP configuration in Cursor Settings → Tools & MCP. This public client is registered for Cursor’s desktop and web callbacks. No client secret is needed. Use its sign-in action when prompted.

{
  "mcpServers": {
    "toolfolio": {
      "url": "https://toolfolio.com/api/mcp",
      "auth": {
        "CLIENT_ID": "3gevgjHfQBLXj4CP",
        "scopes": [
          "toolfolio:read",
          "offline_access"
        ]
      }
    }
  }
}

Cursor setup reference

Claude Code

Add the server, then open Claude Code and use /mcp to authenticate. Current versions also support claude mcp login toolfolio.

claude mcp add --transport http toolfolio https://toolfolio.com/api/mcp

Claude Code setup reference

VS Code / GitHub Copilot

Merge this into .vscode/mcp.json and start the server. If VS Code asks for OAuth credentials, enter public client ID Mg477y8J8wyg5N7o and leave the secret empty, then sign in. Native VS Code verification is pending.

{
  "servers": {
    "toolfolio": {
      "type": "http",
      "url": "https://toolfolio.com/api/mcp"
    }
  }
}

VS Code / GitHub Copilot setup reference

Gemini CLI

Merge this into your Gemini settings.json. This public client uses a fixed local callback and needs no client secret. Run /mcp auth toolfolio to sign in; the native Gemini connection still needs verification.

{
  "mcpServers": {
    "toolfolio": {
      "httpUrl": "https://toolfolio.com/api/mcp",
      "oauth": {
        "enabled": true,
        "clientId": "XxXGZAM6Nl3O0kC3",
        "redirectUri": "http://localhost:8788/oauth/callback",
        "scopes": [
          "toolfolio:read",
          "offline_access"
        ]
      }
    }
  }
}

Gemini CLI setup reference

Windsurf / Cascade

Merge this into mcp_config.json using the editor’s MCP settings. An OAuth-capable client version is required; follow its authentication prompt.

{
  "mcpServers": {
    "toolfolio": {
      "serverUrl": "https://toolfolio.com/api/mcp"
    }
  }
}

Windsurf / Cascade setup reference

Try a search

Use Toolfolio to find design research tools.

Available tools: search_tools, get_tool, list_categories, list_collections, and get_collection. Access covers published catalog content; private collections, bookmarks, and account data are outside this integration.

Connection help

Use a current client that supports remote HTTP MCP and OAuth. For another compatible client, add the server URL, choose HTTP, and sign in. Clients limited to local stdio or legacy SSE need a compatible bridge.

A 401 response before sign-in is expected. If sign-in fails, update your client and reconnect. It must request toolfolio:read and the resource https://toolfolio.com/api/mcp. A 403 after sign-in can mean the required permission was not granted. For 429 responses, wait before retrying.

Opening the endpoint in a browser does not test an MCP connection. Use the assistant’s tools list after signing in. Website cookies and ordinary API keys are not accepted. Keep access tokens out of shared configuration.

Codex login and the pre-registered public-client OAuth flow passed live checks. Native connections in other editors still need verification. Clients requiring dynamic registration need a pre-registered client or a current CIMD-capable version; DCR remains disabled.