🐑 Connect Spacesheep to Muse

Once connected, Muse can publish pages, read your spaces, check versions, and manage your Spacesheep account for you — through Spacesheep's hosted MCP server.

Step 1 — Create a full API key

Go to spacesheep.dev/settings and open the API keys section. Create a new key. It starts with ss_…

Use a full key. A streams-only or sessions-only key cannot use the MCP tools, and the server will refuse it.

Keep the key somewhere safe — it is shown once. You can revoke it any time from the same settings page.

Step 2 — Give the key to Muse

Ask Muse to connect to Spacesheep, and add the key through the secure connection card it shows you. Muse stores the credential in its secure vault — never paste the key into the chat itself.

Behind the scenes, Muse registers it as the custom.spacesheep connector and sends it as a bearer token:

Authorization: Bearer ss_…

to the MCP server at:

https://mcp.spacesheep.dev/mcp

Step 3 — Verify the connection

Ask Muse to check your account. A working connection reads back your profile — for example, name and @handle — and lists the tools the server offers (186 tools as of November 2026, including publishing, reading spaces, sessions, comments, and analytics).

If Muse can read your account, you're connected.

What you can do once connected

Publish pages — turn a document, report, or HTML file into a shareable Spacesheep space.
Read and search spaces — find pages by the words inside them, read versions, and check who has read them.
Manage your account — check API keys, sessions, and settings through Muse.
Keep every version — each publish is a new version you can roll back to.

Troubleshooting

Server refuses the key (401 / 403). The key may be revoked, mistyped, or scoped. Create a fresh full key in Settings → API keys and reconnect with it.

Streams-only or sessions-only key. These keys are for lab boxes and session sync only — they cannot call the MCP tools. Use a full key instead.

Blocked before reaching Spacesheep (HTTP 403, Cloudflare error 1010). This is not a bad key: Cloudflare stops the request before Spacesheep reads it. It bans one user agent, Python's built-in default (Python-urllib/3.x), so a client built on urllib fails with an API key and with OAuth alike. Set any other User-Agent header (for example Muse/1.0) and the same request goes through. Other Python libraries (requests, httpx, aiohttp) are not affected.

The MCP protocol version is not the cause: the server agrees on a version it supports, so a client offering a newer one still connects.

Still stuck? Revoke the key in Settings → API keys, create a new full key, and reconnect. Revoking a key stops anything using it at once.

Security notes

Your key lives in Muse's secure vault and is only sent to mcp.spacesheep.dev and spacesheep.dev.
Never share the key in chat, email, or a screenshot.
Give each machine or integration its own key, so you can revoke one without breaking the others.