API Tools

clearly.sh

Enables searching Clearly's public project directory, chatting with project AI agents, and submitting lead contact requests.

1 endpoint3 known toolsFirst detected June 20, 2026Last detected September 11, 2026

ENDPOINT 1

https://relay.clearly.sh/mcp

No auth detected

MCP server metadata

Name: clearly
Version: 0.3.1+628d27de

Capabilities

toolsprompts

Server instructions

Clearly is the user's workspace: notes, canvases, projects, tickets, and their voice recorder. FINDING A VERB. Only ~20 tools are listed; the workspace has ~1,000 actions behind clearly_workspace_catalog + clearly_workspace_invoke. ALWAYS call the catalog with `search` or `category` — a bare call returns a ~12.7k-token name index with no schemas. Most actions declare no input schema, so the description is the record of the arguments: read it rather than guessing field names. PATHS. The shell tools address two namespaces: `~` is the notes workspace (folders are projects, notes are .md files, canvases are .scene.json) and `/code` is the code tree. A bare or relative path means `~`. (An rpc:admin token also gets `/local`, the user's own machine; without that scope every /local path is refused, so do not reach for it.)

Known tools 3

clearly_search_projects

Search the Clearly directory of public projects (real estate listings, courses, startup data rooms, professional services, products, events, etc.

Inferred read-only

clearly_ask_project

Talk to a public Clearly project's AI agent.

Inferred read-only

clearly_capture_lead

Tell a Clearly project owner that you (or your user) want to be contacted.

Inferred read-only

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.clearly]
url = "https://relay.clearly.sh/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "clearly": {
      "type": "http",
      "url": "https://relay.clearly.sh/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: clearly
Remote MCP URL: https://relay.clearly.sh/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": {
    "clearly": {
      "url": "https://relay.clearly.sh/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "clearly": {
      "type": "http",
      "url": "https://relay.clearly.sh/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "clearly",
  "transport": "streamable-http",
  "url": "https://relay.clearly.sh/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.