Helpdesk
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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Rackspace to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Rackspace once
-
Open Connections, choose Add connection, and pick Rackspace.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Rackspace to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Rackspace to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Rackspace through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Open a Rackspace ticket from a chat
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.
-
Operations
See every open ticket at once
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.
-
Support
Add the customer's update to the ticket
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.
-
Engineering
Catch up on what changed overnight
Read the event history of a Rackspace ticket to see who replied, what was changed and when, without scrolling through email notifications.
-
Security
Find the resource behind an incident
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.
-
Management
Chase a stalled ticket to a close
Check where a Rackspace ticket stands, adjust its details or priority, and leave a note asking for an owner and a date.
Try asking
- “Summarize open Rackspace tickets by category this week.”
- “Comment on ticket 48213 that the fix shipped.”
- “Which Rackspace accounts opened the most tickets?”
AI tools
Rackspace tools for your AI agents
11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Rackspace, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Rackspace gets you
6 screens from the product, each doing one job for your Rackspace account.
The agent
Ask about Rackspace tickets in plain language.
The agent reads live Rackspace tickets, comments and events to answer you.
- tickets
- comments
- accounts
- attachments
Ask Elaichi to work across your apps.
Summarize open Rackspace tickets by category this week.
Comment on ticket 48213 that the fix shipped.
Which Rackspace accounts opened the most tickets?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Rackspace here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
11 Rackspace tools ready without custom code.
Tickets, comments, attachments, accounts, categories and resources, every method already wired.
- List all Rackspace accounts
- List all Rackspace categories
- List all Rackspace tickets
- Create a Rackspace ticket
Toolboxes
Every team gets its own Rackspace toolbox.
Curate one toolbox per team, from support triage to escalation engineering.
- Support
- Escalations
- Infrastructure
- Account management
Shared connections
Share a Rackspace account, never the credential.
See who connected each account and which teams and members work through it.
- Support EMEA
- Support NA
- Escalations
- Infrastructure
Audit log
Every Rackspace ticket change has a name on it.
When, who, what happened, type and resource, appended for each Rackspace call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Rackspace ticket digest.
Fetch tickets, group them, draft a digest, get approval, post the comment back.
Rackspace digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Rackspace
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Rackspace
Queued
Collections and dashboards
Rackspace ticket health, counted not guessed.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
Rackspace health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Comments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support NA 27%
Escalations 21%
Infrastructure 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Rackspace in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.