Guide / Claude Code
Claude Code MCP setup: claude mcp add for Resilis
Connect Claude Code to Resilis so it can request supported deployment and cloud operations for the organization you authorize.
Before you start
Install Claude Code and sign in to a Resilis account with access to the organization you want to use. Keep your application source in a local workspace that Claude Code can access. Connecting to the Resilis MCP server does not require a paid plan; resource operations still require the relevant permissions and billing.
Add the Resilis MCP server
In a terminal, register the remote HTTP server:
Terminal
claude mcp add --transport http resilis https://mcp.resilis.io Sign in and review access
Start the OAuth sign-in from Claude Code. You can run the login command in a terminal or open the MCP panel in a Claude Code session. Sign in to Resilis, select an organization if prompted, and review the requested access before approving it.
Terminal
claude mcp login resilis Check the connection
Run these commands from your application directory to check the configured server and its connection status. Resilis should use https://mcp.resilis.io and show Connected rather than Needs authentication or Failed to connect. In a Claude Code session, /mcp shows the connected server and its available tools.
Terminal
claude mcp list
claude mcp get resilis What you can do once connected
Resilis exposes the following MCP tools for the organization you authorize. Availability depends on account permissions, plan limits, and the selected resource and compute target. Review the requested action before approving a change.
Deploy a workspace
Deploy the reviewed commit from this workspace to my development environment. Confirm the project, compute target, and configuration with me before starting. Inspect a deployment
Show the deployment status for my development app and the last 50 build or runtime log entries. Do not change any resources. Create a database
Create a private PostgreSQL database in the project and environment I choose, after I approve the capacity and configuration. Prepare a rollback
Prepare an app rollback to the historical deployment I select. Explain that it does not restore database data, then ask for my approval. - Deploy a reviewed local workspace with workspaces.deploy; the client handles the local Git steps before Resilis verifies the uploaded commit.
- Check deployment status with deployments.get and inspect bounded build or runtime logs with logs.build and logs.runtime.
- Create a managed PostgreSQL or MySQL database with databases.create.
- Request an app rollback to an authorized historical deployment with deployments.rollback. App rollback does not restore data or reverse database migrations.
Deploy your app from Claude Code
After connecting, follow the getting-started documentation to deploy a reviewed workspace. Git is required; GitHub is unnecessary for this route. Source is transferred to private Resilis-hosted Git. Review the files, secrets, build settings, and environment variables before authorizing deployment to the chosen project, environment, and compute target. Once it finishes, check the deployment status, logs, and running app. Start with a request like this:
Prompt
Inspect this application workspace and prepare a Resilis deployment plan. Ask me which project, environment, and compute target to use. Show the detected build settings and required environment variables so I can review them before the deployment starts. Troubleshoot OAuth and sign-in
If the browser does not open, copy the authorization URL printed in the terminal and open it manually. If the shell asks for a callback URL, follow that prompt in the terminal rather than sharing the URL with your agent.
If the browser signs in to the wrong Resilis account, sign out of that browser session and sign in with the intended account before authorizing again. For the wrong organization, check that the account is a member of the intended organization and select it when prompted during authorization.
If authorization has expired or been revoked, clear the stored credentials with claude mcp logout resilis, then run claude mcp login resilis to authorize again. Use the same reset if you need to replace an existing grant after correcting the account or organization. Signing in again does not restore organization membership or permissions that were removed.
Reset authorization
claude mcp logout resilis
claude mcp login resilis Troubleshoot a server that is not listed
Run claude mcp list from your application directory. The default local scope is tied to that project. Check the name and URL with claude mcp get resilis. In a Claude Code session, use /mcp to inspect status. Review any project-server approval or disabled status before retrying.
Troubleshoot permission and authorization prompts
Client tool approval and Resilis authorization are separate checks. Review each prompt and authorize only the operation you intend. If Resilis refuses an action, check organization membership, scope, target capability, and required production confirmation. Do not bypass a refusal. A working connection does not authorize all production changes.