Rackspace MCP connector
The Rackspace connector brings Rackspace support tickets, accounts, categories, resources and ticket history into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can open, update and comment on tickets in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize open Rackspace tickets by category this week.
Working in Rackspace with Elaichi
-
List all Rackspace accounts
-
List all Rackspace categories
-
List all Rackspace tickets
How to connect Rackspace to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Rackspace MCP connector for 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.
Rackspace MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Rackspace MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Rackspace MCP connector for 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.
Rackspace MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Rackspace through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Rackspace is logged.
-
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?”
What connecting Rackspace gets you
6 screens from Elaichi, each doing one job for your Rackspace account.
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, Cursor or Microsoft Copilot
The agent
Ask about Rackspace tickets in plain language.
The agent reads live Rackspace tickets, comments and events to answer you.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Rackspace here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
11 Rackspace tools ready without custom code.
Tickets, comments, attachments, accounts, categories and resources, every method already wired.
Toolboxes
Every team gets its own Rackspace toolbox.
Curate one toolbox per team, from support triage to escalation engineering.
Shared connections
Share a Rackspace account, never the credential.
See who connected each account and which teams and members work through it.
Audit log
Every Rackspace ticket change has a name on it.
When, who, what happened, type and resource, appended for each Rackspace call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Rackspace digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Rackspace
Queued
Automations
A schedule drafts your Rackspace ticket digest.
Fetch tickets, group them, draft a digest, get approval, post the comment back.
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%
Collections and dashboards
Rackspace ticket health, counted not guessed.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Rackspace
All three can connect Rackspace to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Rackspace tools | Allow or restrict single Rackspace tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Rackspace call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting creating, updating or commenting on them. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client in one step.
Does the Rackspace MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Rackspace is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Rackspace?
Yes. Both let Claude, ChatGPT or Cursor use Rackspace. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Rackspace call.
How is Elaichi different from Composio for Rackspace?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Rackspace: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Rackspace in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot