Koskamo

Wake MCP

Wake MCP connects AI agents like Claude Code, Cursor, and Codex to the Wake desk, enabling them to check site readiness, inspect agent experience, and access observability data via streamable HTTP JSON transport.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Wake MCP logo, by Agent ObservatoryCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-01Published by Agent Observatory
MCP endpoint (Streamable HTTP)
https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp
Vendor documentation

What you can do with it

  • Connect Claude Code to Wake desk
  • Check site agent readiness
  • Inspect agent experience observability

Source and maintenance

Community listingRegistry 1.0.0

Protocol and capabilities

Server
wake-site-readiness 1.0.0
MCP protocol
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Call wake_check_site with a public hostname to see how an AI agent experiences that site and what to fix. wake_about explains Wake. No key needed; results keep structural signals only.

Tools

2 advertised

wake_check_site — Check a site's agent readiness
Advertised by the server during the last successful anonymous check.
Advertised read-only

Probe a public hostname the way an AI agent sees it (homepage, robots.txt, llms.txt, sitemap, agent card) and return scores out of 100 with concrete recommendations and publish-ready llms.txt / robots files. Input is a hostname only; the probe keeps structural signals, never page bodies. No account needed.

wake_check_site input schema
{
  "type": "object",
  "properties": {
    "host": {
      "type": "string",
      "description": "Public hostname, e.g. docs.example.com"
    }
  },
  "additionalProperties": false
}
wake_check_site annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
wake_about — What Wake is
Advertised by the server during the last successful anonymous check.
Advertised read-only

One paragraph on Wake (agent experience observability + agent engine optimisation for a website), with links to docs, API, MCP and signup.

wake_about input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
wake_about annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1239 ms
95th percentile latency
1239 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1239 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http wake-mcp-railway https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add wake-mcp-railway --url https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wake-mcp-railway in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "wake-mcp-railway": {
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "wake-mcp-railway": {
      "type": "streamableHttp",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wake-mcp-railway and inspect its tools.
VS Code configuration
{
  "servers": {
    "wake-mcp-railway": {
      "type": "http",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http wake-mcp-railway https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "wake-mcp-railway": {
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "wake-mcp-railway": {
      "serverUrl": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Wake MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.