███████╗██████╗ █████╗ ██████╗███████╗███████╗██╗ ██╗██╗██████╗ █████╗ ██╗
██╔════╝██╔══██╗██╔══██╗██╔════╝██╔════╝██╔════╝██║ ██║██║██╔══██╗ ██╔══██╗██║
███████╗██████╔╝███████║██║ █████╗ ███████╗███████║██║██████╔╝ ███████║██║
╚════██║██╔═══╝ ██╔══██║██║ ██╔══╝ ╚════██║██╔══██║██║██╔═══╝ ██╔══██║██║
███████║██║ ██║ ██║╚██████╗███████╗███████║██║ ██║██║██║ ██║ ██║██║
╚══════╝╚═╝ ╚═╝ ╚═╝ ╚═════╝╚══════╝╚══════╝╚═╝ ╚═╝╚═╝╚═╝ ╚═╝ ╚═╝╚═╝
Spaceship AI MCP Server
MCP server for Spaceship AI — build, run, and manage AI agents directly from Claude Code, Cursor, VS Code, and Windsurf.
Quick start
Don't want to manually configure your MCP server?
Run spaceshipai@latest init to set everything up automatically with one command:
npx spaceshipai@latest init
This works with Claude Code, Cursor, VS Code, and Windsurf. It will authenticate via your browser, create a Spaceship API key for you, and configure your editor automatically.
Manual installation
If you prefer to configure manually, add the following to your IDE's MCP config file.
Claude Code — run in your terminal:
claude mcp add --scope user --transport stdio spaceship --env SPACESHIP_API_KEY=sk_live_... -- uvx spaceship-mcp
Or add to ~/.claude.json:
{
"mcpServers": {
"spaceship": {
"command": "uvx",
"args": ["spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "sk_live_..."
}
}
}
}
Cursor — add to ~/.cursor/mcp.json:
{
"mcpServers": {
"spaceship": {
"command": "uvx",
"args": ["spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "sk_live_..."
}
}
}
}
VS Code — add to ~/.vscode/mcp.json:
{
"servers": {
"spaceship": {
"command": "uvx",
"args": ["spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "sk_live_..."
}
}
}
}
Windsurf — add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"spaceship": {
"command": "uvx",
"args": ["spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "sk_live_..."
}
}
}
}
Get your API key from spaceshipai.io under Settings → API Keys.
Tools
Projects
| Tool | Description |
|---|---|
list_projects |
List all projects in your organization |
Agents
| Tool | Description |
|---|---|
list_agents |
List agents, optionally filtered by project |
get_agent |
Get full details of a single agent including its system prompt and tools |
create_agent |
Create an agent — pass description for auto-generated system prompt |
update_agent |
Update name, prompt, or tools; re-scaffold by passing a new description |
delete_agent |
Permanently delete an agent and all its logs, memories, and threads |
Running agents
| Tool | Description |
|---|---|
run_agent |
Start an async run; returns execution_id for polling |
get_run_status |
Poll status: queued → running → completed / error / cancelled |
get_run_logs |
Fetch the full chronological event log for a completed run |
list_executions |
List recent runs for an agent with status and duration |
test_agent |
Quick sync test — runs an agent and waits up to 15s for the result |
Orchestrations
| Tool | Description |
|---|---|
list_orchestrations |
List orchestrations, optionally filtered by project |
get_orchestration |
Get full details of an orchestration including its members and tools |
run_orchestration |
Start an async orchestration run; returns execution_id |
test_orchestration |
Quick sync test — runs an orchestration and waits up to 15s for the result |
Tools
| Tool | Description |
|---|---|
list_tools |
List built-in and custom tools available to attach to agents |
Example prompts
Once installed, you can talk to your agents naturally in any supported IDE:
List my projects, then show me all agents in the "production" project.
Create an agent called "Support Bot" in project 12 that handles customer refund requests.
Run the "Data Processor" agent with the prompt "Summarize last week's sales data".
Check the status of execution abc-123 for agent xyz-456, then show me the logs.
Test the "Email Classifier" agent with "Is this email spam: win a free iPhone now!"
List my orchestrations in the "production" project, then run the "Data Pipeline" orchestration.
Test the "Research Team" orchestration with input {"topic": "AI safety"} and show me the result.
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
SPACESHIP_API_KEY |
Yes | — | Your API key (sk_live_...) |
SPACESHIP_API_URL |
No | https://spaceshipai.io |
Override for local dev or staging |
Development
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
pytest tests/ -v
License
MIT
Metadata
Release files for spaceship-mcp 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| spaceship_mcp-0.1.6.tar.gz | 11.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spaceship_mcp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.7 kB
Release files / spaceship_mcp-0.1.6.tar.gz
| Download URL | spaceship_mcp-0.1.6.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b5c2d89cc741af03351bf3d500f1199df9cfb4a353a3d6d52fdf3030965e63a
|
|
BLAKE2b-256 checksum How to use checksums |
d37edc0aba927ea996e94366a31a0f6e3e583922458ac87d9315eeb7d84c9d79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 15, 2026.
Transparency logRelease files / spaceship_mcp-0.1.6-py3-none-any.whl
| Download URL | spaceship_mcp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e9263fb81471769e219c941fbda2490ccfbe9cd7acb690d654d855713607f5d
|
|
BLAKE2b-256 checksum How to use checksums |
7b0792727e09f71b67053c1c79ece43275f3dc62d997690aa71c56d67da8932c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 15, 2026.
Transparency logSecurity for spaceship-mcp 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for spaceship_mcp-0.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.