---
title: "The MCP Server Is Live"
date: 2026-04-06
author: MoteCloud
summary: "MoteCloud's MCP server is publicly accessible — OAuth 2.1, skill-based tool loading, and Streamable HTTP transport for any compatible client."
published: true
---

MoteCloud's MCP server is live at `/mcp`. Any client that supports Streamable HTTP transport can connect, authenticate through the browser, and start using graph memory immediately.

## How authentication works

There are no API keys. The server uses OAuth 2.1 with PKCE and dynamic client registration. Clients authenticate through a browser-based flow — no copying tokens from a dashboard, no managing key rotation, no shared secrets in config files.

The standards plumbing is all public:

- `/.well-known/oauth-authorization-server` — OAuth metadata per RFC 8414
- `/.well-known/oauth-protected-resource/mcp` — protected resource metadata per RFC 9728
- `/.well-known/jwks.json` — JWK set for token verification

This means any standards-compliant OAuth client can discover and authenticate without MoteCloud-specific documentation.

## Skill-based tool loading

The server exposes a bootstrap catalog. Tools load on demand — you activate only the capabilities you need:

| Tool | Purpose |
| --- | --- |
| `memory_prime_context` | Token-budgeted ranked context for a task |
| `memory_query` | Hybrid lexical + vector search |
| `memory_activate` | Graph signal propagation |
| `memory_ingest` | Persist facts with contradiction detection |
| `memory_stream_*` | Working memory sessions |
| `memory_capture_task` | Quick task capture with auto-session |
| `memory_context_for_code` | Code-oriented context preparation |

Entity tools, contradiction resolution, batch retrieval, and health checks are also available. Large outputs are returned as MCP resources rather than inline tool results, keeping context windows lean.

## Client compatibility

Tested and documented configurations exist for:

- **VS Code / GitHub Copilot** — native `mcp.json` configuration
- **Claude Desktop / Cursor** — Streamable HTTP config
- **Devin** — HTTP transport via MCP Marketplace

Any MCP client that supports Streamable HTTP transport should work. The auth flow is standard OAuth — nothing proprietary to integrate against.

## Two paths to access

**Human-created tenant**: Sign up on motecloud.io, create a tenant, mint an agent key. Straightforward for teams that want operators in the loop.

**Agent-created tenant**: A wallet challenge flow using SIWE lets agents sign up autonomously. Useful for systems where the agent provisions its own resources within spending boundaries set by the operator.

## Discovery

The server publishes everything a client or agent needs to self-configure:

```
/mcp                                          — transport endpoint
/.well-known/oauth-authorization-server       — OAuth metadata
/.well-known/oauth-protected-resource/mcp     — resource metadata
/.well-known/motecloud-billing.json           — billing descriptor
/llms.txt                                     — LLM-friendly site description
```

Agents can discover pricing, authenticate, and start working without human intervention.

## Get started

Point your MCP client at `https://motecloud.io/mcp` and follow the OAuth flow. The [docs](https://motecloud.io/docs) cover client-specific configuration for VS Code, Claude Desktop, Cursor, and Devin.