# Rackspace MCP connector The Rackspace connector brings Rackspace support tickets, accounts, categories, resources and ticket history into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can open, update and comment on tickets in plain language. Source: https://elaichi.ai/connectors/rackspace/ ## Facts | | | | --- | --- | | Application | Rackspace | | Category | Helpdesk | | AI tools | 11 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Rackspace is connected - Summarize open Rackspace tickets by category this week. - Comment on ticket 48213 that the fix shipped. - Which Rackspace accounts opened the most tickets? ## Connect Rackspace in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Rackspace. 2. Optionally set Share with, then press Connect. 3. Paste a Rackspace API key. One person generates a token in Rackspace and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Rackspace tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Rackspace to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Rackspace to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Rackspace to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Rackspace to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Rackspace tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Rackspace through Elaichi ### Open a Rackspace ticket from a chat IT. Describe the problem in your own words and a Rackspace ticket is created against the right account and category, with the affected server or service named in it. ### See every open ticket at once Operations. Pull the current list of Rackspace tickets across all your accounts and get them grouped by category, age and status before the morning check-in. ### Add the customer's update to the ticket Support. After a call, post a comment on the Rackspace ticket and upload the screenshot or log file the customer sent, so the Rackspace engineer has everything in one place. ### Catch up on what changed overnight Engineering. Read the event history of a Rackspace ticket to see who replied, what was changed and when, without scrolling through email notifications. ### Find the resource behind an incident Security. List the Rackspace resources on an account and match them to the tickets raised against them, so the right hostname or service ends up in the incident report. ### Chase a stalled ticket to a close Management. Check where a Rackspace ticket stands, adjust its details or priority, and leave a note asking for an owner and a date. ## Frequently asked questions ### How do I connect Rackspace to Claude? First, connect Rackspace in Elaichi by pasting a Rackspace API key when prompted, which takes a minute or two. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register in Rackspace and no client ID or secret to generate. ### Does Rackspace work with ChatGPT and Cursor as well as Claude? Yes. Once Rackspace is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Rackspace once and every client picks it up. ### What can an AI agent actually do with my Rackspace data? With Rackspace connected, an agent can list your accounts, categories and resources, show open tickets, open a new ticket, update an existing one, add a comment and upload an attachment. It can also read the event history of a Rackspace ticket to tell you who changed what and when. It works from the live records in Rackspace, not a copy you have to export. ### Does connecting Rackspace give the AI access to every account? No. Access follows the Rackspace API key the person connected with, so the agent can only see the Rackspace accounts, tickets and resources that key already allows. Elaichi can narrow that further with restrictions per action, and it never widens what Rackspace itself permits. ### Can my team share one Rackspace connection? Yes. One person connects Rackspace in Elaichi and shares the connection with a team, and nobody else ever handles the Rackspace API key. Each teammate still signs in to Elaichi as themselves, so every ticket they open or comment they add is logged under their own name. ### Can I stop an agent from deleting or changing things in Rackspace? Yes. Restrictions in Elaichi apply per action, so you can allow reading Rackspace tickets while blocking creating, updating or commenting on them. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it. ### What happens to a Rackspace connection when someone leaves? Offboarding the person in Elaichi ends their access to Rackspace through every client at once. If they had shared their Rackspace connection with a team, it keeps working for everyone else. If you disconnect Rackspace in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client in one step. ## All 11 Rackspace tools Every tool below is callable through https://api.elaichi.ai/mcp once Rackspace is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Rackspace accounts** (List). List Rackspace accounts available to the authenticated user for viewing and ticket creation. Returns: name, id, rcn, serviceLevel, severities, type, permission, tags, npsOptOut. Max 500 per page. - **List all Rackspace categories** (List). List Rackspace ticket categories available for ticket creation. Returns: id, name, description, classification, subcategories. - **List all Rackspace tickets** (List). List Rackspace support tickets. Returns one record per ticket including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. - **Create a Rackspace ticket** (Create). Create a new Rackspace support ticket. Returns the created ticket including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. Required: accountId, subject, category, subcategory, comment.text. - **Get single Rackspace ticket by ID** (Get). Get a single Rackspace support ticket by id. Returns the full ticket object including ticketId, accountId, subject, status, severity, category, subcategory, created, modified, createdBy, modifiedBy, comments, recipients, and classification. Required: id. - **Update a Rackspace ticket by ID** (Update). Update a Rackspace support ticket by id, setting its status to Closed or replacing its resource list. Returns an empty 204 response on success. Required: id. - **Rackspace tickets add comment** (Add). Add a comment to an existing Rackspace support ticket. Returns an empty 204 response on success. Required: ticket_id, comment.text. - **Rackspace attachments upload** (Upload). Upload a file in Rackspace via multipart form data. Returns: expires, max_file_count, max_file_size, signature, redirect_url, url, uuid. Required: filename. The upload URL expires within 10 minutes and the returned UUID must be submitted with a ticket update to associate the file with a ticket. - **List all Rackspace resources** (List). List Rackspace resources the user has access to, used to select a category during ticket creation. Returns: id, accountId, name, platform, type, location, _links, network. Max 500 results per page. - **List all Rackspace ticket events** (List). List Rackspace consolidated ticketing events from the CloudFeeds Atom feed for a specified account. Returns: id, updated, published, title, category, link, content. Required: account_id. - **Create a Rackspace token** (Create). Authenticate to the Rackspace Cloud Identity service by submitting username and API key credentials to obtain an authentication token. Returns the access object containing the token (id, expires, tenant), service catalog with endpoint URLs, and user information with roles. Credentials are supplied automatically from the integration's stored auth configuration.