About magicpod-mcp-server
magicpod-mcp-server connects AI agents and MCP-compatible coding tools with MagicPod. This repository is deprecated and receives only bug and security fixes until November 1, 2026, before archiving.
Key features
- 01Connects AI agents with MagicPod
- 02Supports API-token or environment-variable authentication
- 03Configuration for MCP-compatible coding tools
- 04Deprecated; bug and security fixes only
Use cases
- 01Connecting an MCP client to MagicPod
- 02Supplying a MagicPod API token through configuration
MCP support
It is an MCP server that integrates AI agents with MagicPod, configured in MCP clients such as Claude Desktop and Cursor.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
30Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| username | string | Yes |
Details
From the project READMEmagicpod-mcp-server
Important
This repository is deprecated in favor of the new MagicPod MCP Server. It will only receive bug fixes and security fixes until November 1, 2026, after which it will be archived.
Please migrate to the new MagicPod MCP Server — see the setup instructions for details.
An MCP (Model Context Protocol) server that integrates your AI agents with MagicPod
Getting Started
Cursor, Claude, and many other AI-powered coding tools support MCP servers. You can refer to their official documents on how to configure MCP servers. For example, if you use Claude Desktop, what you have to do to integrate with MagicPod is only to add the following lines in your claude_desktop_config.json.
MacOS / Linux
{
"mcpServers": {
"magicpod-mcp-server": {
"command": "npx",
"args": ["-y", "magicpod-mcp-server", "--api-token=YOUR-API-TOKEN"]
}
}
}
Windows
{
"mcpServers": {
"magicpod-mcp-server": {
"command": "cmd",
"args": ["/c", "npx", "-y", "magicpod-mcp-server", "--api-token=YOUR-API-TOKEN"]
}
}
}
Make sure that you replace YOUR-API-TOKEN with your actual MagicPod API token. You can retrieve it on the integrations screen.
Using an environment variable instead of --api-token
Passing the token via --api-token puts it in plain text in the process's argument list (visible via ps, /proc/<pid>/cmdline, monitoring tools, etc.), which can be a concern on shared or monitored hosts. As an alternative, you can set the MAGICPOD_API_TOKEN environment variable instead, using the env field supported by most MCP clients:
{
"mcpServers": {
"magicpod-mcp-server": {
"command": "npx",
"args": ["-y", "magicpod-mcp-server"],
"env": {
"MAGICPOD_API_TOKEN": "YOUR-API-TOKEN"
}
}
}
}
If both --api-token and MAGICPOD_API_TOKEN are set, --api-token takes precedence.
Development
Build
npm run build
Configuration
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.