Skip to content
LogoRush
LogoRush MCP

Bring logo production into your agent.

Connect Codex, Claude, or Claude Code to generate logos, manage projects, and export icon packs without leaving your workflow.

Choose your app
OAuth, no API key
About 2 minutes
01

Choose your app

LogoRush is a hosted MCP server. Pick where you want to use it, complete browser sign-in, and start a fresh conversation. No API key or local server is required.

One production endpoint

https://mcp.logoru.sh/mcp
Fastest for Codex

Connect once, use it everywhere in Codex

The desktop app, CLI, and IDE extension share the same MCP configuration on this computer.

Let Codex set itself up

Paste this into a local session with terminal access.

Connect LogoRush MCP for me using https://mcp.logoru.sh/mcp. Configure it for my user account, complete OAuth with personal access only, then start a fresh session and verify the connection by checking my LogoRush plan status and listing my projects.

Or add it in the app

1

Open Settings → MCP servers → Add server

The same menu is available from the gear in the IDE extension.

2

Enter these server details

Name

logorush

Transport

Streamable HTTP

URL

https://mcp.logoru.sh/mcp
3

Save, restart, then authenticate

Select Restart, return to the server list, and choose Authenticate. Approve your Personal account in the LogoRush browser screen.

Prefer the Codex CLI?+
Terminal
codex mcp add logorush --url https://mcp.logoru.sh/mcp
Terminal
codex mcp login logorush --scopes openid
Terminal
codex mcp list

One last step: restart Codex or the IDE extension and open a new chat after authentication so LogoRush tools load into the conversation.

Official Codex MCP instructions
02

Personal by default, team when requested

Most people should connect Personal. It uses your own projects and paid plan without forcing you to choose an organization.

Recommended

Personal account

Uses only the openid scope. Your personal projects and personal plan stay attached to your user account.

Team workspace

Adds user:org:read and asks you to choose a team. The selected team needs its own active LogoRush plan.

I want to connect a team workspace+

Codex

Terminal
codex mcp logout logorush
Terminal
codex mcp login logorush --scopes openid,user:org:read

Claude Code

Terminal
claude mcp remove --scope user logorush
Terminal
claude mcp add-json --scope user logorush \
'{"type":"http","url":"https://mcp.logoru.sh/mcp","oauth":{"scopes":"openid user:org:read"}}'
Terminal
claude mcp login logorush

If the consent screen only lists teams when you wanted Personal, clear that client's LogoRush login and reconnect with only the openid scope.

03

Run one safe check

Use a fresh chat after authentication. This request confirms the tools and the account without changing any projects.

Paste into your new chat

"Use LogoRush to check my plan status and list my logo projects."

Your client should ask permission to call LogoRush tools.

The response should include your plan status and project list.

04

Troubleshooting

Most failures come from stale client state, an unfinished browser login, or a plan attached to a different account.

LogoRush is configured but no tools appear+

Confirm the server is enabled, then restart the app or reload the editor. Start a new chat because an existing conversation may keep its old tool list.

The client says authentication is required+

Open the client's MCP or connector settings and authenticate again. For the CLIs, run `claude mcp login logorush` or `codex mcp login logorush --scopes openid`.

Only team workspaces appear on the consent screen+

The login requested `user:org:read`. Clear the stored LogoRush login and reconnect with only `openid`. Team access is separate and always requires an explicit workspace choice.

LogoRush reports that a subscription is required+

Open LogoRush and confirm that the account selected during consent has an active plan. A personal plan does not activate an organization, and an organization plan does not activate Personal.

The browser completed login but the client did not reconnect+

Return to the client and wait for its local callback to finish. In Claude Code, paste the full callback URL when prompted. Otherwise restart the client and authenticate again.

Still stuck? Email support@logoru.sh
05

Available tools

Ask naturally. Your client chooses the matching LogoRush tool and shows its input before execution.

create-project

Create a brand project

list-projects

List your projects

get-project

Read project details and assets

generate-logo

Generate a logo from a prompt

upload-asset

Add an existing image

convert-asset

Convert an asset to PNG, WebP, or ICO

vectorize-asset

Trace a raster logo into SVG

download-asset

Download an asset

set-asset-status

Mark an asset as draft or selected

delete-asset

Delete an asset

export-size-pack

Build a platform-ready icon pack

get-plan-status

Check plan limits and usage

New tools appear after you start a fresh client session.
06

Personal access token fallback

Use a token only for scripts, headless automation, or a client that cannot finish browser OAuth. Tokens grant access to your account until you revoke them.

Store tokens in an environment variable or secret manager. Never commit one to a repository. OAuth is safer for interactive clients because it avoids a permanent bearer token in configuration.

Sign in to create a token

You can read the full OAuth setup guide while signed out. Sign in only if you need a token for a script or headless client.