Connect to AppWizzy with MCP

Applies to: AppWizzy Projects MCP

AppWizzy Projects MCP connects a compatible AI client to your AppWizzy projects. The client can inspect projects and create an External Code project.

The customer endpoint is:

https://appwizzy.com/mcp/projects

What the connection can do

AppWizzy requests only the scopes that the authorized tools need:

Scope Permission
projects:read List your projects and eligible machine sizes, and read project creation status
projects:create Validate and create projects, reserve required credits, and prepare ZIP uploads

Review the requested scopes on the AppWizzy authorization screen. Then decide whether to allow access.

The create scope can use your AppWizzy credit balance when it creates a project.

create_project automatically starts AI setup and launch for empty projects and projects imported from GitHub or ZIP. The hosting quote excludes AI usage. AppWizzy charges AI usage separately in AppWizzy credits. The final AI cost depends on actual usage and is unknown before creation.

Before creation, your agent must show the machine, code source, visibility, first-period hosting credit reservation, and ongoing daily hosting rate. It must also explain the automatic AI work and its separate usage charges.

Give explicit consent to both hosting costs and additional AI usage charges before the agent calls create_project. If you refuse, the agent must not create the project.

OAuth access permission and consent to a specific paid creation are separate decisions.

Connect from Codex CLI

This guide uses the registered Codex OAuth client. Command options were reviewed with Codex CLI 0.159.2.

Check your installed version:

codex --version

Use callback port 1455 for this registered client. The commands below set this port for each authorization attempt.

Add the remote MCP server for AppWizzy Projects MCP.

codex -c mcp_oauth_callback_port=1455 mcp add appwizzy_projects --url https://appwizzy.com/mcp/projects --oauth-client-id appwizzy-codex-cli

Start the OAuth login if Codex does not prompt you automatically.

codex -c mcp_oauth_callback_port=1455 mcp login --scopes projects:read,projects:create appwizzy_projects

Your browser opens the AppWizzy authorization page. Sign in to AppWizzy.

Review the client and its requested permissions. Select Allow access only if you started the connection.

Verify the connection.

codex mcp list

In Codex, use /mcp to view the active MCP server and available tools.

Use the same connection in Codex clients

Codex CLI and the Codex IDE extension share the MCP server configuration. Add the MCP server with the CLI commands above.

Authorize the MCP server. Refresh or restart the other Codex client if it does not show the connection.

Codex supports OAuth for remote Streamable HTTP MCP servers. See the official Codex MCP documentation for all Codex configuration options.

Available AppWizzy tools

The authorized scopes determine which tools the client shows.

Read tools

  • list_projects lists projects that the authorized AppWizzy user owns.
  • list_project_machines lists machine sizes that currently support MCP External Code creation. The result includes credit rates.
  • get_project_status returns the status of a project creation operation that the user owns.

Creation tools

  • check_project_creation validates the requested name, description, machine size, visibility, account limits, and AppWizzy credit balance.
  • check_project_creation returns a short-lived quote but does not create a project.
  • prepare_project_archive_upload prepares a one-time upload for a ZIP archive.
  • create_project creates the project from a validated quote.
  • create_project can also import a GitHub repository or an uploaded ZIP archive.

The current creation process uses the MCP-enabled External Code template. It creates a development environment with optional code import.

Connect GitHub in AppWizzy before any GitHub import. This requirement applies to public and private repositories.

Choose an empty project only when you intend to start without imported code.

The ready status means the environment and required code import are ready. It does not verify production application health.

The returned project_url opens the AppWizzy project page. It is not the deployed application URL.

See Create Projects with AppWizzy MCP for the complete workflow.

Authentication and security

AppWizzy Projects MCP uses an OAuth authorization-code flow with PKCE.

  • Codex does not receive your AppWizzy password.
  • AppWizzy associates the connection with the signed-in AppWizzy user.
  • The MCP server enforces the scopes that you approve during authorization.
  • The MCP server returns only projects that the authorized user owns.
  • Project creation follows AppWizzy plan, visibility, project limit, machine-size eligibility, and credit rules.

The connected Codex client can complete every action in the approved scopes. Do not authorize a connection that you did not start.

Disconnect

Remove the stored Codex MCP authorization.

codex mcp logout appwizzy_projects

Remove the MCP server definition.

codex mcp remove appwizzy_projects

To reconnect, add the MCP server again. Then complete OAuth again.

Troubleshooting connection problems

Authentication required

Run the OAuth login command above again. Complete the AppWizzy authorization process.

Invalid client or redirect URI

Use appwizzy-codex-cli as the OAuth client ID. Use callback port 1455 when you add or authorize this server.

Do not replace the redirect URI with another address. The redirect must match the registered client.

If the error continues, send your Codex version and the displayed callback URL to AppWizzy support.

Do not send the complete authorization URL, callback query, authorization code, or tokens.

Callback port unavailable

Close another process that uses port 1455. Then repeat the OAuth login command.

Insufficient scope

The connection does not have the scope for the requested action. Log out and reconnect.

Review the required scope. Approve it only if you need its actions.

Rate limit exceeded

The MCP server accepts up to 120 authenticated requests per minute for one connection. Wait for the Retry-After period before you retry.