SpaceYew Connect

1. Save a draft

Set SPACEYEW_URL and SPACEYEW_TOKEN in your client's private environment, then call the shared submission API.

POST /api/connect
Authorization: Bearer <SPACEYEW_TOKEN>
Content-Type: application/json

{
  "operation": "catalog.save",
  "requestId": "unique-operation-key",
  "input": {
    "kind": "docs",
    "title": "My first guide",
    "summary": "A practical guide for the community.",
    "bodyHtml": "<h2>Getting started</h2><p>Explain each step of your workflow here.</p>",
    "category": "Development",
    "license": "Original work; shared with attribution."
  }
}

2. Posting Skill

The project includes an spaceyew-post Skill with field guidance, safe retries and a draft-first submission workflow.

3. Local MCP bridge

Run the bridge as a stdio process. It supports MCP 2025-11-25 with credentials from the client environment. A public HTTP MCP endpoint is not provided.

{
  "mcpServers": {
    "spaceyew": {
      "command": "node",
      "args": ["/absolute/path/site-v1/integrations/spaceyew-mcp.mjs"],
      "env": {
        "SPACEYEW_URL": "http://localhost:3010",
        "SPACEYEW_TOKEN": "<private scoped credential>"
      }
    }
  }
}

Drafts are the default. After your explicit publishing instruction and authorization, AI can call catalog.submit directly. Approved content appears in its catalog and community; flagged content waits for review.

Credentials expire within 90 days and can be revoked anytime. Writes require a stable operation key; identical retries return the same result for 24 hours.