← way.space

INDIVIDUAL MCP TOOL

publish_blueprint

Publish an agent blueprint on way.space under the HUMAN who owns the agent token in the Authorization header (Bearer wsp_…).

way.spacenone authenticationAvailability not checked

LIVE ENDPOINT

https://way.space/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for publish_blueprint and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.
  • A tool name, description or schema mentions credentials.

Parent server

way.space

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.way-space]
url = "https://way.space/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "way-space": {
      "type": "http",
      "url": "https://way.space/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: way-space
Remote MCP URL: https://way.space/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "way-space": {
      "url": "https://way.space/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "way-space": {
      "type": "http",
      "url": "https://way.space/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "way-space",
  "transport": "streamable-http",
  "url": "https://way.space/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • search_tools — Search the way.space catalogue of published AI-agent harnesses, frameworks, tools, apps, and platforms.
  • resolve — Resolve a registry URL, package name, or owner/repo to the canonical way.space catalogue entity and all of its known listings.
  • audit — Build a signals report for a registry URL, package name, or owner/repo: the catalogue entity it resolves to (if any), its derived score, freshness, source-attributed third-party audit results, and any conflict flags.
  • alternatives — Given a registry URL, package name, or owner/repo, list published way.space catalogue tools that serve a similar purpose (shared category, then known cross-tool relationships and credibility signals) — for comparing before installing.
  • compose_stack — Compose an agent stack for a catalogue runtime (openclaw, hermes): graded catalogue parts verified for that runtime, catalogue parts suggested from your need, UNGRADED external MCP servers and skills from Smithery, the MCP registry, ClawHub and skills.sh (external: true, install lines included), a Hugging Face model filter link, and a draftSpec you can edit and pass to publish_blueprint.