The MontyCloud MCP server lets AI apps such as Claude, ChatGPT, Claude Code, Cursor and Visual Studio Code work with your MontyCloud data. It uses the Model Context Protocol (MCP). MontyCloud hosts the server, so there's nothing to deploy or run.
What AI apps can do
You can ask about your data in plain language:
Area | What the app can do |
Tenants and accounts | See your tenants, their cloud accounts, and a summary of resources by type, region and account |
Cost and savings | See spend by account, service and region, the cost forecast, and savings from rightsizing, idle resources, Reserved Instances and Savings Plans |
Security | Review security posture, see which AWS security services are turned off in which accounts, and find the checks that fail most often |
Health | Track open, upcoming and closed AWS Health events |
Well-Architected assessments | Look into assessments, findings and review questions, create and run assessments, and answer review questions |
The server has 29 tools. Most only read data. Three create and run Well-Architected assessments and answer review questions. See the MCP Tools Reference for the full list.
Choose how to sign in
You can connect an app in two ways. Either way, the app has the same access as a MontyCloud user's role, and nothing more.
OAuth (recommended) | API key | |
Best for | People using AI apps | Scripts, CI pipelines and servers where nobody can sign in through a browser |
Apps | Claude, ChatGPT, Claude Code, Cursor, Visual Studio Code, and other apps that support remote MCP with OAuth | Claude Desktop, Cursor and Visual Studio Code, through the |
What you need | The MCP server URL and your MontyCloud login | A MontyCloud API key and secret, and Node.js 20 or later |
How you sign in | In your browser, with your password or your company's single sign-on (SSO), and MFA if your organization requires it | There's no browser sign-in. The app sends the key and secret with every request. |
Where credentials are kept | The app holds a token that only works with the MontyCloud MCP server. It never sees your password. | In the app's config file. Anyone who can read the file can use the key. |
Before you start
You need:
- A MontyCloud user account with a role in your organization.
- An AI app. The apps covered on this page are Claude, ChatGPT, Claude Code, Cursor and Visual Studio Code.
For an API key, you also need a MontyCloud API key and secret, and Node.js 20 or later with npm.
Find your MCP server URL
Use the MCP server URL for the region where you sign in to MontyCloud. Both sign-in methods use the same URL.
Region | You sign in to MontyCloud at | MCP server URL |
US |
|
|
EU |
|
|
US GovCloud |
| Not available yet |
To work out the URL, take your MontyCloud sign-in address, replace app with api, and add /mcp.
The URL must match your region. A MontyCloud account only works on its own region's server, so an EU account can't connect through the US URL.
In the steps below, replace <YOUR_MCP_SERVER_URL> with the URL from this table.
Connect with OAuth
OAuth is the recommended way for users to connect. You add the MCP server URL to your app, sign in with your usual MontyCloud login, and approve the app. You don't create or paste API keys.
Claude (claude.ai and Claude Desktop)
On the Pro and Max plans:
- Go to Settings > Connectors and choose Add custom connector.
- Enter a name, for example CloudOpsMCP, and enter
<YOUR_MCP_SERVER_URL>as the MCP server URL. - Choose Add, then Connect, and sign in.
- In a chat, turn on the connector from the tools menu.
On the Team and Enterprise plans, an Owner adds the connector once for the whole organization:
- The Owner goes to Organization settings > Connectors and adds a custom connector with the same name and URL.
- Each member then goes to Settings > Connectors, chooses Connect next to CloudOpsMCP, and signs in with their own MontyCloud account.
ChatGPT
ChatGPT connects to custom MCP servers in developer mode. On Business and Enterprise workspaces, an admin must allow custom connectors first.
- Go to Settings > Apps & Connectors > Advanced settings and turn on Developer mode.
- Back in Apps & Connectors, choose Create.
- Enter a name, for example CloudOpsMCP, enter
<YOUR_MCP_SERVER_URL>as the MCP server URL, and set Authentication to OAuth. - Confirm that you trust the app, choose Create, and sign in. ChatGPT registers itself with the MontyCloud MCP server, so there's nothing else to enter.
- In a chat, choose the connector from the tools menu.
Claude Code
Add the server:
claude mcp add --transport http cloudopsmcp <YOUR_MCP_SERVER_URL>
For example, in the US:
claude mcp add --transport http cloudopsmcp https://api.montycloud.com/mcp
Add --scope user to use the server in all your projects. Then, in a Claude Code session:
- Run
/mcp. - Select cloudopsmcp.
- Choose Authenticate and sign in in your browser.
Cursor
Add the server to ~/.cursor/mcp.json to use it in all your projects, or to .cursor/mcp.json to use it in one project:
{
"mcpServers": {
"cloudopsmcp": {
"url": "<YOUR_MCP_SERVER_URL>"
}
}
}
Open Cursor Settings > MCP. Next to cloudopsmcp, choose Connect (or Needs login) and sign in.
Visual Studio Code (GitHub Copilot)
Run MCP: Add Server from the Command Palette, choose HTTP, and enter your MCP server URL. Or add the server to .vscode/mcp.json:
{
"servers": {
"cloudopsmcp": {
"type": "http",
"url": "<YOUR_MCP_SERVER_URL>"
}
}
}
Choose Start above the server entry. When VS Code asks you to sign in, choose Allow and sign in. You can then use the MontyCloud tools in Copilot's agent mode.
Other apps
Other apps can connect with OAuth if they:
- support remote MCP servers over Streamable HTTP;
- sign in with OAuth 2.1 and PKCE, and register through Dynamic Client Registration or a Client ID Metadata Document;
- use a callback URL that MontyCloud has approved.
See Supported Apps and Callback URLs for the approved list and how to request a new callback URL.
If your app can only run local (stdio) MCP servers, connect through the mcp-remote bridge:
{
"mcpServers": {
"cloudopsmcp": {
"command": "npx",
"args": ["-y", "mcp-remote", "<YOUR_MCP_SERVER_URL>"]
}
}
}What happens when you sign in
You sign in the first time you connect, and again whenever your app asks you to.
- Your app opens the MontyCloud sign-in page for your region in your browser.
- Enter your work email and choose Continue.
- If your organization uses SSO, you go to your company's sign-in page. Otherwise, enter your MontyCloud password, and your MFA code if you have MFA set up.
- MontyCloud shows which app is asking for access and which account you signed in with. Choose Allow to connect, or Deny to stop. If you're signed in as the wrong person, choose Use another account.
- Your browser returns to the app, and the app is connected.
Some things to know about signing in:
- The app never sees your password. You sign in on MontyCloud's page, and the app receives a token that only works with the MontyCloud MCP server.
- The app stays signed in. Access tokens last one hour, and the app renews them on its own. After 30 days, or if your access ends, the app asks you to sign in again.
- The sign-in page times out after 15 minutes. If that happens, start again from the app.
Connect with an API key
Use an API key for scripts, CI pipelines and servers where nobody can sign in through a browser. An API key also works for an app that can't sign in with OAuth, or whose callback URL isn't approved yet.
Step 1: Create an API key
- Sign in to MontyCloud.
- Open User Settings from the profile menu in the top right.
- Go to API Keys and choose Generate API Key.
- Copy the API key and the secret key. MontyCloud shows the secret key only once, so store it somewhere safe.
The key has the same access as the role of the MontyCloud user who created it.
Step 2: Check that the key works
This step is optional. Send a test request with your MCP server URL, key and secret:
curl -X POST '<YOUR_MCP_SERVER_URL>' \
--header 'Accept: application/json, text/event-stream' \ --header 'Content-Type: application/json' \ --header 'x-api-key: <YOUR_API_KEY>' \ --header 'Authorization: <YOUR_API_SECRET>' \ --data '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}'
If the key works, the response is a JSON list of the available tools.
Step 3: Add the server to your app
Add this configuration to your app. It runs the mcp-remote bridge, which sends your key and secret to the MontyCloud MCP server:
{
"mcpServers": {
"cloudopsmcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<YOUR_MCP_SERVER_URL>",
"--header",
"x-api-key:${API_KEY}",
"--header",
"Authorization:${API_SECRET}"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"API_SECRET": "<YOUR_API_SECRET>"
}
}
}
}App | Where the configuration goes |
Claude Desktop | Go to Settings > Developer and choose Edit Config. This opens |
Cursor |
|
Visual Studio Code (GitHub Copilot) |
|
Keep the config file private, and don't commit it to source control. Anyone who can read it can use your key.
What the app can access
The app acts as a MontyCloud user. With OAuth, that's the person who signed in. With an API key, it's the user who created the key. The app can only see and do what that user's role allows, in the tenants the user can access. One connection covers all of those tenants, so you don't need a connection per tenant.
Disconnect an app
For an app connected with OAuth:
- In the app, remove or disconnect the CloudOpsMCP connector.
- To end access from MontyCloud's side, email MontyCloud support at support@montycloud.com. Support can end one app's access to your account, or all your app connections.
- Changing or resetting your MontyCloud password ends all your OAuth connections at once.
OAuth access also ends on its own if your MontyCloud account is disabled or deleted.
For an app connected with an API key, remove the server from the app's config file. To stop the key working in every app and script that uses it, delete the key in MontyCloud.
Security
Area | How it's handled |
Transport | Streamable HTTP over HTTPS only |
Tenant controls | MCP access can be turned off for a tenant. To turn it off or back on, email support@montycloud.com. |
Compliance | MontyCloud is SOC 2 Type 2 certified |
Troubleshooting
OAuth sign-in
What you see | What it means and what to do |
This app's callback URL is not allowed | The app's callback URL isn't on MontyCloud's approved list yet. See Supported Apps and Callback URLs to request it. In the meantime, you can connect with an API key. |
This sign-in has expired | The sign-in took longer than 15 minutes, or a sign-in page was reused. Start again from the app. |
We couldn't find a MontyCloud account for this sign-in | There's no MontyCloud user for this email in this region. Check that you used your region's MCP server URL. If you did, ask your administrator to invite you. |
Your MontyCloud account has no role yet | Ask your administrator to give you a role. |
MCP access is turned off for your tenant | MCP access was turned off for your tenant. Contact your administrator, or email MontyCloud support at support@montycloud.com. |
Your organization signs in with single sign-on, not a password | Use your company sign-in. Enter your work email on the first page, and you're sent there. |
Your organization requires MFA | Your organization requires multi-factor authentication (MFA) for password sign-ins, and you haven't set it up yet. You can't set it up during this sign-in. Sign in to the MontyCloud web app, set up MFA there, then connect again. |
You're signed in as the wrong person | On the approval page, choose Use another account. |
The app was connected but now fails or asks you to sign in | Your sign-in ended after 30 days, a password change, or a change to your account. Connect again from the app. |
API key
Problem | What to do |
The connection is refused | Check your network connection and, if you need one, your VPN. Check that the MCP server URL matches your region. |
Authentication fails | Run the test request in Step 2. Check that the key and secret are correct and haven't expired. If they have, ask your administrator for new ones. |
Access is denied, even though the key and secret are correct | MCP access or API key access may be turned off for your tenant. Contact your administrator, or email MontyCloud support at support@montycloud.com. |
The server doesn't start, or tools fail | Run |
FAQ
Do I need an API key to connect?
No. With OAuth you sign in with your MontyCloud login. You only need an API key for scripts and other setups where nobody can sign in through a browser.
Can the app see my password?
No. With OAuth, you sign in on MontyCloud's page, and the app only receives a token that works with the MontyCloud MCP server. With an API key, the app uses the key and secret, not your password.
Can I connect more than one app?
Yes. Each app has its own connection. With OAuth, you approve each one.
I work across several tenants. Do I need one connection per tenant?
No. The connection uses a MontyCloud user, so the app works across all the tenants that user's role gives access to.
My app isn't listed on this page. Can I still use it?
Often, yes, if it supports remote MCP with OAuth. If its callback URL isn't approved yet, see Supported Apps and Callback URLs to request it.
Related
- MCP Tools Reference: what each tool does
- Supported Apps and Callback URLs: approved apps, new app requests, and details for app developers